How to
Deploy to Vercel
Deploy the Kredal app and the docs site to Vercel.
Kredal is two deployable projects: the app (kredal-app/) and the docs site
(docs-site/). Both are Next.js and deploy cleanly to Vercel.
Deploy the app
- In Vercel, New Project → import the
anilandcode/loanreadyrepo. - Set Root Directory to
kredal-app. - Add environment variables (Project Settings → Environment Variables):
NEXT_PUBLIC_SUPABASE_URLNEXT_PUBLIC_SUPABASE_ANON_KEYSUPABASE_SERVICE_ROLE_KEY(mark as sensitive; never expose to the browser)
- Deploy. Framework preset auto-detects Next.js.
- In Supabase → Authentication → URL Configuration:
- Set Site URL to the production URL.
- Add
https://<your-domain>/auth/callbackto Redirect URLs — password-reset and email-confirmation links exchange their code at this route.
Auth email volume (do this before any pilot)
Supabase's built-in auth mailer is rate-limited to roughly two emails per hour — enough for solo testing, guaranteed to break real signups, password resets, and member invites. Connect a custom SMTP provider (Resend has a free tier) in Supabase → Authentication → SMTP Settings, and verify a sender domain there first.
Deploy the docs site
- New Project → same repo, Root Directory
docs-site. - No secret env vars are required for the public docs.
- Deploy. Optionally attach a
docs.subdomain. - Confirm
/,/llms.txt, and/llms-full.txtall respond.
Verify a deployment
- App: sign up, create a company, run an assessment against the live database.
- Docs: search works, a page renders with the Kredal navy theme, Mermaid diagrams draw.
Notes
- This repo lives on a Google Drive–synced path locally, which makes git operations slow.
When committing before a deploy, allow generous timeouts (or run in the background) and
check for a stale
.git/index.lockbefore assuming a crash. - Preview deployments are created per pull request automatically — useful for reviewing docs
changes before they hit
main.