Cloud Personal Server plan

[tnunamak]

Summary

Plan for provisioning Personal Servers on account.vana.org when users log in — no desktop app required.

• Dockerize personal-server-ts for cloud deployment (GCE micro VMs initially, Sprites.dev later)
• Provider abstraction so infra backend is swappable via env var
• Stripe-style API routes in vana-connect (POST /api/servers, GET /api/servers/:id, etc.)
• Neon Postgres for user→server mapping
• Provision on login — after Privy auth, auto-provision or reconnect to existing server
• UI — server status, MCP endpoint copy, in account.vana.org dashboard

Phasing

1. Containerize personal-server-ts
2. GCP provider + API routes in vana-connect
3. Login integration + UI
4. Sprites.dev provider (swap)

Key decisions made

• GCE VMs (not Cloud Run) — PS is stateful/long-lived
• Stripe-style API semantics (resource-oriented, idempotent creation, srv_ prefixed IDs)
• No "full handover" token model for now — Vana manages servers
• Connectors via CLI for now, not in scope

See docs/260319-cloud-personal-server-plan.md for full details.

Review

This is a plan doc for discussion — no code changes.