Features

Everything behind your office's static IP

From launching the gateway to knowing when a tunnel drops, TunnelYard covers it in one dashboard.

1Launch a serverDedicated instance, static IPFrankfurt · 203.0.113.102Add a tunnelSettings matched to the peerIKEv2 · AES-2563Export the peer configCisco, Fortinet, MikroTik…branch-fw.conf4Monitor every tunnelStatus, traffic and logsUp

Launch a gateway with its own static IP

Every TunnelYard gateway is a dedicated server with its own static public IPv4 in the city you pick. It's ready in 10–15 minutes.

  • Dedicated, never shared
  • 38 locations in 20 countries today
  • Ready in 10–15 minutes

Connect your firewall over IPsec

Add a tunnel for each office with its public IP and LAN subnets. TunnelYard generates the key and the IKEv2 settings: start from the Standard, Modern or Compatible preset, or set custom proposals on Enterprise.

  • IKEv2, policy-based, a pre-shared key per tunnel
  • Standard, Modern and Compatible presets
  • One tunnel per office, up to your plan's limit

Decide what goes out

Firewall rules apply to the traffic from your offices through the gateway, and P2P and BitTorrent blocking comes with every plan.

  • Allow and deny rules by direction, tunnel, subnet, protocol and port
  • P2P blocking set to Off, Log only or Block
  • Rule logging and hit counters on Enterprise
#MatchActionHits
1branch-tlv → 10.10.0.0/16 · TCP 443Allow1,204
2plant-ot → 10.10.0.0/16 · TCP 502Allow318
3plant-ot → any · anyDeny57
P2PAll tunnels · BitTorrentBlock12

Hand your firewall a config that works

Export a ready-to-paste configuration for your office firewall, generated from the tunnel you defined, so both ends always agree.

  • Cisco, Fortinet, Palo Alto, Juniper, MikroTik
  • pfSense, OPNsense, Ubiquiti, OpenWrt, or any other IKEv2 device
  • Re-export any time the tunnel changes
Export configOpenWrt (strongSwan swanctl)
connections {
  tunnelyard-hq {
    version = 2
    remote_addrs = 203.0.113.10
    proposals = aes256-sha384-ecp384
    local {
      auth = psk
      id = branch.example.com
    }
    remote {
      auth = psk
      id = 203.0.113.10
    }
    children {
      hq-net {
        local_ts  = 192.168.20.0/24
        remote_ts = 10.10.0.0/16
        esp_proposals = aes256-sha384-ecp384
        start_action = start
      }
    }
  }
}
# secrets section exported separately

Know when the tunnel drops, and why

Live status for every tunnel, traffic graphs, and logs you can read without SSH-ing into anything.

  • Tunnel status (Up, Down, Stopped) at a glance
  • Traffic and uptime per tunnel over time
  • Alerts when a tunnel has been down for 2 minutes
TunnelLast rekeyTraffic (24h)Status
hq ⇄ branch-ams12 min ago18.4 GBUp
hq ⇄ branch-tlv41 min ago6.2 GBUp
hq ⇄ warehouse3 h ago0.9 GBUp
09:41:07 hq ⇄ branch-tlv IKE_SA established, IKEv2, AES_CBC_256
09:41:07 hq ⇄ branch-tlv CHILD_SA installed 10.10.0.0/16 === 192.168.20.0/24
09:41:08 tunnel up, DPD every 30s
Technical details

Standards-based IPsec, with sensible defaults

Strong suites are on by default, with a Compatible preset for peers that need it.

Key exchangeIKEv2
EncryptionAES-256-CBC (Standard, Modern and Compatible presets; custom proposals on Enterprise)
Integrity and PRFSHA-256, SHA-384, SHA-512
Diffie-Hellman groups14, 19, 20, 21
AuthenticationPre-shared keys, one per tunnel
Tunnel typesPolicy-based, with static routes to your LAN subnets
TrafficOutbound internet from your LAN subnets, leaving from the gateway's static IP. Inbound connections to your office are not forwarded.
IP versionIPv4 (IPv6 is coming)
ResilienceNAT traversal (NAT-T), dead peer detection (DPD), automatic rekeying
Custom proposalsIKE and ESP proposals, lifetimes and dead-peer detection (Enterprise)
FAQ

Questions about IPsec features

Which IPsec settings are supported?

Tunnels use IKEv2 with AES-256 and a pre-shared key per tunnel, generated for you and rotated any time. Pick the Standard, Modern or Compatible preset to match your firewall; on the Enterprise plan you can also set custom IKE and ESP proposals, lifetimes and dead-peer detection.

Does TunnelYard support IKEv1?

No. TunnelYard uses IKEv2, which current firewalls and routers all support. Our article IKEv1 vs IKEv2 explains the differences and how to move an older device to IKEv2.

Which traffic goes through the gateway?

Outbound internet traffic from the LAN subnets you add to the tunnel. It leaves from the gateway's static IP and the replies come back the same way. Tunnels are policy-based with static routing; inbound connections to your office and traffic between your offices are not carried.

Can TunnelYard generate the configuration for my firewall?

Yes. You export a ready-to-paste configuration generated from the tunnel you defined, for Cisco, Fortinet, Palo Alto, Juniper, MikroTik, pfSense, OPNsense, Ubiquiti and OpenWrt, plus a settings sheet for any other IKEv2 device. Re-export it whenever the tunnel changes, so both ends always agree.

Does it work behind NAT, and what happens when the office line drops?

NAT traversal (NAT-T) lets the tunnel work when your firewall sits behind NAT, dead peer detection (DPD) notices when the office stops responding, and keys are renewed automatically. When the tunnel has been down for 2 minutes you get an alert, and a recovery message when it is back.

Is IPv6 supported?

Not yet. Gateways, tunnels, the static IP and firewall rules are IPv4 today. IPv6 support is coming in a future version.

Get a static IP for your office

Launch a gateway, connect your firewall, and allow-list one IP today.