Xome
FeaturesHow it worksFAQDocsTry Xome →Join waitlist

Self-hosting

Deploying.

It's a standard Next.js app, Vercel deploys it with zero config; any Node host works.

Vercel (recommended)

  1. 1
    Import the repo
    vercel.com → Add New → Project → import your fork/clone of xome-webapp. Next.js is auto-detected; default build settings work.
  2. 2
    Set environment variables
    .env.local is gitignored and does not deploy, add every variable from the Environment variables page in Project → Settings → Environment Variables, then redeploy.
  3. 3
    Point your domain
    Settings → Domains → add your domain (e.g. app.your-domain.com) and create the CNAME it shows at your DNS provider.
  4. 4
    Update the provider dashboards
    Add the production redirect URIs on Google/Slack/GitHub, and your domain to Privy's allowed origins. If you use a different production hostname than app.xome.bot, set XOME_PROD_HOST.

Other hosts

  • Anything that runs Next.js 15 (Node 20+): npm run build && npm run start behind a reverse proxy.
  • Behind a proxy/load balancer, forward x-forwarded-host and x-forwarded-proto, OAuth redirect URIs are derived from them.
There is no database to provision and no server state to back up, user data lives in each user's browser. Your deployment is stateless and horizontally scalable by default.