Working with AI

Ship and own your stack

Graduating from no-code to a real production deploy you control.

0/11 complete
01

When (and why) to graduate from an AI builder

Five signals it is time to leave Lovable, Replit, Bolt, v0, Emergent or Base44. What migrating actually involves, and what graduating does not fix.

7 min read
02

Your first real deploy: Supabase + Vercel from scratch

Concrete walkthrough, exporting from no-code, setting up Postgres, deploying frontend, custom domain. Ends with a working URL.

12 min read
03

Migrating from Lovable: GitHub sync, TanStack Start SSR, and Supabase auth

Lovable's GitHub sync pushes to your repo directly. From there: Vite deploys to Vercel in one step; TanStack Start needs a node/edge adapter; Supabase auth redirects require three env vars updated. Includes a flag for the newer TanStack Start (SSR) stack.

10 min read
04

Migrate from Replit: Vercel + Fly.io + Postgres (full guide, 2026)

Move your Replit app off Replit and onto your own Railway hosting, following Railway's official migration path. Export to GitHub (free on Starter), translate the .replit run command, migrate Postgres with pg_dump, and replace Replit Auth.

12 min read
05

Migrate from Emergent: FastAPI→Railway, React→Vercel (2026)

Move your Emergent app off the platform and replace the emergentintegrations client and EMERGENT_LLM_KEY with a direct LLM connection. FastAPI moves to Railway, React to Vercel, MongoDB to Atlas, with exact commands and env wiring.

11 min read
06

Migrate from Base44 to Vercel + Supabase (full guide, 2026)

Migrate your Base44 app to your own stack. Vercel for the frontend, Supabase for data — exact commands, env wiring, and the eject path. Updated 2026.

12 min read
07

Migrate from Bolt (bolt.new) to your own hosting (2026)

Move your Bolt app off the platform: export to GitHub, deploy the Vite + React frontend to Netlify or Vercel, and add a real backend if it only had mock data. Exact build settings, secrets, and the Supabase path.

8 min read
08

Migrate from v0 to your own Next.js app + backend (2026)

v0 already generates standard Next.js on the Vercel stack, so the move is light: own the repo, deploy to Vercel, and swap v0's mock data for a real backend (Supabase). Auth, env vars, and the server-vs-client gotchas.

8 min read
09

Claude Code & CLI workflows: shipping from your terminal

Agentic CLI coding, git, npm, deploy commands. Graduating from web IDEs to a real local setup.

8 min read
10

Production monitoring: when your app breaks at 3am

Sentry for errors, Vercel and Railway logs, uptime checks, alert fatigue. The minimum setup so you find out before your users do.

7 min read
11

emergentintegrations.llm.chat: how the Python package works outside Emergent, plus JavaScript alternatives

What the emergentintegrations Python package does, how to keep it running on your own infrastructure with EMERGENT_LLM_KEY, why there is no JavaScript SDK, and how to replace it with direct OpenAI or Anthropic calls.

6 min read
When you are done here, go to

AI by role

Role-specific playbooks for sales, marketing, founders, HR, PM, engineering, design, ops.