Appearance

Language

Build a personal website from 0

Does a Personal Website Need a Backend? When to Add Supabase

Most personal websites don't need a backend: posts and projects can be static files. Add one like Supabase when visitors log in, write data, or content changes without a deploy. Supabase Free vs Pro at US$25/month, Firebase and self-hosting on AWS Lightsail compared on cost and upkeep.

Kelvin Wang · · 7 min read

Blog posts, a portfolio and an about page are built once and served from a CDN, with no database and no server code. When I do need a backend (comments, saved settings, a private dashboard), I use Supabase, a hosted PostgreSQL database with user auth and file storage built in. It runs the private side of my personal site, and its free plan is enough to start. Supabase Free costs nothing; Pro starts at US$25 a month and includes US$10 of compute credits, enough for one Micro instance.

What a backend actually does

The frontend is what the browser shows: HTML, CSS and a bit of JavaScript. The backend is the part that runs somewhere you control and remembers things between visits. In practice that means three jobs:

  • A database that stores data and answers queries.
  • Auth that knows who a visitor is, so it can show them their own data and nobody else’s.
  • File storage for uploads like images.

If nothing on your site needs to remember anything about a visitor, and every page can be built ahead of time, you have no backend to run.

When you don’t need one

What you wantDo it without a backend
Blog postsMarkdown/MDX files in your repo, built into static pages
Portfolio and about pageStatic pages
ContactAn email link, or a hosted form service that emails you
Visitor statsAn analytics script; no database of your own
Updating contentEdit the file and push; the host rebuilds

My own site proves the point in reverse. In June 2026 I moved my blog posts into a Supabase table, and later wrote them through an editor in my admin app. On November 5, 2026 I moved all 52 published posts back into files in the repo. The editor went unused (an AI drafts, I read everything and say when it can go out, and the AI does the rest), it limited the layout, and every post existed twice. The public blog hasn’t needed the database since.

Go deeper Add a Markdown Blog to an Astro Website (2026) A blog with no database: a folder of Markdown files and two Astro pages.

When you do need one

  • Sign-in. Anything behind a login: a members area, a private dashboard, an admin page.
  • Data that visitors create. Comments, likes, form submissions you want to keep and query.
  • Data that changes faster than you deploy. Prices, stock levels, a feed updated by a script.
  • Logging events you’ll query later, like which outbound links get clicked.

Here’s what my site actually keeps in Supabase today:

FeatureIn Supabase?Why
Blog postsNo (files since 2026-11-05)They change only when I publish, so a build is enough
Private dashboard at /app (finance and other private data)YesPrivate data behind Google sign-in
Sign-inYes, Supabase AuthOnly workspace members get into /app
Exchange section dataYesFee and promo rows update between deploys
Referral link clicksYesOne row per click, no IP or user agent, queried in the dashboard

Why Supabase again

I’d used it before, it’s open source, and the community behind it is strong. The free plan makes it easy to start, and even if I have to pay later, the price is manageable.

To explain the choice properly, though, I had to answer one question: would running my own database on AWS be cheaper?

First, what are we buying?

Besides a PostgreSQL database, Supabase comes with backend features like user auth and file storage, each with its own plan limits.

A server where you install the database yourself is a different purchase. Once it’s rented, database updates, backups and restores, user auth and the backend API are all still yours to set up.

So I limited this comparison to a personal site that’s just starting: low traffic, a few users, mostly text. The frontend stays on Cloudflare; I only looked at backend cost and the work I’d have to take on.

Supabase pricing vs Firebase vs AWS: starting costs

OptionStarting costWhat you get
Supabase FreeUS$0/month within the limitsDatabase plus integrated backend features; watch storage, the pause rules and backups
Supabase ProFrom US$25/monthIncludes US$10/month of compute credits, which cover one Micro instance; more projects, bigger instances or overages cost more
Firebase: Firestore + standard sign-inCan be US$0/month within the free tierAnother managed backend combination; Firestore is a document database, not PostgreSQL
AWS Lightsail, self-hosted databaseUS$12/month for the server in this exampleA Linux server with 2 GB RAM, 2 vCPUs, 60 GB SSD and a public IPv4 address; database software, API, user auth and maintenance are up to you

USD prices, excluding tax, short-term trial offers and overage fees. First checked September 2026, rechecked November 7, 2026 with no change.

Supabase Free includes a 500 MB database and 1 GB of file storage per project, 50,000 monthly active users and 5 GB of egress. Free projects pause after a week without activity, the free plan allows at most two active projects, and there are no automatic backups. If you already have other projects there, check that you still have a free slot and enough quota.

