Enterprise modules
What the Enterprise license adds, module by module. Each module is separable, and the platform runs without any of them.
The Community edition is under the AGPL-3.0 and complete on its own. The Enterprise modules are under the Rikoo Enterprise License, and running them in production requires a signed license that names the modules it grants. They are separable by construction: a module that is not installed, or not granted by the license, leaves the platform running with that feature unavailable. The instance still starts.
- Single sign-on: OIDC and SAML, configured per organization, with verified domains, just-in-time provisioning and an option that makes SSO the only way to sign in to the organization, except for one designated owner who keeps a password.
- Human approval: a run pauses before a tool call that needs approval, and waits for a person's decision on the Approvals screen. It goes dormant instead of holding a worker.
- Publication gates: a version is pinned to
liveonly if the agent's test suites reach their pass threshold.testis not gated, so a version can still be tried there at once. - Full audit: filters on the audit log, CSV export, and a retention period (365 days by default) enforced by a purge that records itself in the audit log.
- Source connectors: crawl a website, or sync from Notion and Confluence, with scheduled re-synchronization and tokens held in the vault.
- Several organizations: more than one organization on the same instance. The Community edition allows one.
- Per-organization trace export: each organization sends its traces to its own collectors, set on the Export OTLP screen, alongside the operator's collector.
To install the Enterprise images and activate a license, see Enterprise license.
When a license expires, or stops granting a module, the module stops on its next use, without a restart, and the instance continues as Community. What was created with the module stays in the database, and the AGPL-3.0 core keeps running exactly as before.