Skip to main content
To run a production-grade instance of the Worlds Platform, configure the following infrastructure and services.

​
Provision infrastructure

Collect the necessary API keys and credentials for each service:
  • Identity, via WorkOS: Set up AuthKit and retrieve WORKOS_API_KEY, WORKOS_CLIENT_ID, and WORKOS_COOKIE_PASSWORD.
  • Compute, via Deno Deploy: Generate a personal access token.
  • Storage, via Turso: Retrieve TURSO_API_TOKEN and TURSO_ORG.
  • AI models, via OpenRouter: Retrieve OPENROUTER_API_KEY.
Protect your WORKOS_COOKIE_PASSWORD and TURSO_API_TOKEN securely. These keys guarantee admin or root access to identity management and persistent storage.

​
Deploy the console

The console is a Next.js application. Deploy it to Vercel, Netlify, or a VPS.
1

Import

Import your repository into Vercel.
2

Configure

Set the environment variables retrieved in the previous step.
3

Verify

Ensure NEXT_PUBLIC_WORKOS_REDIRECT_URI matches your deployment callback URL.

​
Orchestrate worlds

Once the console is running:
1

Log in

Access your console and log in via AuthKit.
2

Create an organization

Define your organization within the console.
Worlds Console dashboard
3

Automatic provisioning

The platform will automatically provision a Turso database, deploy a Deno Deploy app, and link them together.

​
Cloud embeddings with OpenRouter

Production environments utilize OpenRouter for cloud-based embeddings by default.
1

Generate API key

Visit OpenRouter to get an API key.
2

Configure console

Add OPENROUTER_API_KEY to your console environment.
3

Verify injection

The console automatically injects this key into new world instances.