Self-Hosted Gateway
The Self-Hosted Gateway is the Axemere Gateway running on your own infrastructure, connected to the Axemere Control Plane and managed from the Cloud Console. Every self-hosted gateway registers to your org this way: your nodes appear in the Cloud Console's Gateways page, policies and credentials are pushed automatically, and usage flows into analytics and billing.
Unlike the Managed Gateway, you own and operate the infrastructure. Axemere provides the Control Plane, Cloud Console, and support.
When to use the Self-Hosted Gateway
- Your organization requires data to stay on-premises or in your own cloud account
- You need network-level control (VPC, private endpoints, firewall rules)
- You want managed fleet visibility and Cloud Console governance without handing over infrastructure
How it works
- You install the gateway binary on your infrastructure (VM, container, Kubernetes)
- The gateway connects to the Axemere Control Plane at startup using a bootstrap token
- From that point, the Cloud Console manages policies, credentials, and analytics; no SSH required
Getting started
| New install, connect to the Control Plane in under 5 minutes | Self-Hosted + CP Connected |
| Install by OS: macOS, Linux (Debian/RHEL), Windows (WSL2) | macOS · Linux — Debian · Linux — RHEL · Windows |
| Deploy: Docker, Kubernetes, cloud VMs, architecture and config reference | Deployment and Operations Guide |
Related: Cloud Console — Gateways | Managed Gateway