01 / 07
Enterprise Networks
Campus, WAN, SD-WAN and wireless: we design, build and migrate enterprise networks — documented from HLD to sign-off.
- Campus & WAN
- SD-WAN
- Wireless
We design, build and operate business networks. From the first architecture decision to ongoing operations, Configlane combines Cisco engineering with automation — as your project partner, an extension of your IT team or the delivery team behind your service provider.
Cisco networks & network automation
Network
Engineering.Automated.
Cisco network solutions
Campus, WAN, wireless and security: we support business networks across their full lifecycle — from architecture and migration to site rollouts and ongoing operations.
Network automation
We industrialise network operations: source of truth, configuration as code and tested changes are our standard, not a special project. Rollouts become plannable and changes become predictable.
Operations & ownership
We stay alongside you after the project: through managed services or together with your IT team. Standard changes, maintenance, escalation and documentation have an agreed scope and clear ownership.
Cisco Meraki · Plan / Build / Operate
Your network. A shared plan.
From a single office to a branch network: we design, build and operate Cisco Meraki networks. Directly for your business or as the delivery team for your IT service provider.
Managed services
Dashboard operations, changes, firmware and escalation – managed for you or alongside your IT team.
Explore the scope02Design & rollout
Build new sites with a reviewed design, a pilot, a cutover plan and documented acceptance.
Explore the scope03Wireless & switching
Align RF design, access switches and network access with your spaces, devices and applications.
Explore the scope04SD-WAN & branch connectivity
Connect sites with Meraki MX, including routing, segmentation and tested failure scenarios.
Explore the scope05Existing network takeover
Change providers or relieve your team with a structured assessment and a controlled handover.
Explore the scopeBuild a new network, take over an existing estate or complement your IT team. Scope, service hours and responsibilities are agreed around your needs.
Prepare for the conversation: download the Meraki project brief (.md)Editable checklist. No registration.
The approach
We do network engineering and automation. Most of all, we make infrastructure quiet: one source of truth instead of spreadsheets, tested changes instead of night shifts — so your team can attend to what truly counts.
Quiet
infrastructure.
About Configlane
A systems house run by engineers
Grown out of operations. Configlane is an owner-led systems house for network engineering and automation. Our roots are in operating large Cisco environments, where changes need real maintenance windows and a mistake is never abstract. That experience shapes how we set up projects: clear responsibilities, honest estimates, and a way back that is settled before the change.
Engineering leads. No sales layer steers our projects. Whoever designs at Configlane also builds; whoever builds stays accountable in operations. Decisions are made in review, not in the hallway — every change has an author, a reviewer and a documented rollback. That is our idea of craftsmanship in IT.
Knowledge stays with you. Runbooks, architecture decisions and the source of truth are part of the delivery. Your team should be able to understand, operate and evolve our work — clients stay with us because they want to, not because they have to.
What we stand for
For us, accountability does not end at sign-off.
Know-how
Deep in the Cisco stack, at home in automation
Our CCNP-certified engineers work across the Cisco stack: routing and switching in campus and WAN, SD-WAN, wireless, Identity Services Engine, Secure Firewall, Meraki and Catalyst Center. We know these platforms from projects and from operations — not from the datasheet.
Alongside it sits an automation stack proven in daily practice: NetBox as the source of truth, Ansible and Python for execution, pyATS for automated network testing, Git for review and history. Tools change — the discipline behind them does not.
Services
The whole network, across its whole lifecycle
Consulting, design, delivery and operations interlock. Engage any service on its own — or hand over the complete project.
02 / 07
Network Automation
Source of truth, configuration as code and tested changes: network operations that repeat reliably instead of depending on individuals.
- NetBox
- Ansible
- pyATS
03 / 07
Cisco Catalyst Center
Cisco Catalyst Center as an operations platform: plug-and-play rollouts, golden images, compliance and assurance — introduced and handed over.
- Plug and Play
- SWIM
- Assurance
04 / 07
Security & Access
Firewalls, segmentation, NAC with Cisco ISE and vulnerability management: controlled access, comprehensible rules and gaps that get closed.
- Firewall
- NAC / ISE
- Segmentation
- Vulnerability Management
05 / 07
OT Security
Visibility and segmentation for production and industry: Cisco Cyber Vision, zones per IEC 62443, NIS2-ready evidence.
- Cyber Vision
- IEC 62443
- NIS2
06 / 07
Cisco Meraki
Cloud-managed networking with Cisco Meraki: from design and rollout to dashboard operations and the API.
- MX · MS · MR
- Dashboard
- API
07 / 07
Small Business
Dependable networks for smaller companies: Wi-Fi, firewall and VPN — built properly, priced fairly, looked after.
- Wi-Fi
- Firewall
- Care plans
- Cisco
- Cisco Meraki
- Ansible
- Cisco Catalyst
- Python
- Cisco Catalyst Center
- NetBox
- Jinja
- Cisco ISE
- Cisco Cyber Vision
- Git
- Cisco pyATS
- pfSense
- Check Point
- Jinja
- Cisco ISE
- Cisco Cyber Vision
- Git
- Cisco pyATS
- pfSense
- Check Point
- Cisco
- Cisco Meraki
- Ansible
- Cisco Catalyst
- Python
- Cisco Catalyst Center
- NetBox
How we work
Every change travels the same lane
Six stages with defined entry and exit criteria. The separation of build, test and deploy matters most: a successfully generated configuration artifact is not yet an approval for production. Every stage leaves an artifact that lasts — from the inventory diff to the acceptance record.
- Inventory diff
Discover
We capture the current state from devices, controllers and APIs and hold it against the existing documentation.
- Network inventory via CLI, SNMP and controller APIs
- As-is analysis for LAN, WAN and Wi-Fi
- Reconciled against CMDB and existing docs
- HLD / LLD
Design
Target architecture, data model and migration path are designed and agreed with your team.
- High-level and low-level design (HLD/LLD)
- Target architecture for campus, data centre and SD-WAN
- Migration plan with risk assessment
- Jinja template
Automate
The target configuration is generated from structured data and versioned templates, not copy-and-paste.
- Infrastructure as code with Ansible and Python
- Jinja2 templates from the source of truth (NetBox)
- Versioned and reviewed in Git
- pyATS report
Test
Cisco pyATS and Genie verify routing, adjacencies, VPN, redundancy and reachability — before and after the change.
- Automated network testing with Cisco pyATS and Genie
- Pre- and post-checks for routing, VPN and redundancy
- Test reports as the release gate
- Change log
Change
Execution in the approved window, with dry run, peer review, full logging and a defined rollback.
- Change management with dry runs and peer review
- Maintenance windows with a defined rollback plan
- Every change fully logged
- Acceptance record
Document
The source of truth is updated, acceptance is recorded and operations are handed over.
- Network documentation and operations handover
- Source of truth updated in NetBox
- Acceptance protocol and runbooks for operations
Where repetition pays off, we automate
Automation is never an end in itself for us — it is the tool that makes recurring rollouts, checks and standard changes dependable. Whatever repeats gets structured, versioned and tested.
Repeatable rollouts
Templates and structured data instead of one-off configuration.
Fewer manual errors
Validation, peer review and controlled execution.
Traceable changes
Git history, logs and acceptance reports for every change.
Less key-person risk
Standardised roles, tests and operating procedures.
Our standard
A change is only done when it is tested, documented and reversible.
This is how a standard change runs at Configlane: the change is born as a record in the source of truth, rendered from versioned templates and diffed against the live state. Before rollout come automated pre-checks and a peer review by a second engineer; after it, post-checks against the same criteria — inside the agreed maintenance window, with the way back prepared.
None of this is project theatre; it is our everyday operations. It makes changes plannable, audits calm and night shifts rare.
Articles
Practical knowledge for Cisco networks
The three articles that bring searchers to this site most often — on licensing models, wireless planning and release strategy. Researched, dated, with sources disclosed.
All articles
For IT providers
White-label senior engineering
A customer Meraki rollout, ongoing dashboard operations or a demanding Cisco project: we complement your team as a white-label delivery partner. With agreed customer communication, clear responsibilities and documentation for your operations.
Next step
An assessment, not a transformation promise
We start with an inventory: how reliable are your records, standards and change processes — and where does automation pay off first?
Request an assessmentAssessment → first dependable change