Describe the app. Mason builds it: Vite, TypeScript, Tailwind and a real database. Code you own from the first prompt.
The database needs a connected Neon account. Without it, Mason builds the frontend only.
A simulated Mason chat, not a recording. The prompt “A booking app for my barbershop” is sent. Mason creates the schema, writes components, wires auth and opens a preview of a barbershop booking app. Then it asks for permission to push the code to GitHub and waits. You can answer with the buttons. This example assumes Neon and GitHub are connected.
Simulated preview · assumes Neon and GitHub are connected
What’s under the hood
- Frontend
- Vite, TypeScript, Tailwind
- Backend
- Neon + Express APIWhen your Neon account is connected.
- Export
- One click, frontend and backendThe backend is in the export when it was built, so with Neon connected.
- Hosting
- Backend goes to your GitHub, ready to deploy on RenderWith GitHub and Render connected, and only after you approve the push.
- Models
- Sabiá, by Maritaca AI
The conditions, plainly. Connect Neon, GitHub and Render and Mason builds the full stack. The push to GitHub only happens after you approve it. Without those connections, Mason builds the frontend only.
It asks before it breaks things
Routine work runs without stopping. Anything you can’t easily undo, anything that costs money and anything that goes public waits for your yes.
Does on its own
- Writing and editing code
- Creating the schema, with Neon connected
- Building components
- Wiring auth
- Running the preview
Asks you first
- Deleting data
- Force-pushing
- Pushing to GitHub
- Deploying to production
- Anything that touches credentials
- Purchases
- Publishing anything publicly
Built on Sabiá. We’ll say it out loud.
Mason runs on Sabiá models from Maritaca AI: a fast one for quick edits, a thinking one for building. Brazilian models, no smoke.