Security And Access

Questions about approvals, RBAC, auditability, and how teams control access and change in Nomatron.

Does Nomatron support approvals and RBAC?

Yes.

Approvals and RBAC are core parts of the product, not bolt-on conventions. Nomatron includes:

  • role-based access control;
  • built-in and custom roles;
  • assignment by user or group;
  • approval policies;
  • audit logs; and
  • environment-aware promotion and review workflows.

Does Nomatron keep an audit trail?

Yes.

Nomatron is designed to provide visibility into who changed what, who approved what, and how deployment operations progressed over time.

Can I manage Nomatron as code?

Yes.

Nomatron has a Terraform provider, an API, and a CLI. Teams can choose the interface that best fits the workflow:

  • GUI for interactive operations;
  • CLI for scripting and automation;
  • API for custom integrations; and
  • Terraform for declarative management of Nomatron resources.

Does Nomatron support private-network connectivity without exposing Nomad directly?

Yes.

That is one of the main reasons the Network Agent exists. It lets teams keep clusters in private networks while still connecting them to the Nomatron control plane through an outbound gRPC path.

Can I control access differently across organizations and environments?

Yes.

Nomatron’s model is designed for scoped control. Access and approval policy can be shaped around global responsibilities, organization boundaries, application ownership, and environment-specific delivery controls.

Is security only about login and permissions?

No.

For Nomatron, security also includes:

  • approval workflows;
  • auditability;
  • deployment traceability;
  • environment separation;
  • TLS and private-network design; and
  • operational hardening of the control plane itself.

For that side of the story, contact us during private beta and we can share the current production hardening guidance.