Convex is your backend
agentify, Jmcon, clickmediaprodev, and nicodelgadodev all use Convex — not a separate SQL platform.
Difficulty 2/5
Mental model
Plain English
When you ship an app for a client, the data layer is almost always Convex: TypeScript schema, functions that enforce who can read/write, and live updates in the UI. You don't need a second backend product for your repos on the VPS.
Analogy
One kitchen for all your restaurants — same rules, different menus (schemas).
Jessica's wedding portal
Events, tasks, chat in youthful-kookabura-525; organizationId on rows.
Agentify CRM
CRM data in decisive-warthog-196; inbox updates without refresh.
HógaPy real estate
Leads and intake chat in clickmediaprodev Convex deployment.
Go deeper
Convex = database + server code + realtime.
Common mistakes
- Looking for 'the Postgres' in your repos — it's Convex tables.
- Adding a second BaaS because a tutorial said so.
AI-agent trap
Agents scaffold Supabase for your projects — redirect to Convex patterns in convex/ of the target repo.
Quick check
Where does Agentify store conversations?
Summary
Frontend only calls Convex functions; secrets stay in convex env.
Confidence: