What Happens When You Type a URL and Press Enter
DNS lookups, TCP and TLS handshakes, HTTP requests, servers, and the browser's rendering pipeline. The whole journey of a web page, explained so it finally clicks.
Read →Which free database should you pick for a side project? A comparison of managed Postgres, MongoDB and edge SQLite options, with the limits that matter and how to stay portable.
Your side project needs somewhere to keep its data, and you'd rather not pay for it until someone actually uses the thing. Free database hosting is easy to find now. The hard part is picking one that won't box you in six months from now.
Before comparing free tiers, decide what kind of database fits your app.
If you're unsure, pick Postgres. It handles relational data, JSON columns, full-text search and even vector embeddings through extensions. It's very hard to outgrow for a side project.
Supabase. Postgres plus a lot of extras: authentication, file storage, realtime subscriptions and auto-generated REST APIs. Row-level security lets you query safely from the frontend. Free projects pause after a period of inactivity, so a forgotten demo may need a click to wake up.
Neon. Serverless Postgres that scales compute down to zero when idle, which suits hobby traffic well. Its standout feature is branching: copy your database instantly for a preview deployment or a risky migration.
Others. Several providers, such as Aiven, have offered small free Postgres or MySQL instances. Plans change, so compare current limits when you sign up.
MongoDB Atlas has offered a free shared cluster for years. It's the natural choice if you're following MERN tutorials or your data is document-shaped. Pair it with Mongoose for schema validation; schemaless doesn't have to mean structureless.
Turso (built on libSQL, a fork of SQLite) and Cloudflare D1 bring SQLite to serverless apps. Reads are very fast and replicas can sit close to users. They're great for content sites, small SaaS tools and read-heavy APIs. For complex write-heavy workloads, Postgres is usually more comfortable.
| Need | Good free pick |
|---|---|
| General web app with auth | Supabase |
| Serverless Postgres with preview branches | Neon |
| Document data / MERN tutorials | MongoDB Atlas |
| Edge functions, read-heavy content | Turso or Cloudflare D1 |
| Cache, sessions, rate limits | Upstash Redis |
Storage limits get all the attention, but these bite first:
Free plans change. PlanetScale once had a popular free MySQL plan and removed it, and plenty of developers had to migrate in a hurry. Protect yourself:
A free database gets the same performance rules as a paid one. Add indexes for the columns you filter and sort by (indexing explained) and watch out for the N+1 query problem. A well-indexed database on a free tier will often outrun a sloppy one on an expensive plan.
Supabase or Neon if you're learning SQL, MongoDB Atlas if you're following a MERN course. Supabase is especially beginner-friendly because of its dashboard and built-in auth.
Yes, for many apps. SQLite handles a lot of read traffic well. Hosted options like Turso and D1 make it practical for serverless deployments. Write-heavy apps with many simultaneous writers usually do better on Postgres.
Many free plans pause inactive databases to save resources. Upgrade, choose a provider that scales to zero and resumes automatically, or accept the occasional wake-up delay for hobby projects.
DNS lookups, TCP and TLS handshakes, HTTP requests, servers, and the browser's rendering pipeline. The whole journey of a web page, explained so it finally clicks.
Read →There are dozens of HTTP status codes, but about fifteen cover nearly everything. What each one means, when to return it, and the mix-ups (401 vs 403, 301 vs 302) that confuse everyone.
Read →A, AAAA, CNAME, MX, TXT and NS records in plain English, why DNS changes seem slow, and the troubleshooting commands that tell you what is really going on.
Read →