Rige
For one person who wants their own governed place.
Self-service · shared cloud
- 1 governed domain
- Predefined governance regime
- Shared infrastructure, managed by OpenNube
- MCP included for your agents
- Optional support
Every Rige answer is cited against what your organization decided, who decided it and since when. What changes between plans is where Rige runs, how far it adapts to you and the people around it.
For one person who wants their own governed place.
Self-service · shared cloud
For teams that decide together and need their own approval workflows.
Self-service · shared cloud
Your own instance, in our cloud or on your premises, with people alongside it.
Dedicated instance · cloud or on-premise
Rige taken to your industry: its regulations, its domains and its systems. A project shaped to your organization.
Each proposal is put together with you: users, domains, where it runs, usage and the people you need.
How many people use Rige and in how many governed domains; where it runs — our cloud, a dedicated instance or your data center; how much usage you expect; and how much of our team you want alongside.
We look at it together in a first conversation and you get a written proposal. No list price to negotiate down from.
We let you know at 50, 80 and 100% of your month's usage. If it runs out, Rige offers you more. There are no automatic overage charges, and an answer in progress is never cut.
Browsing, reading and approving in the platform use nothing. Your actual usage is always visible in the product.
Claude, ChatGPT or your own agents query and propose in Rige over MCP, with your permissions. What they register waits for the approval your regime sets. It is included in every plan, with no per-call charge, with up to 3 agents per user.
Each agent has its own credential, which you can revoke from the administration. The call limits grow with the plan.
| Rige | Rige Pro | Rige Max | Rige for Industries | |
|---|---|---|---|---|
| Where it runs | Shared cloud | Shared cloud | Dedicated instance or on-premise | Dedicated cloud or on-premise |
| Data residency | — | — | Yes | Yes |
| Integration with your systems | — | — | Standard connectors | Custom |
| Identity | Rige account | Rige account · SSO on request | Your identity provider | Your identity provider |
| Governance regime | Predefined | Your own workflows | Shaped with you | Shaped with you + industry modules |
| MCP agents | 3 per user | 3 per user | 3 per user | Set by the project |
| People | — | Support | Onboarding and support | Implementation team and technical lead |
| How you start | By invitation, 30 days | Upgrade inside your workspace | A conversation and a proposal | A project with us |
Because two organizations rarely need the same Rige: users, domains, where it runs and the people around it change the proposal. We would rather put together the right one with you than make you fit a list.
No. Rige is by invitation, with 30 days to try it with your own knowledge. When they end, you can export everything you loaded.
Yes. Rige Max and Rige for Industries can run on-premise: the same Rige, installed in your infrastructure. Content, database and attachments stay there; AI requests go to the model provider we agree on, and identifiers can be pseudonymized before they leave.
Yes. From Rige to Pro is a change in the same account. From Pro to Max we take you through a migration to your own instance.
It is stored in one place, your company's: in Rige Max, in a dedicated instance with the residency you need, or on your premises. To answer, Rige uses AI model providers; we tell you which ones before we start.
We look at how your organization decides today, which questions it still can't answer and where Rige has to run.
Book a conversation