> For the complete documentation index, see [llms.txt](https://docs.visdom.virtuslab.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.visdom.virtuslab.com/visdom-control-plane/roadmap.md). # Roadmap Where the Control Plane is going, in the order we expect to build it. Today the Control Plane decides who may do what in the coding products. The direction is wider: one place that decides who may use AI at all, on what, within which budget and under which policy, for every product and every channel, the IDE, background agents, pull request review and the AI Gateway alike. The items below are grouped by horizon, not dated. {% hint style="warning" %} Roadmap items are direction, not commitments. Order and scope can change. What ships is listed on [Available today](/visdom-control-plane/available-today.md). {% endhint %} ## Next * **Teams.** A team as a first-class object: members, a project set and roles granted to the team rather than person by person. The page exists in the UI and is hidden until the model behind it does. * **Service accounts and API keys.** Machine identities managed in the Control Plane instead of only in Keycloak, with an owner, a scope and an expiry. * **Audit trail.** Every administrative change, a grant, a revoked access, a new repository, a replaced token, written as an event with who, what and when, and exported to AI Tracing's signed chain. * **External secret manager.** Values kept in the organisation's own store (Vault through External Secrets Operator, or a cloud KMS) with the Control Plane holding references; a key ring so the master key can rotate without a restart. * **Helm chart.** The Control Plane installed with the rest of the platform from one umbrella chart, with SBOM and signed images. * **Managing the AI Gateway.** Teams, virtual keys (owner, scope, expiry, rotation) and budgets issued from the Control Plane and enforced by the LLM gateway; a catalogue of approved models and MCP servers; one kill switch for a model, a provider, an MCP server or a tool that reaches both gateways at once. * **Repository metadata.** Owner, application and system fields on a repository, so policies and reports can follow the organisation rather than the URL. ## Later * **Organisation hierarchy from the directory.** Departments and teams read, never written, from Entra ID or LDAP, with deprovisioning following the directory. * **Inherited budgets and policies.** A limit set on a department applies to its teams unless narrowed; a lower level can narrow what is allowed but never widen it. Alerts at a threshold, a hard stop at the limit, and a request-for-more flow. * **Delegated administration.** An administrator for a subtree of the organisation, not only for the whole workspace. * **Policy Gate.** The runtime decision in front of every model call, tool call and agent action: allowed or not, and why, with the decision written to AI Tracing. Policies as code, reviewed in Git, deny by default. * **High availability.** Two or more replicas with coordination in PostgreSQL, and rolling upgrades. * **Role dashboards.** Views for the security officer, the platform owner and FinOps, built on the same data the products already produce. ## Exploring * **Multi-workspace.** The data model already carries a workspace identifier; one Control Plane serving several isolated workspaces is a question of demand. * **An access report across products.** *What can this person reach, everywhere*, in one answer. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.visdom.virtuslab.com/visdom-control-plane/roadmap.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.