Skip to main content
DIVERSITY. We make IT happen

Private Link

Your offices, plants and your own datacenter, connected to the services you run with us. Three ways in, whichever suits the site: our router over the connectivity you already have, our fibre and our router, or a tunnel over your own connection.

Encrypted on every way in

50 Mbps to 10 Gbps

Tunnel live in 24 to 48 hours

Three ways in. One link reaches all four sites.

Private does not mean the internet is absent from the path. It means encryption on every way in, and a firewall that lets through only the services you agree with us. Each link lands at our site nearest to it, and our own Layer 2 network carries it to the other three.

Topology: three of your sites reach the DIVERSITY network, one way in each. A branch rides its own line through a router of ours, the head office rides our fibre and our router, and your own datacenter runs a tunnel from its equipment over its own line. All three are encrypted and land at our site nearest you, where a firewall lets through only the services you agree with us, among Cloud, Bare Metal, Colocation and Telecom. Our own Layer 2 network carries the link on to our other three sites, and to whatever you run there.

Branches and sites

Our router over the connectivity you already have

Head office

Our fibre and our router, both

Your own datacenter

Your own tunnel, over WireGuard, IPsec, or GRE inside IPsec

DIVERSITY network

Our site nearest you

Our firewall lets through only the services you agree with us

Cloud

Instances and managed services

Bare Metal

Dedicated servers

Colocation

Your racks in our datacenters

Telecom

CloudPBX and SIP trunking

Our other three sites

Whatever you run there, over our own Layer 2 network

Private Link

Your sites, one way in each

Your line

Our fibre

Your line

Pick the way in. The rest is the same.

The way in depends on what the site already has. Everything below it is true of every link: the capacity range, the encryption, the routing, the reach, the cover and the terms. Where the way in changes an item, the item says so. There are no prices here; you get one in your quote.

Ways in

Our router over your line

We install it, configured, on the connection your site already has

Up to 14 days

Our fibre and our router

For a site in Madrid, Amsterdam, Munich or Helsinki, with a European partner on the last mile

14 to 35 days: the fibre has to be laid

A tunnel over your connection

From your own equipment, with WireGuard, IPsec, or GRE inside IPsec

24 to 48 hours

Every link

Capacity

  • From 50 Mbps to 10 Gbps
  • Best effort, set per link for what the site needs

Encryption

  • Every way in, from your site to ours
  • On a tunnel: WireGuard or IPsec, and GRE only inside IPsec
  • Specific algorithms on request, agreed per customer
  • Between our four sites too

Routing

  • BGP, with your own ASN, public or private
  • Your private ranges are announced to us
  • Our services keep their own addresses
  • IPv4 only: IPv6 is not carried
  • MTU and the rest agreed in the design

Reach

  • Lands at our site nearest you
  • Reaches the other three over our own Layer 2 network
  • Only the services you agree with us get through our firewall

Cover

  • 99.9% uptime, by contract, with automatic credits
  • Covers what is ours: our router, our fibre, our network, our end of a tunnel
  • A failed router replaced by us; in the four cities of our datacenters, the downtime counts against the SLA
  • Both ends monitored on our router or fibre, our end on a tunnel
  • One link as standard; a redundant setup on request

Terms

  • Six-month minimum term
  • When the contract ends, we collect the router and remove the fibre, or switch the tunnel off

Encrypted on every line. European on ours.

The router we install, our fibre and our network between the four sites are ours to answer for, under a contract with a European company that has no US parent above it, and the partner that lays our last mile is European too. The line you already have, and the connection under a tunnel, belong to your carrier, and we cannot choose where it sends your traffic. That is why every way in is encrypted from your site to ours.

When to use Private Link

When a site of yours needs to reach something you run with us, encrypted, routed with your own addresses, and limited to what you agree.

Offices and branches reaching ERP on dedicated servers

Plants and warehouses reaching the systems that run them

Your own datacenter as the main site and ours for recovery, or the reverse

A database of yours that our engineers stream into a broker, over TLS

Your offices reaching a private assistant on our GPUs in Amsterdam

Head office and branches reaching CloudPBX

Your racks in our datacenters and the comms room at head office, on one link

A new office on its own equipment, live over a tunnel in 24 to 48 hours

Tell us where your sites are.

Which sites, what connection each one already has, and what it needs to reach.
An engineer comes back with the way in that fits and how long it takes.

Usually a reply within 24 h

No commitment

An engineer on the call

Things people ask before signing

Straight answers, no upsell.

Our services already have public addresses. Why not run our own tunnel to them?

