Do I need to self-host Nomatron?
Nomatron is designed to run in the customer’s own environment.
The docs cover:
- binary installation;
- Docker deployment;
- Nomad deployment; and
- supporting components like PostgreSQL, load balancers, and the Network Agent.
Can Nomatron run in private environments?
Yes.
Nomatron supports private-network operation patterns, including the Network Agent for clusters that are not directly reachable from the Nomatron server.
What is the Network Agent for?
The Network Agent lets Nomatron manage Nomad clusters that live inside private networks.
Instead of requiring direct inbound connectivity from the Nomatron server to the Nomad API, the agent opens an outbound gRPC connection back to Nomatron and brokers cluster access from within the private environment.
Does Nomatron support high availability?
Yes.
Nomatron is designed to support multi-server deployments behind load balancers, with PostgreSQL as the shared system of record.
The production docs recommend:
- multiple Nomatron servers;
- HA PostgreSQL;
- proper TLS;
- health checks; and
- placement patterns that avoid putting all server replicas on one failure domain.
Can I run Nomatron in air-gapped or offline environments?
Nomatron supports offline licensing patterns, but they are not the default deployment model.
Offline licensing is an Enterprise Plus pattern and requires a license relay inside the customer environment. Most deployments should assume connected licensing unless they explicitly need the offline model.
Does Nomatron require me to redesign how I already run Nomad?
Not necessarily.
Nomatron is usually adopted on top of an existing Nomad estate. The main shift is not the runtime itself, but the control path around deployments: approvals, variables, environments, promotion, and access control become explicit and repeatable.
Is there a fast way to evaluate it locally?
Yes.
During private beta, request early access and we will share the current evaluation path for your environment.