OC.XSFIRE.COM

Launch a dedicated OpenClaw runtime for your team, with Jan on the same host.

Create a workspace, pay for a dedicated runtime, and move into /oc and /jan without touching deployment tooling. Identity, invites, and member metadata stay on Appwrite Cloud while the runtime stays on your dedicated host.

Member DB Appwrite Cloud Dedicated runtime root xsoc.xsfire.com
Console Host
oc.xsfire.com
Member Identity
Appwrite Cloud
Workspace Runtime Root
xsoc.xsfire.com
Runtime Surfaces
/oc + /jan
Create Account Create Workspace See Launch Path
1. Account
2. Workspace
3. Checkout
4. Runtime
5. Codex
6. Ready
Account Access

Sign up or log in first. The server keeps only the session cookie locally and stores member metadata in Appwrite Cloud.

signed_out
Loading auth config...

Signup is invite-only. Ask the operator for an invite token, then use it once to create your account.

My Workspaces

Workspace is the billing and access boundary. Each completed payment can create one additional OpenClaw runtime under that workspace.

idle
Sign in to load workspaces.
Create Workspace

Hosted Dedicated keeps infrastructure choices hidden. You only choose name, subdomain, and plan.

Waiting for account session.

Select a plan from the list or click a plan card below. Both controls stay in sync.

Checkout & Provisioning

Checkout drives the billing state machine for one runtime order. When payment completes, provisioning starts and the selected runtime should move into running or auth_required.

select_workspace
Select or create a workspace to continue.
Runtime Activation

Verify runtime, paste the Codex callback URL, and run the first smoke. Runtime secrets stay on the tenant server only.

idle
Select a workspace to inspect runtime readiness.
Legacy operator bridge routes are internal-only on this environment.