kushbavaria tries to stand up Mike as Ornn's own hosted instance
A closed PR sketches what it would take to run Mike on Google's cloud, gated to one firm's staff.
kushbavaria proposed wiring Mike onto Google Cloud Run as two services - frontend and backend - with the supporting plumbing to match: a fresh Google Cloud project under the ornn.com organization, billing linked, container registry, secrets storage, and a dedicated runtime identity with read access to those secrets.
The more interesting half is an access policy layered on top. By default the app would only let @ornn.com users in, with a named-email escape hatch for inviting outside advisors. Login, signup, and the shared auth layer were rewired to enforce it. Documentation landed alongside so the deploy could be repeated. The author noted that an actual deploy still needs real Supabase, storage, and model-provider credentials, and the PR was closed about a minute after opening without merging.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?