Feature limitations
The honest list.
By the OneEnv team · Last updated
Not built, and not planned as part of the current product
- Runtime secrets delivery, secret rotation, dynamic credentials.
- SSO/SAML and a Kubernetes operator.
- Environment tiers (dev, staging, production) inside a workspace.
- Pushing values into running services; propagation is a decision and export is pulled.
- Reading your source code or observing traffic to find consumers.
Partially built
- API Studio: routes, fields, mappings and drafts are real; Send, test results, environments, history and activity panels are simulated or mock.
- Branch review: approve or reject only. No comments, no request-changes, no partial approval.
- Impact analysis: one hop at merge time. The graphs are read-only views.
- Revert: update-type changes only; creations and deletions are skipped and reported.
- Migration preview: generated text for columns only; nothing is executed.
- Notification delivery by email or webhook: opt-in, best-effort; in-app is the source of truth.
Trade-offs to expect
- Governance adds a step. Reserve it for values with real fan-out.
- A service whose owner never answers stays on its last approved value. Decide who may act on its behalf.
- The dependency data is only as accurate as the inheritance and source links your team records.
- Archived names still reserve a key; you cannot reuse them.
Choose another tool when
You need a vault, rotation or runtime injection (use a secrets manager). You have a single service (a .env file in version control is enough). You need contract testing against live traffic (use a contract-testing tool). See also Who should use OneEnv?