01
Sign in on the web
Luckee Supabase handles auth. Profile metadata syncs to the Railway cloud API — not your Vercel secret.
Vercel-only today — one local dashboard for visits and pageviews across your projects. Create a free account for GitHub URLs; website data and your Vercel token stay on your machine.
Local Postgres
Websites and cache on your device
Vercel token
Companion .env only — never the cloud site
Luckee auth
Same sign-in as other Luckee apps
01Setup
The companion SQL lives under sql/ in the express-server repo. Luckee Hub can start Postgres, apply migrations, and launch dev servers.
02Companion
On the hosted surface, /app probes your machine at NEXT_PUBLIC_LOCAL_API_URL (default http://127.0.0.1:3009). Analytics and project discovery never flow through Railway.
GET /api/health
curl -s http://127.0.0.1:3009/api/health03How it works
01
Luckee Supabase handles auth. Profile metadata syncs to the Railway cloud API — not your Vercel secret.
02
Express loads websites from Postgres and pulls Vercel Web Analytics pageviews and visitors with your token.
03
Local surface uses the companion directly. Cloud /app unlocks when the health probe succeeds.
Sign up free for GitHub URLs, run the companion locally, then open the app when the health check passes.