Pricing
Self-hosted by design. You bring the cloud, the model keys, and the data — Oracus.ai runs inside your network, and pricing scales with the repositories you connect.
Community
For tinkerers and tiny teams
Free
Self-hosted · access by request
1 repository
- ✓ Files, Jira, and JUnit ingest
- ✓ Single team
- ✓ Bring your own model keys
- ✓ Community support (GitHub)
Team
Small engineering orgs
Contact us
Per-instance, billed yearly
Up to 10 repositories
- ✓ All connectors (Jira, JUnit, Confluence, OpenAPI, GitHub)
- ✓ Slack bot
- ✓ Single team
- ✓ Email support
Business
PopularMid-size orgs with compliance needs
Contact us
Per-instance, billed yearly
Up to 50 repositories
- ✓ Everything in Team
- ✓ Multi-team isolation + RBAC
- ✓ SSO / SAML / SCIM
- ✓ Audit log
- ✓ Priority support
Enterprise
Large or regulated organizations
Contact us
Custom contract
Unlimited repositories
- ✓ Everything in Business
- ✓ SLA-backed support
- ✓ BYOC deployment (your VPC)
- ✓ Data residency + customer-managed keys
- ✓ Custom retention + custom connectors
- ✓ Named customer success manager
Common questions
- Why is pricing per repository?
- Repos track the size of your engineering organization more honestly than seats — and Oracus.ai shows up in Slack, so seat metering would just discourage adoption. Bigger orgs have more services; bigger orgs pay more.
- Do users count against the price?
- No. Once Oracus.ai is connected to your Slack workspace, everyone who needs an answer can ask one. We don't meter people.
- What about model costs?
- You bring your own keys for OpenAI, Anthropic, Ollama, or any OpenAI-compatible provider. Token spend lands on your provider bill, not ours — no markup, full transparency.
- Where does the data live?
- On infrastructure you control. Oracus.ai is self-hosted. Tickets, specs, embeddings, and chat history never leave your network.
- Need something different?
- Custom connectors, on-prem appliance, regulated-industry deployment — write to hello@oracus.ai and tell us about it.