The outcome

Give authenticated users a recoverable AI workspace without exposing provider keys, registrations, conversations, files, or administration surfaces.

Step by step

A workflow you can repeat.

  1. 01

    Define users, tenants, domain, regions, providers, data classes, authentication, registration, database, vector and object storage, retention, SLO, backup, and incident ownership.

  2. 02

    Pin reviewed container images and configuration, deploy PostgreSQL with vector support, private object storage and supported SSO, use HTTPS, and restrict databases and administration to internal networks.

  3. 03

    Store provider and application secrets outside images and source, disable open registration, assign least privilege, separate environments, set resource limits, and redact logs and traces.

  4. 04

    Test login and logout, tenant and file isolation, provider-key leakage, uploads, knowledge retrieval, failed storage, database migration, restore, dependency outage, rate limits, and account removal.

  5. 05

    Canary pinned updates, back up before migrations, verify restore on a separate instance, monitor access and spend, rotate secrets, and delete retired files, sessions, buckets, volumes, and accounts.

Working standard

What good use looks like.

  • Never expose an unauthenticated instance.
  • Back up before every migration.
  • Test tenant isolation and restore.

Official references

Check the current product documentation.