What is OneEnv?
A definition, what it governs, and what it deliberately does not do.
By the OneEnv team · Last updated
Definition
OneEnv is a shared-configuration governance platform. When several services depend on the same value, such as a database host, an API path, a column or a validation rule, OneEnv records those dependencies and puts a review between an edit and its effect. An edit is staged on a branch, reviewed once by an Owner or Admin, merged, and then each affected service approves or rejects the change for itself.
What it governs
- Environment variables (Env Master): a shared key with one value that services inherit.
- Database structure (DB Master): databases, tables and columns that services inherit.
- API routes: routes owned by a service, with request fields, that other services consume.
- Validation rules (Validation Master): reusable rules assigned to columns and fields.
What you get
- An explicit answer to 'which services depend on this?' before you change it.
- One review for a related set of changes, instead of one per edit.
- A per-service decision, so a consumer is never silently changed.
- A record of who proposed, reviewed and approved, on the History page.
What it is not
OneEnv is not a runtime secrets vault or config server. It has no secret rotation, dynamic credentials, SSO/SAML or Kubernetes operator, and it does not push values into running services. It exports configuration for your pipeline to pull. Dev/staging/production tiers do not exist as a concept; each workspace has one flat value per key. See Feature limitations.