Products
Tillered is available as a fully managed cloud service or as a self-hosted deployment for offline and restricted environments. Both products share the same core networking and optimisation technology.
Tillered accelerates TCP traffic over long-distance links at the network layer, without changes to your applications or workflows. It's available in two deployment models.
Tillered Self-Hosted
Tillered Self-Hosted is designed for environments where external connectivity, SaaS control planes, or cloud dependencies are not acceptable. Organisations deploy signed binaries directly onto their infrastructure and operate the system independently.
- CLI and declarative YAML compose file management
- Peer-to-peer clustering with encrypted tunnels
- Route-based traffic policies
- No external control plane dependency
- Linux hosts (x86_64 and ARM64)
- Works fully offline in air-gapped networks
Tillered Cloud
Tillered Cloud provides a hosted control plane for deploying and managing Tillered nodes across internet-connected environments. Infrastructure is provisioned using pre-built virtual machine images and managed centrally through the Tillered Hub.
Once deployed, Tillered nodes transparently accelerate TCP traffic between sites. Existing tools and workflows benefit automatically with no application changes.
- Managed via the Tillered Hub
- Pre-built VM images for supported cloud platforms
- Secure node registration and lifecycle management
- Centralised configuration and upgrades
- Operator-driven management (no unattended automation)
Design principles
Tillered is built around a clear separation between the control plane and the data plane. This separation allows the same core networking technology to be deployed in both centrally managed and fully decentralised environments.
- Control plane components manage configuration and coordination
- Data-plane traffic flows directly between nodes
- Optimised traffic is never proxied through external services
- Deployment models differ primarily in control-plane operation
Choosing a deployment model
Both deployment models provide the same core functionality. The appropriate choice depends on operational constraints rather than feature availability.
Not sure which model fits? Talk to our team.
| Consideration | Tillered Cloud | Tillered Self-Hosted |
|---|---|---|
| Internet connectivity | Required | Not required |
| Control plane location | Hosted by Tillered | Customer-operated |
| Operational overhead | Lower | Higher |
| Autonomy and control | Shared | Full |
| Automation | Operator-driven only | Operator or automated |
| Typical environments | Cloud and hybrid | Restricted and air-gapped |