Plans
One product, three ways to run it.
Pricing will be announced at launch. Until then, tell us your student count and deployment preference, and we will say plainly what each model involves for an institution your size.
Deployment models
Choose who runs it and where.
The software is identical in all three. What changes is who operates it, where the data lives and where the AI runs.
Run by OneRubric
Hosted
A multi-tenant service at your-institution.onerubric.click. Live after a short setup wizard.
Pricing announced at launch
- 7-day trial with institutional sign-in, no card needed
- Data region pinned at signup: US, DE, UK, IN or SG
- Daily snapshots and 7-day point-in-time recovery
- Hosted AI under a no-training, zero-retention agreement
Run by your IT team
Self-hosted
A single-tenant install on infrastructure your institution controls, on premise or in your cloud.
Pricing announced at launch
- Your database, servers and region; no OneRubric sub-processors
- AI on your own Ollama server, with no outside AI traffic
- Source access and a yearly independent audit right
- You decide when to upgrade; there is no kill switch
Run by OneRubric, in your account
Managed
For institutions without spare IT capacity: we operate the self-hosted stack inside your own cloud account.
Pricing announced at launch
- You own the account, the data and the infrastructure
- We run the application, database and AI
- The same privacy posture as self-hosting
- Responsibilities agreed in the contract
Side by side
How the three compare.
| Topic | Hosted | Self-hosted | Managed |
|---|---|---|---|
| Who operates it | OneRubric | Your IT team | OneRubric, inside your cloud account |
| Where the data lives | A region pinned at signup, never moved without 30 days’ notice | Your servers or data centre | Your own cloud account |
| Where the AI runs | Together.ai under a no-training, zero-retention DPA; OpenAI optional, off by default | Mistral 7B on your Ollama server; no outbound AI traffic | Inside your account, as self-hosted |
| Sub-processors | DigitalOcean, Together.ai, Stripe and Paystack, Resend, Sentry | None | Set out in the contract |
| Backups and recovery | Daily snapshots, 7-day point-in-time recovery; RPO ≤ 15 min, RTO ≤ 4 h | Daily pg_dump from the runbook; you own retention; RPO 24 h, RTO 8 h | Shared-responsibility split agreed in the contract |
| Upgrades | Applied by OneRubric | Applied by your operator when you choose | Agreed in the contract |
| Getting started | Same day, after the setup wizard | About fifteen minutes with the provided orchestrator, then the setup wizard | Scoped with your IT team |
In every plan
The whole product, whichever model you choose.
- All seven roles and their scoped screens
- Sign-in with Google, Microsoft Entra or SAML 2.0
- SCIM 2.0 provisioning and magic-link invites
- Private AI: themes, cited answers and briefings
- Action plans with next-term verification
- Executive board pack and per-course PDFs
- Your branding and terminology from admin screens
- Custom evaluation questions per programme
- Canvas and Moodle sync
- Append-only audit log, exportable to CSV
- Full data export at any time, free
- Written answers from the lead engineer within 5 business days
Questions
Before you ask for a quote.
Can we self-host instead of using the hosted service?
Yes. The same software deploys to DigitalOcean, AWS, GCP, Azure or your own on-premise infrastructure. In that model OneRubric the company has no sub-processors and no operational access to your data without an explicit, time-bounded support grant.
What happens to our data if we leave?
You can export a complete, portable copy of your institution’s data at any time, free, regardless of contract status. On the hosted service, tenant data is retained for 90 days after termination so you can request a final export, then purged. Self-hosted customers already hold their own database.
Do you hold SOC 2 or ISO 27001?
Not yet. We follow the practices but do not hold either audit report; both are on the roadmap. Every contract includes source-code access and the right to commission an independent security audit each year. We would rather say this plainly than imply a certification we do not have.
How long does it take to get started?
On the hosted service you sign up, walk a short setup wizard (institution name, sign-in providers, branding) and invite your QA team the same day. A self-hosted production deployment takes roughly fifteen minutes of setup with the provided orchestrator, after which the same wizard brands it and brings it live.
What does it cost?
Pricing will be announced at launch. If you are evaluating now, tell us your student count and deployment preference on the contact page and we will walk you through what each model involves.
Tell us about your institution.
Student count, number of schools, and whether IT prefers hosted or self-hosted. We will reply from a named address with what each model involves.