For one site and one server you can, and your firewall will do it. What Private Link changes is where the tunnel ends: in our network rather than on each server, so one link reaches every service you agree with us, in any of our four sites, instead of one tunnel per machine. Your private ranges are announced to us over BGP under your own ASN, our firewall lets through only what we agreed, and the 99.9% by contract covers our end. If you would rather run no tunnel at all, we install our router at your site and monitor both ends.

Is this the same as AWS PrivateLink or Azure Private Link?

No, despite the name. Those give a service inside one cloud a private address in your own network in that same cloud. Ours connects your sites, meaning offices, plants and your own datacenter, to the services you run with us. If what you need is a private connection from our sites into your own network at AWS, Azure, Google Cloud or Oracle, that is a private interconnect, and we study it per customer. Our direct peering with those clouds at European exchange points is a separate thing again: it carries traffic to their public services, not into your private network there.

Which way in should we pick?

Start from what the site already has. A line you are happy with, and no wish to run the equipment: we install our router on it, configured, in up to 14 days. A site in Madrid, Amsterdam, Munich or Helsinki where you want the line to be ours too: our fibre and our router, in 14 to 35 days, because the fibre has to be laid. Equipment of your own that speaks WireGuard or IPsec: a tunnel from it, live in 24 to 48 hours. Every way in is encrypted and lands at our site nearest you.

What does one link reach?

Only what you agree with us. Each link lands at our site nearest to it, and our firewall lets through the services and destinations we set up together and nothing else. From there our own Layer 2 network reaches the other three sites, so a link that lands in Madrid can reach a server in Helsinki. Our services keep their own addresses, and your private ranges are announced to us over BGP, so each side knows the way back.

How fast can it go?

From 50 Mbps to 10 Gbps, set per link for what the site needs. The rate is best effort, not a guaranteed floor, and on a tunnel your own connection sets the ceiling.

Which routing does it use?

BGP, with your own ASN, public or private. Your private ranges are announced to us, and our services keep their own addresses. It carries IPv4 only: IPv6 is not carried over Private Link. MTU and the other parameters are agreed in the design, site by site.

What happens when the link goes down?

A standard link is a single path from one site of yours to our site nearest it, so while it is down that site has no private path in. Our other three sites are reached through the same link, not in place of it. On our router or our fibre we monitor both ends, and on a tunnel our end. If our router fails, we replace it, and in the four cities where our datacenters are, the time it is down counts against the 99.9%. If a site cannot be without its link, a redundant setup is available on request.

What does the 99.9% cover?

Private Link, by contract, with automatic credits if we miss it: the same figure as every product we tie to an SLA. It covers what is ours: the router we install, our fibre, our network and our end of a tunnel. In the four cities where our datacenters are, replacing a failed router is inside it too. The line you already have, and the connection a tunnel runs over, are your carrier's, and we cannot answer for them.

Who sets it up, and who watches it?

We configure our router, install it at your site, and help you extend your network to it or use it as it is. On our fibre, a European partner lays the last mile and we do the rest. Either way, we monitor both ends. On a tunnel we monitor our end and help you configure yours, and specific parameters or algorithms can be agreed per customer. Support is free, with a 4-hour target response time on support requests, as on everything we sell.

How long does it take?

A tunnel is live in 24 to 48 hours. Our router over the line you already have takes up to 14 days. Our fibre and our router take 14 to 35 days, because the fibre has to be laid first.

What is the minimum term, and what happens when the contract ends?

Six months. When the contract ends, we collect the router and, where there is one, remove the fibre; a tunnel is switched off. There are no prices on this page: you get one in your quote.

Can we have it in place before we move anything?

Yes. You can buy it on its own and connect a site before anything moves. It reaches nothing until a service runs with us, though: a link leads only to services you run with us.

Is it encrypted, and over whose networks?

Every way in is encrypted from your site to ours, and so is the traffic between our four sites. Nothing on our fibre or our network between the four sites runs over a network owned outside the EU, and the partner that lays our last mile is European. The line under our router, and the connection under a tunnel, are your carrier's, and we cannot choose where your carrier sends your traffic: that is what the encryption is for.

Why does it matter where the company is?

Because an order served on the company that runs a network can reach the traffic on it. The router and the network your link lands on are run by DIVERSITY, a European company with no parent company, US or otherwise, so there is no entity above us for a court outside the EU to compel. On your carrier's line, what it carries is encrypted from your site to ours.

Testimonials

What they say about our work

“Our own datacenter is still the main site. Theirs is where we recover, over Private Link.”

Infrastructure lead

Engineering firm, Belgium

What else we operate

Disaster Recovery when your own datacenter is one side of the plan, Colocation when your hardware moves into our datacenters, and Bare Metal for dedicated servers we rack for you.

Shall we talk?

An AI deployment, critical infrastructure, or a quote.

Write or call and you'll get an engineer, not a ticket bot.