We build the network.
Then we hand over the access.
Some projects need more than a machine with a cable in it. We design the network, buy the equipment, rack it in our own data centres, configure it, and then hand over the access.
- where
- AMS · MEP · IAD · PHX
- scope
- design → racking → handover
- vendors
- Cisco · Juniper · MikroTik
- afterwards
- monitoring · changes by ticket
- price
- quoted per project
Two sites, one segment.
Each site gets its carriers over BGP, a router pair and a firewall in front of your segments. The private one can stretch across both sites as a single L2 segment, so servers in the Netherlands and the US share one addressing domain.
From a topology drawing to a configured rack.
Network architecture
architecture for server clusters · isolated private segments · distributed networks between our data centres · highly available configurations with redundant equipment · multi-level segmentation by traffic type · room to grow without a rebuild
Procurement and installation
buying switches, routers and firewalls to the specification · physical mounting in the data centre rack · power and network connection · structured cabling · configuration and handover with access
Private segments
private VLANs per segment of your infrastructure · traffic separation at L2 and L3 · DMZ zones for public services · microsegmentation with per-service policy · east-west filtering inside the network
Multiple uplinks and BGP
connections to several upstream providers · BGP routing with automatic failover · balancing between carriers · route optimisation for shorter paths · separate channels for different traffic types · redundancy at the provider level, not just the switch
Distributed networks and VXLAN
VXLAN between our sites in the US and the Netherlands · one addressing domain across locations · geo-distributed clusters · disaster-recovery configurations · hybrid setups split across sites
Throughput and latency
high-throughput configurations · tuning per traffic type: storage, database, web · jumbo frames · RDMA for latency-sensitive workloads · dedicated bandwidth channels · LACP aggregation for speed and redundancy · QoS priorities for the traffic that must not wait
Network security
firewall rules and ACLs · NAT and address translation · isolation between customer segments · protected management networks · intrusion detection at the network layer · monitoring for anomalous traffic · periodic review of the configuration
Monitoring and support
availability of every network component · bandwidth use and emerging bottlenecks · latency and packet loss · BGP session and routing state · load on the network equipment · incident response and scheduled maintenance · configuration changes at an agreed time
Whatever the project needs
non-standard VLAN schemes · complex routing policies · custom firewall rules · specific QoS configurations · integration with your existing network over VPN or IPsec · BGP peering with your own infrastructure · hybrid cloud connectivity
This is the one service where we do the work ourselves. The boundary does not move: the operating systems on your machines stay yours, as /about says.
Priced per project, because none of them repeat.
Cost follows the architecture: segments, VXLAN across sites, uplinks, what has to be redundant, and how much of it we watch afterwards.
You describe the requirement
Technical requirements, or the problem you are trying to solve if the requirements are not settled yet.
Our engineers design it
We work out the architecture and the equipment list against your constraints, budget included.
We quote the whole thing
A commercial proposal with the solution described in detail: equipment, work, and what it costs to keep running.
We agree terms and timing
An accurate timeline is possible once the design exists. Before that, any date would be a guess.
We build it and keep it running
Procurement, racking, configuration, handover, then monitoring and changes by ticket.
- No DDoS mitigation, here or anywhere on this site. Edge filtering and monitoring that wakes a human is the whole of it.[no]
- No uptime percentage. Redundancy and several carriers are real; a number we have not signed is not.[no]
- No timeline before the design exists. Anything earlier is a guess with a date attached.[no]
- Monitoring data is shared on request, in a limited form, since it is our infrastructure being measured.[limit]
- The operating systems on your servers stay yours.[limit]
- 01 ─
What if I need the configuration changed later?
Open a ticket describing the change. Our engineers make it in a window agreed with you.
- 02 ─
Can you integrate with my existing infrastructure?
Usually yes: BGP peering or another form of integration. What is possible depends on what the end result has to look like, so describe that first.
- 03 ─
Do you support IPv6?
Yes, fully, in every location.
Ready to talk about your network?
Describe the requirement and we will come back with an architecture, from a handful of VLANs to a VXLAN cluster across two continents.