Where OneEnv is headed

OneEnv started with environment variables, extended the same governance model into database structure, API routes, and validation rules, unified how every change gets reviewed under one Branch/Merge flow, then made all of it measurable — scores, history, reports. Here's the full picture of what's shipped and what's next, in the order we're building it. For the unvarnished version — including what's deliberately missing — see the honest roadmap post.

1. 1

   Env governance

   Done

   One change to a shared env value fans out into one notification and a per-service approve/reject checklist before it's live.

2. 2

   DB governance

   Done

   Workspace-scoped DB → Table → Column structure that services can inherit, gated by the same notification/approve/reject flow — plus service-initiated proposals, .sql import, and cross-DB structure sync.

3. 3

   API governance

   Done

   The same one-change, one-notification, explicit-approval model, applied to service-owned API routes — inherited read-only or tracked as a live source by a dependent route — and to their governed request fields.

4. 4

   Validation governance

   Done

   Reusable validation rules assignable to a DB column or inherited directly by a service, with a rule change notifying both audiences.

5. 5

   Branch & Merge review

   Done

   Every governed edit across all four domains stages on one Branch, reviewed once like a pull request — with conflict detection, rebase, revert, and a review comment thread — and merged deliberately.

6. 6

   Governance visibility

   Done

   Computed impact scores and risk levels on every change, a searchable audit History, a per-branch Change Review Center with readiness scoring and impact preview, a workspace error-code catalog, and a Workspace Report with a weighted health score.

7. 7

   API Studio

   Done

   An IDE-style editor for designing service-owned routes: governed request fields, DB and response mapping, validation assignment, and per-user drafts for everything you type — tests, examples, and mock responses included.

8. 8

   Production hardening

   Done

   Automated unit, integration, and browser E2E test suites; a load-testing pass that found and fixed a real scaling bug; workspace archival with export takeout and a gated permanent-delete; a documented backup/restore runbook.

9. 9

   Notification delivery channels

   Done

   Opt-in email and webhook delivery per member, so an approval doesn't require someone to have the app open. In-app stays the source of truth.

10. 10

    Service-account API tokens

    Done

    Scoped, revocable read-only tokens per service, so a CI pipeline can pull an export without borrowing a human's session.

11. 11

    Dependency graph & transitive impact

    Done

    A workspace-wide visual graph of who inherits what — with cycle detection on API source chains — plus a multi-hop blast-radius preview on branch review.

12. 12

    Free and Custom offering

    Done

    OneEnv is free to start (unlimited services and members, the full governance engine), with a Custom contact-us option for complex architectures.

13. 13

    GitHub import

    Done

    Connect a workspace to GitHub once, then import repositories as real Services with their env keys pre-populated — processed through a daily import window.

14. 14

    Workspace-wide search

    Done

    A Ctrl+K command palette searching every governed domain at once — services, env values, DB structure, API routes, validation rules — permission-filtered exactly like every other read.

15. 15

    Mock API governance

    Planned

    Workspace-managed mock APIs for local and CI development, kept in sync with the real, governed contracts.

16. 16

    AI code generation

    Planned

    Generate implementation code in your language of choice directly from governed env, DB, and API definitions.