Solutions
For in-house development
Requirements for an internal team: files in your repository, hosts described in the model, your own subscriptions.
Who this is for
In your terms
You build internal systems for your own company. They run on your servers, and your agents run on the accounts you already pay for.
You want the requirements, the code and the running hosts described in one place, without a hosted service in between.
Today
What you get today
- Self-hosted: files in your repository, an embedded graph index, no external database.
- Hosts are elements of the model, and the trace level is set per element and host.
- Run-time views show which requirements actually ran.
- Model providers of your choice: the Claude Code CLI on your subscription, API keys through LiteLLM, or local models through Ollama.
- Sources from Jira, GitHub Issues, Slack, Discord and Telegram.
- A remote host for builds and test stands, while coders stay where the subscription is logged in.Pro
- A pool of subscription accounts with failover when one hits its limit, and budget guards.Pro
- Local semantic search over code, without an external service.Pro
- Several projects in one installation, on shared subscriptions with quotas.Pro
- Monitoring: repeating errors in the logs become incidents for an on-duty role.Pro
Coming soon
What is coming
- Account area on the site for seats and subscriptions coming soon
Next step
Start with the open core
Install the open core on a server of your own. Pro is in early access.