Philosophy

Simple tools for complex problems

We built Rabtly out of frustration with overcomplicated VPN setups, cloud vendor lock-in, and tools that treat your data as a product. Here is what we believe.

Why we exist

Connecting infrastructure securely should not require a PhD in networking or a five-figure annual contract. The tools that exist either ask you to trust a black box with your network traffic, lock your configuration in a proprietary format, or charge per-seat fees that scale painfully as your team grows.

WireGuard proved that modern cryptography can be simple, fast, and auditable. Rabtly is the control plane that WireGuard deserves — one that gets out of your way, respects your privacy, and is honest about what it does with your data.

Our principles

01

Simplicity over features

We would rather do one thing exceptionally well than ten things adequately. Every feature in Rabtly earns its place by solving a real problem for real users. We remove things that add complexity without adding value.

02

Privacy by default

Privacy is not a setting you enable. Your traffic never touches our infrastructure — WireGuard is end-to-end encrypted between your nodes. No telemetry is collected without your knowledge. Self-hosting is always an option, and always will be.

03

Open protocols, no lock-in

Rabtly is built on WireGuard, the Noise protocol framework, and standard HTTPS APIs. Your nodes speak WireGuard — a protocol that will outlast any vendor. You can migrate away at any time, and we make that easy on purpose.

04

Developer first

The CLI, the REST API, and the dashboard are all first-class interfaces — not an afterthought. If something takes three clicks in the UI, it should take one command in the CLI. If it is in the dashboard, it is in the API.

What we refuse to do

Principles only mean something when they constrain behavior. Here is what we commit to never doing:

  • Collect data we don't need to operate the service
  • Sell or share your data with advertisers or data brokers
  • Build dark patterns that make cancellation difficult
  • Hide pricing or use bait-and-switch tier structures
  • Lock your configuration in a proprietary format
  • Require an agent that phones home unnecessarily