Standalone API host
Xoro now owns the website operating model.
The standalone API and standalone web app are no longer placeholders. They are the active boundary for hosted website control-plane behavior.
Privy is not wired into the standalone app yet, so authentication still depends on the shared session flow.
Current ownership mode
Customer-facing contract already extracted
No compatibility fallback configured
Standalone Xoro runtime
These product layers now run inside the standalone app and API rather than the old Planck admin host.
Tenant boundary, identity linkage, and workspace-scoped operations.
Sites, environments, artifacts, and source metadata for hosted ownership.
Queued deployments, environment state, promotion, and rollback primitives.
Verification records, routing targets, and environment-linked domains.
Remaining compatibility edges
The product boundary is correct now. The remaining work is extraction of the last shared services.
Current API surface
This is the route ownership published by the standalone Xoro service itself.
/api/v1/me/api/v1/workspaces/api/v1/api-keys/api/v1/agent-tokens/api/v1/sites/api/v1/sites/:siteId/api/v1/sites/:siteId/env-vars/api/v1/sites/:siteId/service-bindings/api/v1/artifacts/api/v1/releases/api/v1/releases/:releaseId/promote/api/v1/deployments/api/v1/deployments/:deploymentId/api/v1/deployments/:deploymentId/execute/api/v1/deployments/:deploymentId/logs/api/v1/domains/api/v1/import-sources/api/v1/import-runs/api/xoro/me/api/xoro/workspaces/api/xoro/api-keys/api/xoro/agent-tokens/api/xoro/sites/api/xoro/sites/:siteId/api/xoro/sites/:siteId/env-vars/api/xoro/sites/:siteId/service-bindings/api/xoro/artifacts/api/xoro/releases/api/xoro/releases/:releaseId/promote/api/xoro/deployments/api/xoro/deployments/:deploymentId/api/xoro/deployments/:deploymentId/execute/api/xoro/deployments/:deploymentId/logs/api/xoro/domains/api/xoro/import-sources/api/xoro/import-runs