Skip to content

Private Networking Overview

By default, Sliplane services can be made public (accessible via the internet) or private (only accessible by other services on the same server). With private networking or tunnel solutions, you can:

  • Keep your services private on Sliplane
  • Access them securely through an encrypted connection
  • Connect services across different servers or networks
  1. Deploy a VPN or tunnel client as a private service on Sliplane
  2. Configure it to connect to your private network or tunnel provider
  3. Add your private services as network resources
  4. Connect from your local devices or route traffic through the provider
  5. Access services via their internal hostnames (e.g., my-service.internal)

There are several private networking and tunnel solutions you can use with Sliplane:

SolutionDescription
NetBirdGerman, Open-source, peer-to-peer mesh VPN
TailscaleZero-config VPN built on WireGuard
TwingateZero-trust network access
CloudflaredCloudflare Tunnel client for routing traffic through Cloudflare
  • Security: Services do not need a public Sliplane endpoint
  • Simplicity: No firewall rules or port forwarding needed
  • Flexibility: Access from anywhere through your chosen network or tunnel provider
  • Cost-effective: No need for additional load balancers or proxies