Hosting a small internal tool that needs a database and logins
If you built the tool with an AI assistant and don't run servers, choose a host that includes the database and the sign-in and that your assistant can deploy to. If a developer or IT team will own it, a developer cloud plus a managed database gives more room to change things. If you would rather drag and drop and don't mind rebuilding, a low-code builder works. For a team of ten, the routes in the table start at $25 a month as listed, and two other hosts that bundle the database and sign-in start lower.
Updated 7 November 2026. Prices of other products checked 6 and 7 November 2026.
Three questions that pick the route
Who will fix it when it breaks? Who has to sign in, and can they use their work email? What does the tool store, and for how long? A tool that holds a year of expense claims has different needs from one that does a calculation.
The example: an expense tracker for ten people
Say your team has an expense form. Nine colleagues each submit claims and one person (you) builds and manages it. It needs one table, one sign-in and a backup. Here is what each route costs on public list prices, and what you do to get it running.
| Route | What you pay a month | Database | Sign-in | Backups |
|---|---|---|---|---|
| Low-code builder (Retool) | Free up to 5 users, so ten needs a paid plan. At the Team rates we read (£10 for the builder, £6 per internal user), 1 builder and 9 users come to £64 | Retool Database, up to 5 GB | Not checked | Not checked |
| Developer cloud plus database (Render and Supabase) | Supabase Pro $25, plus a Render web service (Hobby $0 plus compute, Pro $25 plus compute; compute rate not listed here, check Render) | Supabase Postgres | Supabase Auth | Daily, kept 7 days, on Supabase Pro |
| Host your assistant deploys to (Haechy) | Pro US$25 or €25 a month as listed, since the Free plan covers 5 people and this team is 10. Checkout isn't open yet | Postgres per app | Emailed one-time link | Nightly, 30 days, plus weekly copies for 90 days |
| Ask your IT team | Depends on what they run | Theirs | Theirs | Theirs |
Retool figures from its pricing page and Supabase and Render figures from theirs, checked 6 November 2026. Haechy's from its pricing page, 7 November 2026.
AppDeploy and Hatchable are two more hosts in the same row as Haechy. Hatchable's Builder plan is $12 a month and AppDeploy's Plus is $20 a month, as listed on 7 November 2026; both are cheaper at entry than Haechy's Pro. The connector list compares them.
What the work looks like on each route
A low-code builder means building the screens in the builder's own editor. Your assistant's code doesn't carry over. It is a good choice when the tool is mostly forms and tables and you like clicking more than prompting.
A developer cloud with a managed database is the most flexible. You create the database project, set up sign-in with an auth service, put the web service on a host, connect the three with settings and secrets, and keep an eye on them. Free tiers need care: Supabase pauses a free project after a week of inactivity and doesn't include backups, and Render says its free Postgres expires 30 days after creation and shouldn't be used for production applications. It suits a team with someone who enjoys this kind of work.
A host your assistant deploys to is the shortest. On Haechy you connect it to Claude once (the setup guide has the steps), create an account with your email, a password and a code sent to your phone, then ask Claude to build the tool and put it online. Claude creates the database and the sign-in comes with every app. You add the colleagues' emails and send them the address. Each colleague receives a one-time link, with no password and no Claude account. If you make a mistake later, you can ask Claude to restore a backup, and it takes a safety copy of the current data first.
Asking IT is the right call when the tool touches systems they already manage, or when the company's rules decide where things may run. The IT page lists what Haechy does and doesn't do, so you can send them something concrete.
Python or Node?
Haechy runs Node, Python or a static site, and a small Python tool for ten people works the same as anything else here: Claude writes it, deploys it, and the database and sign-in are already there. For the other routes, check what the host supports for your language before you commit; this page doesn't claim it for them.
Sign-in in more detail
Three ways to give a self-built tool a login. The host does it for you, which is how Haechy works. An auth service such as Supabase Auth does it, and you wire it into the code. Or an access layer sits in front of the app, such as Cloudflare Access, which sends approved email addresses a one-time PIN. The first asks the least of you and the last needs the most setup. Giving colleagues access without accounts goes through the choices.
If you were going to use Vercel
Vercel is built for front-end sites, and that is where it shines. Its Hobby plan is for personal, non-commercial use, per its pricing page, and the Claude connector it lists is for searching and managing projects and deployments, with no database in it. A tool that needs a database and logins for a team usually wants a host that comes with them, or a database service next to Vercel. For a public-facing site, Vercel is a good fit.
When Haechy isn't the answer
It isn't built for public marketing sites or for heavy computing. Free apps sleep after 15 minutes without use and wake in seconds, the terms promise no uptime guarantee, and the Free plan holds 500 MB of data (250 MB per app). A big dataset, a high-traffic site or a tool that must be on 24/7 belongs on a developer cloud or with IT.
Data location is covered in hosting an internal app in the EU. Plan limits are on pricing and in the limits docs; the quickstart and security page cover starting and what Haechy checks on every deploy.