Who puts Rikoo in production, and for what.
Six segments where the gap between a prototype and a service is widest. Named references are on the way; the quote further down is a placeholder until ours are approved.
Support on the website and in Slack
A widget in one script tag, a knowledge collection with citations, verified visitor identity so the agent picks up the right customer thread, end-user feedback collected, and a known cost per conversation.
A tooled operations agent
MCP servers to GitHub, Linear, PagerDuty and PostgreSQL over OAuth, secrets in the vault, human approval before a sensitive action in Enterprise, and an audit line for every gesture.
Banking, health, public sector, defence
On-premises or on a sovereign cloud, with European or local models, air-gapped if needed, and a tamper-evident log. The compliance file is written from the architectural invariants rather than from marketing copy.
One platform to deliver at every client
Prototype on the open core, operate several clients on one instance with Enterprise multi-organization, and integrate with what they already run through a published OpenAPI contract.
An agent inside your product
A widget customizable zone by zone, a JavaScript SDK, in-page capabilities behind consent, your own users' identity, and per-customer rebilling in Enterprise.
Getting out of the prototype
A notebook or a personal agent becomes a versioned, tested, gated and traced service, with sub-agents and skills, without rewriting the orchestration.
We stopped arguing about whether teams were allowed to build agents. Rikoo turned the answer into a policy instead of a meeting.
The prototype was never the hard part.
Start with the free edition.
Nothing to sign, nothing to ask. Install it and decide later.