The cheapest way to host a website and database for a side project
The cheapest way to host a side project website and database is with thelastapi, where hosting is $0 today and Postgres provisions in one command.
On this page 9 sections
The cheapest way to host a website and database for a side project is on an integrated platform where web hosting is currently uncharged at $0 and serverless Postgres provisions automatically. On thelastapi, running a single initialization command sets up hosting, a Postgres database, user sign-in, and analytics under one project key. Every project gets a free web address on day one with zero hosting fees today, keeping your initial monthly infrastructure bills at zero.
When you start a side project, coordinating separate providers for front-end hosting, database branches, and DNS routing quickly adds administrative friction and recurring base tiers. Combining these tools into one environment eliminates both the extra accounts and the idle infrastructure costs.
What does it cost to run a side project on thelastapi?
Hosting on thelastapi is not charged today: builds and live sites are recorded in usage at $0, as pricing has not been decided. Every project receives an active web address at https://<slug>.vibiz.app that stays free for as long as the project exists.
When you initialize a project, the core services needed to run a dynamic web application are provisioned together:
| Resource | What it provides | Cost today |
|---|---|---|
| Web hosting | Content-hash builds, global delivery, preview URLs | $0 (recorded at $0 in usage) |
| Database | Dedicated serverless Postgres per project | Included with project provisioning |
| User sign-in | Authentication supporting Google and GitHub | Included with project provisioning |
| Analytics | Privacy-conscious visitor metrics and traffic tracking | Included with project provisioning |
| Web address | Subdomain at https://<slug>.vibiz.app | Free for the life of the project |
| Custom domains | Connect a domain you already own elsewhere | Free to connect (DNS verification) |
Because hosting and resource provisioning operate under one account, you do not need to enter card details across separate services just to test a prototype or validate an idea. You can also explore how every project gets its own web address on day one without setting up DNS records before you build.
How do you deploy a website and database together?
You can create and deploy a project from your local terminal using the vibiz CLI, or trigger it directly through an AI coding agent like Claude Code, Codex, or Cursor.
1. Initialize the project
Install the CLI and initialize your app directory. By default, vibiz init configures hosting, a database, sign-in, and analytics:
mkdir acme-app && cd acme-app
vibiz init "Acme App"If you prefer a pre-configured framework with schemas and routes ready to edit, use the SaaS starter template:
vibiz init "Acme App" --template nextjs-saasTo see how full-stack starters run, read how to deploy a Next.js app with a database and sign-in in one command.
2. Configure local development
Run the development command to generate your local environment configuration:
vibiz devThis command creates a .env.development.local file containing your development credentials. Instead of forcing you to share or seed a live database, development includes its own isolated database branch. It carries production's tables and schema without any live customer rows. To learn more about branch mechanics, read about serverless Postgres for side projects: one database per project.
3. Deploy to production
To push your code live, run:
vibiz deploy -m "Initial release"The CLI builds the project and publishes it to your assigned address at https://acme-app.vibiz.app. Deployments work by content hash: files that the host already stores are never uploaded twice. If you want to check your changes before pointing production traffic to them, create a preview deployment:
vibiz deploy --previewPreviews receive their own unique URL. When you are satisfied with the preview build, promote it instantly:
vibiz promote dep_123If you do not want to work from a local terminal, you can also connect your account to ChatGPT or Claude via remote MCP (https://thelastapi.dev/mcp). This setup lets you host a landing page that ChatGPT or Claude wrote directly from chat without installing local dependencies.
What limits apply to builds and hosting?
To ensure platform reliability while keeping hosting at $0, the following usage rules and boundaries apply:
- Daily builds: Projects can run up to 30 builds per UTC day. When a project hits 30 builds, requests receive a
429 rate_limitederror until the reset window. You can monitor your current build count usingGET /v1/usage, which exposes thebuilds_todayfield. - File counts and sizes: A standard folder deployment supports up to 10,000 files, with an individual file limit of 50 MB. When deploying directly from an AI chat interface using remote tool calls, you can send up to 300 files per call, with limits of 3 MiB per file and 4 MiB total payload per request.
- Ignored paths: The deployment pipeline automatically strips unneeded development directories and secrets. Files inside
node_modules,.git,.next,dist,.turbo,vibiz.json, and any.env*files are never uploaded. Credential files like*.pem,id_rsa, and.npmrcare also refused. - Project restoration: If you delete a project, its site goes offline immediately. However, project files and database data are retained for 7 days, allowing you to run a full restoration during that window.
Detailed build limits and command flags are documented in the Hosting guide.
How do version rollbacks work?
Every deployment creates an immutable version entry in your project history. If a new deployment introduces a regression, you can inspect the differences and revert without touching git branches:
vibiz versions # view recent deploys, messages, and timestamps
vibiz diff # view the unified diff between live and the prior release
vibiz rollback # switch immediately back to the previous production versionWhen rolling back, remember one critical rule: the database is not rolled back. Only the site's code and assets return to the previous version. Your database tables, rows, and schema adjustments remain unchanged, ensuring you do not overwrite new records created by users while the faulty deployment was active.
Connecting your own domain
While every app starts on a https://<slug>.vibiz.app address, you can attach custom domains whenever you choose.
To link a domain you already own:
vibiz domains add shop.example.comThe CLI prints the exact DNS records to enter at your DNS registrar:
- For a subdomain like
shop.example.com, add aCNAMErecord pointing tocname.vibiz.app. - For an apex domain like
example.com, add anArecord pointing to the address shown inrecords_to_set. Adding an apex domain automatically sets upwww.example.comas a redirect.
Once your records propagate, check the status:
vibiz domains verify shop.example.comHTTPS certificates issue automatically once DNS resolves. For full configuration steps, see the documentation on Domains.
Monitoring your project health
Side projects often sit unattended for days or weeks. Instead of instrumenting separate monitoring dashboards, the platform includes automated health checks through Mission Control.
Every active project is checked approximately once an hour for:
- Site availability: Verifies that your domain resolves, serves a valid HTTPS certificate, and returns a 200-level HTTP status code within 10 seconds.
- Deployment health: Flags failed builds or builds stuck in a queued state for over 30 minutes.
- Resource provisioning: Confirms that databases and dependencies are healthy.
- Runtime errors: Detects spikes in JavaScript errors, dead clicks, or rage clicks recorded during visitor sessions.
You can inspect the status of your projects from the command line:
vibiz health # list all projects, sorted worst-first
vibiz health --failing # show only failing projects
vibiz health run # check every business again now in the backgroundRead more about health checks and diagnostic thresholds in the Mission Control and health checks guide.
Exporting your code and database
Keeping hosting costs low should never trap your code inside a closed garden. With thelastapi, you can export your application files and database records whenever you choose:
vibiz exportThe command generates two key production exports:
<slug>-<env>-code.zip: A zip file containing your complete original application source code as uploaded, a setup guide (VIBIZ-EXPORT.md), and an.env.examplefile documenting required variables.<slug>-<env>-database.sql.gz: A complete snapshot of your Postgres schema, tables, indexes, views, functions, triggers, and rows.
Because the database dump uses plain SQL, you can restore your data directly into any clean Postgres instance (version 15 or newer):
gunzip -c acme-app-production-database.sql.gz | psql "$NEW_DATABASE_URL"To review export options, including CSV generation, refer to the documentation on Export.
Next step
To begin hosting your website and database on one key, create your account at thelastapi.dev/start. Then read the Quickstart guide to connect your environment and deploy your first application.
Frequently asked questions
How much does hosting cost on thelastapi?
Hosting is currently uncharged at $0, with builds and live sites recorded in usage at no cost while long-term pricing is undecided.
How many builds can I run per day?
Each project is permitted up to 30 builds per UTC day before returning a rate-limit error.
What happens to my database when I roll back a deployment?
Rolling back with `vibiz rollback` reverts your application code only; database schemas, tables, and rows remain in their current state.
Can I use my own domain with the free hosting?
Yes, you can attach any domain you own by running `vibiz domains add <domain>` and pointing the required CNAME or A records to our hosting addresses.
How can I back up or migrate my Postgres database elsewhere?
Running `vibiz export --db` downloads an uncompressed or gzipped SQL snapshot that you can restore into any standard Postgres 15+ database using `psql`.