Self-hosted custody
Keep memory, source files, vectors, graphs, jobs, and model credentials inside infrastructure the organization controls.
Enterprise
Re:Yi can serve individuals and organizations, but enterprise rollout needs the same principle at a larger scale: explicit ownership, clean operations, auditable connections, and no surprise data movement.
Keep memory, source files, vectors, graphs, jobs, and model credentials inside infrastructure the organization controls.
Use the private Admin surface for accounts, releases, docs, remote connection preflight, audit, and operational evidence.
Install, update, rollback, backup, restore, disable, and uninstall through explicit checks instead of hidden side effects.
Allow Local MCP, Provider Gateway, SDK, and application access only when permission and audit boundaries are clear.
Admin boundary
The public site should help people understand Re:Yi and start safely. Private operational tasks stay in Admin, and machine-local changes stay in Control Center so enterprise environments can recover cleanly.