Supabase Pro starts at US$25 a month. That includes US$10 of compute credits, enough for one Micro instance, so a single small project costs the base price. Each project gets 8 GB of disk (then US$0.125 per GB), 100,000 monthly active users, 100 GB of file storage, 250 GB of egress and 7 days of backups, and Pro projects are never paused. A second project, or a larger compute size, is billed on top.

Go deeper Supabase pricing explained: Free, Pro at US$25, and compute add-ons How compute credits work, what a second project costs, and when Free stops being enough.

Firebase also lets you start free. Firestore’s free tier includes 1 GiB of stored data, 50,000 document reads and 20,000 writes a day, and 10 GiB of outbound transfer a month. This comparison assumes Firestore with standard sign-in, no SMS. File storage, Cloud Functions, SMS and similar services are billed separately, and you may need to move to the Blaze plan.

Self-hosting on AWS may cut the monthly bill, but count the maintenance

Going by the table, Supabase Pro at US$25 and the Lightsail server at US$12 differ by US$13 a month on paper. That leaves out the backups, the other services and my own time that self-hosting needs.

This is how I look at cost:

Monthly total = service fees + extra resources + the cost of maintenance time.

If you already know how to run servers and databases, self-hosting can be worth it. If you’d rather get the site’s features built first, ask how much maintenance and integration work that monthly fee saves you.

AWS CLI can automate it, but deploying still takes time

I also looked at doing the setup with the AWS CLI, using commands and scripts instead of clicking around the console. Scripts make the setup repeatable, but someone still has to write them, run updates, test restores and fix whatever breaks.

Connecting Supabase to an Astro site: first steps

  1. Create a project at supabase.com. Pick the region closest to your visitors.
  2. Copy two values from the project’s API settings: the Project URL and the publishable key (it starts with sb_publishable_). The publishable key is safe in browser code because Row Level Security decides what it can read.
  3. Store them as environment variables, locally in .env (keep it out of Git) and in your host’s build settings:
PUBLIC_SUPABASE_URL=https://your-project.supabase.co
PUBLIC_SUPABASE_PUBLISHABLE_KEY=sb_publishable_...
  1. Install the client and create it once:
npm install @supabase/supabase-js
// src/lib/supabase.ts
import { createClient } from '@supabase/supabase-js';

export const supabase = createClient(
  import.meta.env.PUBLIC_SUPABASE_URL,
  import.meta.env.PUBLIC_SUPABASE_PUBLISHABLE_KEY,
);
  1. Turn on Row Level Security for every table and write a policy before you put real data in. Without a policy, the publishable key can’t read the table; with a careless one, anybody can. Run this in the SQL editor for a table anyone may read but nobody may change through the publishable key (notes is an example name):
alter table public.notes enable row level security;

create policy "Anyone can read notes"
  on public.notes for select
  to anon, authenticated
  using (true);

For rows that belong to a signed-in user, the condition becomes using ((select auth.uid()) = user_id), where user_id is the column that stores the owner. With no insert, update or delete policy, those operations are refused.

Go deeper Supabase RLS Tutorial: Policies, using vs with check, Testing Write policies that let the right people in and test that they keep everyone else out.

Pitfalls I hit

  • A database in the build path. While my posts lived in Supabase, every build read them from the database, so Cloudflare Workers Builds needed the Supabase variables set in its build settings or the build couldn’t produce the blog. Moving posts to files removed that dependency.
  • Pausing on the free plan. A free project pauses after a week of inactivity. A small site that only reads its database occasionally can hit this; check the project before you rely on it for something visitors see.
  • Policies written for one user. Most of my tables first matched rows with owner_id = auth.uid(), the signed-in user. Before adding a second member to the dashboard, a review found two problems: the new member wouldn’t see anything in the dashboard, while three finance tables allowed any signed-in account to read and write them. Every policy now checks workspace membership first, then the workspace owner.

I stayed with Supabase mostly because I know it

My earlier projects already use it, so that experience carries over and I skip relearning and wiring up other tools. My site runs on the free plan and costs nothing; I moved my other projects to Pro (US$25 a month) for custom domains and so they don’t pause when idle. If you’re just starting, the free plan is enough to check whether the limits cover what you need. When it’s time to pay, look at actual usage, backup needs and maintenance cost, so you don’t waste money.

If your site is posts and projects only, skip the backend for now. Add it the day you build the first feature that needs to remember something.

Sources

  1. 1. Supabase pricing · Supabase · 2026-11-07
  2. 2. Understanding API keys · Supabase · 2026-11-07
  3. 3. Firebase pricing · Firebase
  4. 4. Cloud Firestore pricing · Firebase · 2026-11-07
  5. 5. Amazon Lightsail pricing · AWS · 2026-11-07
  6. 6. Lightsail bundles · AWS
  7. 7. AWS CLI · AWS

About the author

Kelvin Wang

Electrical engineer building tools with AI agents, sharing hands-on notes on engineering and investing.

More about me