Curiosity

Deploy and manage Curiosity Workspace

Install, configure, secure, monitor, back up, and upgrade — for the team running the platform.

For the people who run Curiosity Workspace

These docs are aimed at administrators, SREs, and platform engineers — the team that installs Curiosity Workspace, keeps it running, and stays on the hook when something breaks.

If you're a developer building an enterprise AI app, the starting point is Curiosity Workspace → Build enterprise AI apps. If you're customizing the front-end, custom endpoints, or AI tools, see Workspace Customization.


Pick your path

Install

Pick a delivery platform and bring up your first workspace. Local Docker, full Kubernetes, Windows installer, and per-cloud reference architectures.

Secure

TLS, secrets, JWT keys, ReBAC, token discipline. The baseline that has to be in place before real users sign in.

Identity (SSO)

Microsoft Entra ID, Google, Okta, Auth0, SAML. With group → team mapping for ReBAC.

Production deployment

The full pre-flight checklist: image hygiene, storage, networking, identity, observability, disaster recovery.

Monitor

What to watch, what to alert on, where the metrics live, how to wire it to your existing observability stack.

Back up and restore

Snapshot, ship off-host, restore into a sandbox, and validate. With a quarterly drill template.

Upgrade and migrate

Versioned image tags, schema migrations, environment promotion.

Troubleshoot

Symptom-first guide. Each section walks from "what you're seeing" to the most likely cause and how to confirm.


Reference

Configuration reference (MSK_*)

Every runtime environment variable, with recommended values per environment tier.

Token scopes

The three token types and least-privilege recipes for connectors, exports, and third-party integrations.

Error codes

HTTP status codes, the error envelope, retry policies.

REST API

Built-in routes (auth, SSO, custom endpoint invocation, admin metrics).


Need help?

© 2026 Curiosity. All rights reserved.
Powered by Neko