Roadmap
This page describes what's coming to Phillip, Tara, Ryoma, and Bandum. Items marked coming soon are planned and are not available yet. We don't promise specific dates, because the order can change as real users give feedback. For what has already shipped, see the Changelog.
In progress
The biggest effort right now is turning Tara into a shared service where any team signs up, creates an organization, and invites its own people. Organizations, roles, seats, and invitations are in place. Since 7 November every resource has an owner, a person or an organization, and a version that passes the automatic scan is released without a manual review. Sign-in works with GitHub, Google, an email link, or your own organization's SSO, and people join through an invitation, a verified email domain, or your GitHub organization.
The other effort is moving Tara and Ryoma to a production environment that many users share. The Helm chart is ready. What remains is installing on a real cluster over HTTPS, verifying that Claude Code can download packages from users' machines, and placing Grafana behind the internal network. When that's done, the first team will share a single Tara and a single Ryoma from their own machines.
Local Bandum is still being streamlined. The goal is for Bandum to take its configuration from Tara on its own and to sync with each user's own token instead of a service token placed on each machine.
Guardrails is being tested on real machines. The install command works on macOS, Linux, and Windows, but on Windows only file writing has been checked, and it hasn't run on a real Windows machine. We also need a few weeks of real use to measure the number of false-positive blocks before we tune the rules.
Coming up
Ryoma will read tasks from work management systems such as Jira, through the tracker kit, whose contract and Jira kit already exist. When the connection is done, teams that use Jira can still see AI cost by task and by sprint right in Ryoma. Ryoma will also compute the ratio of users to an organization's number of developers, once a reliable source for headcount exists.
Bandum will have a table of time spent in each task state.
The knowledge base will search Vietnamese better. The plan includes adding BM25, reranking results, reading PDF documents, and an evaluation set for search quality. Per-project read permissions are also in the plan.
Phillip will have ph forge doctor check Guardrails's managed settings and hook server as well.
Coming soon: sign-in and joining
- SAML. For organizations whose provider doesn't speak OIDC.
Coming soon: guardrails and dashboards
- Metrics in the Portal (Projects pages). Flow, AI, task health, and at-risk tasks for your organization and each project, read in one place in the browser without Grafana. Guardrails counts sit next to the policy in Settings.
- More for paid plans. The Team plan is available now (see Pricing). Private projects and a signed audit log export are on Team, and SCIM provisioning is on Enterprise (see Pricing). Planned on top of that: SAML as a native sign-in and custom roles. Until then SAML-only providers connect through an OIDC bridge (guide).
Under consideration
The items below make sense, but we haven't decided whether to do them or when.
Phillip could switch models automatically by task type, for example a reasoning model for design and a code-generation model for writing code, instead of you choosing by hand with ph model use.
Tara could support signing keys stored in dedicated hardware (HSM), alongside Vault and OpenBao as it does today. The network permissions of kits that run on the server also need tightening once Node.js has a stable mechanism for it.
Further out, the platform could support AI coding tools other than Claude Code, run self-hosted models, and have its own evaluation suite for agents. These are directions, not commitments.
Want something sooner?
The order above changes with feedback. If an item affects your team's daily work, tell your organization's Owner or Admin, or see how to get in touch at Contact.