GLEE Cloud

The platform Worker is live. The custom hostname is attached.

GLEE should not stop on vague limits. This page shows the exact public cloud state: what runs now, what is still being connected, and what proof exists.

Read platform-status.json Worker health Read contracts
GLEE Cloud

Platform Worker is live. Custom hostname is attached.

The Worker is available through platform.gleephoenix.com and the Workers.dev fallback. GitHub OAuth credentials are the remaining account setup step.

FallbackLiveWorkers.dev remains available
Live now

Platform custom domain

  • /health returns service state.
  • /login serves the account scaffold.
  • /mcp is the public read-mostly MCP airlock endpoint.
  • Worker custom domain for platform.gleephoenix.com is deployed and enabled.
Remaining setup

GitHub OAuth

  • Application name: GLEE Phoenix Platform
  • Homepage: https://platform.gleephoenix.com
  • Callback: https://platform.gleephoenix.com/auth/github/callback
  • Scope: read:user
  • Current auth start: 503 setup pending until credentials are installed.
How it is connected

Cloudflare Worker custom domain, not Sunny exposure.

platform.gleephoenix.com is attached directly to the glee-platform Worker. The public cloud can serve onboarding, WorkLoops, MCP airlock reads, and account shell pages. It does not expose the Sunny or create an inbound command path to the private ship.

Open work continues

GLEE keeps building while OAuth is pending.

The current open path is public site improvement, contracts, search, Vela, receipts, updates, platform Worker surfaces, and proof loops. Once GitHub OAuth credentials are installed, GLEE should verify the first authenticated dashboard session.