Independent systems architecture

Small by design.
Serious by consequence.

AlpskiMedved.solutions is built around one accountable systems architect—not a generic helpdesk façade. The scope expands when the problem demands it, not because a catalogue needs filling.

The front door

Networks first.

Network architecture stays front and centre because it is the technical core: connectivity, routing, switching, wireless, segmentation, resilience and the field conditions that make them difficult.

Adjacent business systems belong when they share the same operational problem. They do not become a vague promise to “do all IT.”

Operating principles

A specialist model with visible edges.

01

Evidence over adjectives

Measurements, constraints and observed behaviour carry more weight than generic promises about reliability.

02

Architecture before procurement

Hardware is selected because the system needs it—not because a preferred stack needs somewhere to go.

03

Smallest sufficient system

Enough structure, resilience and headroom for the real operation without manufacturing complexity.

04

Right specialist, right moment

Fibre, electrical, construction and other disciplines are coordinated with trusted peers instead of being imitated.

How the model scales

One accountable line.
A flexible delivery team.

CORE

Systems architect

Discovery, architecture, technical decisions, integration and verification.

WHEN NEEDED

Trusted specialists

Fibre, electrical, construction, installation capacity and adjacent disciplines.

OUTCOME

One coherent system

The right work performed by the right people, without losing architectural accountability.

SERVICE AREABohinj · Bled · Kranjska Gora
SPECIALISTMarko Kolman
FOCUSNetworks · SMB technology
MODELSolutions architect · MSP

Start with the work

See the problems, contexts and field method.