Enterprise — SaaS

The fastest way to start. Caura runs the platform; you only need an account and an API key.

Sign upCopy Anchor Link

1. Go to caura.ai/signin and create an account.
2. Pick a plan from the pricing page.
3. Open Connect › Keys and create a key for your tenant: Create key under Create a key. It starts with mc_. New accounts can also press Create your key in the Connect › Get started checklist.

ConnectCopy Anchor Link

Continue with the Quickstart — pick OpenClaw, MCP, or REST.

Going beyond personal use: per-agent keysCopy Anchor Link

The tenant-scoped mc_ key is fine for a single user or one-off scripts. Any production deployment (a fleet of agents, a multi-user team, anything that needs trust gating or per-agent keystones) should bind each agent to its own agent-scoped credential. Both kinds use the mc_ prefix on the wire — scope is bound at mint time on the credential row. Mint atomically:

curl -X POST https://caura.ai/api/v1/admin/agent-keys/provision \
  -H "X-API-Key: $MC_TENANT_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "agent_id":      "your-agent-id",
    "label":         "human-readable label",
    "initial_trust": 1,
    "initial_fleet": "your-fleet-id"
  }'

One round trip mints the credential, creates the Agent row, sets the trust level, and assigns the fleet. The response includes raw_key (returned once — save it) and agent_row_created: true. Verify with GET /api/v1/whoami using the new credential. Full flow in Per-agent keys.

When the managed deployment fitsCopy Anchor Link

• Zero ops. Caura runs Postgres, the worker, embeddings, and the LLM provider. No on-call rotation, no upgrades, no capacity planning on your side.
• Availability targets. Free runs on a best-efforts basis with no availability guarantee. Paid plans target 99.5% monthly availability of the API and dashboard; this is a target, not a contractual SLA with credit remedies. See the service-level terms for measurement and exclusions.
• Support response targets. Free has community support with no guaranteed response. Pro targets an initial response within 3 business days; Business within 2 business days. These targets use Caura business hours in Israel, Sunday–Thursday, excluding Israeli public holidays. Enterprise/custom commitments are specified in the Order Form. See the service-level terms and pricing page.
• Security and compliance out of the box. SOC 2 controls, audit logs, encryption at rest and in transit, tenant isolation enforced server-side. No security review of your own stack needed.
• Fleet-level governance without wiring. Trust levels, keystones, contradiction surfacing, the Karpathy Loop, and the near-duplicate scan all run for you — flip the switches in Settings › Tenant settings › Features and review what they find in Review › Conflicts and Review › Near-duplicates.
• A working dashboard from day one (Prism) for browsing, curating, and auditing memories. Plus billing, members, agent keys, and tenant management.
• Upgrades and migrations are our problem. New tools, model swaps, and schema migrations roll out on our side without downtime on yours.

When self-host or on-prem fits betterCopy Anchor Link

• Data residency or air-gap requirements. If your data legally can't leave your VPC, region, or facility, see On-prem Enterprise.
• You're already running a Postgres-heavy stack and want to keep one operational footprint. The OSS bundle is Apache 2.0 — see OSS Self-host.
• Hobby / single-machine usage. OSS on a laptop is free and complete.

Same code across all three paths — switching later is a config + migration, not a rewrite.