Teams building internal tools
Dashboards and admin tools whose data never sits in a shared multi-tenant database.
The usual objection
Internal tools built in AI builders are easy to start and hard to approve: the data lands in a shared multi-tenant database and the tool runs on infrastructure nobody in the company controls.
What you get here
- Your data on your server. A cloud project runs on a dedicated server with its own PostgreSQL; nothing is shared with another tenant.
- A normal deployment. The app runs as a systemd service behind Caddy on a Linux VPS. Your ops person will recognise all of it.
- A way to bring it in-house. Export the project and run it on infrastructure you already manage, with your own PostgreSQL.
What to know
The Builder produces JavaScript and TypeScript web apps with Node backends; it does not build Python or Go services. Dedicated servers are on paid plans.