Tillered
← All products

Tillered Self-Hosted

A decentralised, offline-capable deployment model for restricted or regulated environments.

Overview

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.

Nodes form a peer-to-peer control fabric. Management commands and API requests can be issued to any node, allowing the system to be built, configured, and operated without a central hub.

This deployment model is intended for regulated, restricted, or disconnected environments where control, auditability, and autonomy are required.

Key characteristics

  • Customer-deployed, signed binaries
  • License-based activation
  • Decentralised peer-to-peer architecture
  • No external control plane dependency
  • Suitable for offline and air-gapped networks
  • Supports operator and automated management via any node

Architecture

In Tillered Self-Hosted deployments, there is no externally hosted control plane. All nodes participate equally in a decentralised control fabric operated entirely within customer infrastructure.

Tillered Self-Hosted architecture An operator or automation system can connect to any node in the Tillered platform. Four nodes form a full mesh topology with no central control plane. Operator / Automation connect to any node Tillered Platform Node A Node B Node C Node D
No external control plane. All nodes participate equally in a decentralised peer-to-peer control fabric.
  • Offline and air-gapped operation
  • No dependency on external services
  • Resilient to individual node failure
  • Suitable for restricted and regulated environments

Management model

Tillered Self-Hosted does not require a central management service. Operators interact with the system by issuing commands or API calls to any reachable node. This approach enables:

  • Operation in disconnected environments
  • Resilience to individual node failure
  • Flexible deployment topologies
  • Incremental system build-out

Licensing

Self-hosted deployments use a license-based activation model. Licenses are issued to customers and validated locally by the deployed binaries.

This allows systems to operate without contacting external services while still providing clear entitlement and version control.

Who this is for

  • Government and defence environments
  • Critical infrastructure operators
  • Highly regulated industries
  • Disconnected or intermittently connected networks
  • Organisations requiring full operational autonomy

Getting access

Tillered Self-Hosted deployments are provisioned through a licensing process. Binaries and documentation are provided directly to customers for internal deployment.