Our Honest Roadmap
We'd rather tell you what OneEnv doesn't do yet than let you find out the hard way. Here's the current, honest list — grouped by how much it should actually worry you.
Recently shipped
Governance visibility
impact scores + risk levels on every change, the searchable audit History, the per-branch review center, branch revert, and the Workspace Report with health score
Automated test suites
unit + integration (against a real Postgres) + real-browser E2E over the full governance loop, plus a load-testing pass that found and fixed a real scaling bug
Workspace archival & takeout
archive (reversible), a resolved-config takeout bundle, and permanent deletion gated behind a 30-day grace period
Masked-secret re-save guard
re-submitting a form containing a masked secret used to overwrite the real value with the mask string — now detected and rejected
Archive-integrity cascade
archiving a DB/table now cascades to children and cleans up stale inheritance/relation rows — nothing points at structure that no longer exists
Branch review comments
a comment thread on every branch, including a formal Owner/Admin 'request changes' signal — the decision itself stays binary
Outbound notification delivery
opt-in email and webhook delivery per member, wired into branch submit and merge — in-app stays the source of truth
Service export tokens
scoped, revocable per-service tokens so a CI pipeline can pull an export without a human's session
Workspace-wide dependency graph
a real, unrooted graph of every governed entity and how it connects, plus a per-branch blast-radius preview up to 5 hops out
GitHub import
connect a workspace to GitHub and import repos as real Services with env keys pre-populated, processed through a daily import window
Workspace-wide search
a Ctrl+K palette over every governed domain at once — services, env values, DB structure, API routes, validation rules
Actively being hardened
Catalog browsing isn't permission-scoped yet
Env/DB/Validation Master pages are membership-gated only, not per-service — visibility scoping covers Services, Notifications, History, and Reports so far
No restore for archived DB/API/Validation masters
services and workspaces can be un-archived; those three domains can't yet
Audit trail doesn't cover everything
governed changes, approvals, and overrides are recorded — a role change or a plain create/rename/archive still isn't
Impact analysis is one hop at score time
the risk scorer counts directly affected services; the dependency graph above is the multi-hop view, but it doesn't feed back into the score itself
Known, deliberate limitations
No export surface for DB structure
DB Master is governance/documentation only, by design
DB columns hold no value
purely structure — key, type, description, secret flag — an earlier design gave columns their own value and that was removed on purpose
Renames are silent
consistent with 'creating doesn't notify' — but a real gap for dependents
Revert covers value changes only
structural creates/deletes are skipped and reported, not mechanically inverted — undoing those is a decision
Parts of API Studio are still mock
'Send' returns a canned response, and the environments/variables/history widgets are UI-only — labeled as such, never pretending
No auto-purge timer
a workspace eligible for permanent deletion still requires an Owner to explicitly trigger it — nothing deletes governance history on a clock
On the roadmap
- Slack, on top of the email/webhook delivery channels that already ship
- SSO/SAML against a corporate identity provider (today it's email OTP only)
- Pagination on the remaining list endpoints — notifications paginates server-side, but env/DB/validation/branch lists still return everything at once
- Feeding the dependency graph's multi-hop reach back into the impact score itself, not just showing it alongside
None of this is hidden in a backlog tool nobody can see — it's the same list our own team works from, and it changes as items ship. Everything in "Recently shipped" above started its life on it.