1. Connect Your Git Repository
Start by connecting Nomatron to your GitHub repository.
Nomatron listens for job file changes (*.nomad.hcl, variables, templates) and automatically generates a deployment plan.
Each plan shows a clear diff between the current and proposed state — so you can review every change before it reaches your clusters.
- ✅ Git-based automation
- ✅ Versioned configuration
- ✅ Real-time diff and plan previews
2. Review and Approve
Before anything runs, every change passes through Nomatron’s review and approval layer.
- Role-based permissions ensure only authorized users can deploy.
- Audit logs capture every action for compliance and traceability.
- Environment promotion lets you safely move workloads from dev → staging → production.
Nomatron brings Continuous Delivery discipline to Nomad — giving you confidence with every deploy.
3. Deploy via the Control Plane
Once approved, Nomatron securely orchestrates the deployment across your clusters using its control plane.
- The control plane never runs customer workloads — it coordinates them.
- It issues deployment instructions through a secure HTTPS or mTLS channel to Nomatron Agents.
- All communication is outbound from the customer network — no inbound exposure required.
This design helps keep your infrastructure private while still providing practical visibility and operational control.
4. Nomatron Executes Inside Your Network
Nomatron Agents are lightweight, stateless services you deploy inside private networks or cloud environments.
They act as secure bridges between the control plane and your Nomad clusters:
- Maintains outbound-only, encrypted connection
- Authenticates using signed tokens
- Executes plans and reports status back to the control plane
Agents let Nomatron work across public clouds, private data centers, or hybrid setups without exposing internal endpoints.
5. Observe, Roll Back, and Audit
Every deployment is recorded, observable, and reversible.
- View logs, diffs, and job history in one place.
- Use release history to support recovery and rollback decisions.
- Export activity reports for compliance or incident review.
Nomatron combines operational visibility with governance — so you always know what changed, who approved it, and when it happened.
6. Built for Scale and Extensibility
Nomatron’s architecture is designed to support practical enterprise rollout patterns.
- Multi-cluster aware — manage Nomad clusters across environments from one operating layer.
- GitHub-based workflows — connect source changes to plan, approval, and apply workflows.
- Self-hosted operation — keep the operational control plane close to your Nomad estate.
Nomatron stays close to Nomad rather than replacing it with an unrelated abstraction.
In Short
| Step | What Happens | Where |
|---|---|---|
| 1. Connect Git | Nomatron monitors your repo for job changes | Nomatron |
| 2. Review Plan | Diffs and approvals in the Nomatron UI | Nomatron |
| 3. Deploy | Secure plan execution | Nomatron Control Plane |
| 4. Run | Nomatron Agent applies to Nomad | Customer Network |
| 5. Observe | Release history, status, and audit context | Nomatron |
Why It Works
Nomatron was built by a former HashiCorp engineer with over five years at the company — someone who helped build official integrations for Nomad, Terraform, and Vault.
We’ve lived the operational pain points firsthand, and Nomatron solves them through:
- Empathy-driven design — simple, guided workflows for every operator
- Security by default — encrypted channels, audit trails, and strong identity
- Operational clarity — one source of truth for every deployment
Nomatron doesn’t replace Nomad — it completes it.
Experience deployment the way it should be.