Design · migrations · multi-vendor

Network engineering & architecture

We design and migrate networks for operators and businesses — from access and radio links to metro rings and the BGP edge. Multi-vendor, documented and without service interruption.

Illustration of a network topology with nodes connected in a ring
Multi-vendor, no bias
MikroTik, Cisco, Juniper, Edgecore with OcNOS. We don't sell hardware, so we choose it for the network, not for the margin.
Migrations without downtime
Step by step, in maintenance windows, with a rollback plan and measurements before and after every phase.
Operator-grade design
ISP, WISP and MDU networks — access, aggregation, core, the BGP edge and upstream connectivity.
Documentation that stays true
Topology, addressing plan and configs in git. Your team knows what was done and why.

Scope

What we do

The most common projects, from a greenfield network to replacing hardware under live traffic.

Stack

  • MikroTik
  • Cisco
  • Juniper
  • Edgecore / OcNOS
  • BGP
  • OSPF
  • MPLS

Operator networks

  • ISP, WISP and MDU network design — access, aggregation and core
  • The BGP edge: upstream and peering connectivity, filtering and routing policy
  • Metro rings and redundant paths, OSPF and MPLS in the core
  • Point-to-point radio links and wireless access for WISPs
  • MDU networks for residential and commercial buildings

Migrations and hardware replacement

  • Moving between vendors (e.g. replacing one vendor with another in the core or aggregation)
  • RouterOS v6 to v7 upgrades
  • Merging networks after an acquisition or integration
  • Rolling out IPv6 alongside existing IPv4 traffic

Assessment and audit

  • A review of the existing network: risks, single points of failure, security
  • Capacity analysis and a growth plan
  • Written findings with priorities — what to fix now, next quarter, and what can wait

How we work

Every change has a rollback plan.

  1. 01

    Baseline

    Topology, configs, monitoring and traffic. We find out what actually runs, not just what the documentation says.

  2. 02

    Design

    Target architecture, addressing plan, routing policy and migration order — in writing, for your review.

  3. 03

    Migration

    Phases in maintenance windows, with before/after measurements and a clear rollback criterion.

  4. 04

    Handover

    Updated documentation, configs in git and a walkthrough of the new network for your team.

Questions

Frequently asked

Do you only work with MikroTik?

No. We work with MikroTik, Cisco, Juniper and Edgecore/OcNOS — often in networks that use all of them together.

Can you take over a network someone else designed?

Yes — that is a common starting point. We baseline and document what exists first, and only then propose changes.

Do you work outside Serbia?

Yes. On-site in Serbia and the region, and remotely anywhere with secure access.

Planning a migration or a new network?

Send us a topology or a short description — we'll propose a plan and scope.