Sign in to the protected portal before the build goes live.

The shell is designed for localhost-first OAuth login now and Vercel deployment later. Once Google OAuth and the session route are wired, the portal stays private and returns to your callback URL.

Start a project

Local first

The login shell works on localhost before production Vercel settings are added.

Google OAuth

Sign-in returns to your callback URL so the portal stays protected.

Stripe-ready

Billing actions are wired for a future Stripe Checkout route once the backend is live.

Session status

Checking access

ASC

Protected route for active clients and internal reviews.

Callback URLs stay on localhost while you test, then move to Vercel.

Stripe checkout can be added behind the portal without changing the shell.

Signed-in identity

Client access

Use the Google OAuth flow to attach a session.

Talk to us

PROTECTED ENTRYCLIENT PORTAL