3Edit Web Builder iconLesson 7 · How web apps work

Does my website need a database?

A simple test you can use on any idea.

Some websites only show information. Others have to remember things: who signed up, what was booked, what was ordered. Learn the simple test that tells you which one you are building, and when to connect a database.

About 7 minutes to readLast updated

By Humayun Rashed, founder of 3Edit

What a database does

A database is your app’s memory. It keeps information in tidy tables, a bit like a spreadsheet with strict rules: one table for customers, one for bookings, one for orders, each row one record.

Without a database, a website shows the same thing to everyone and forgets each visit as soon as it ends. With one, it can remember who signed up, what they booked and what they bought, and show each person what belongs to them.

The database test

Go through your idea feature by feature. If you answer yes to any of these, your site needs a database.

  • Accounts: do visitors sign up and log in?
  • Saving: does a visitor create something that must still be there later, such as a booking, an order, a message, a review or a saved list?
  • Different views: should different people see different things, such as a member’s own bookings or an admin page?
  • Changing content: do you want to add products, posts or events from an admin page, without asking for a code change each time?
  • Keeping records: do you need a list of everything that happened, such as every order or every enquiry?

Sites that can stay simple

Plenty of great websites never need a database. If your site’s job is to explain, impress and invite people to get in touch, it can stay simple, which keeps it quick to build and easy to look after.

  • A portfolio that shows your work and how to reach you.
  • A one-page site for a local business, with services, prices and opening hours.
  • A restaurant menu page or an event page with a link to book elsewhere.
  • A landing page for a new idea, with a button that links to your email or social pages.

Sites that need one

IdeaNeeds a database?Why
Photographer’s portfolioNoIt shows the same work to everyone.
Cleaning company with a booking request formYesEvery request is kept so the owner can see them all.
Online storeYesProducts, customers, orders and payments all have to be remembered.
Members’ area for a running clubYesMembers log in and each one sees their own details.
Restaurant with online orderingYesOrders and customer accounts are stored.
Personal blog you update yourself from an admin pageYesYour posts are kept as records you can add and edit.

When to connect your database

Connect it before you ask for the first feature that has to remember something. The AI can then build that feature properly from the start, with its tables and access rules in place, rather than a version that only looks right in the preview.

If you start simple and your site grows, that’s fine. Many projects begin as a frontend-only site and connect a database the day they add bookings or logins.

Your database in 3Edit: Supabase

A simple site in 3Edit needs no database. When you want one, you sign in to Supabase and approve 3Edit, then choose an existing database or create a new one. Supabase is a full Postgres database, and it lives in your own account, so your data stays yours.

Once it is connected, the 3Edit Agent builds what your idea needs: logins and roles, database tables and access rules in your Supabase, and server routes. The ecommerce, jewellery and restaurant starter kits come with their backends already built.

Good practice from day one

  • Describe the records you need: “Each booking has a name, email, service, date and status” gives the AI a clear table to build.
  • Say who can see what: “Customers see only their own bookings; I see all of them” becomes access rules in the database.
  • Test with two accounts: sign up as two different people and check neither can see the other’s data. The testing guide shows how.
  • Keep secret keys on the server: the security basics guide explains why, in plain words.

Try it in 3Edit.

These prompts build a booking request form for a cleaning company. Connect your Supabase first, as the connect guide shows, then paste each prompt in turn and check the result in the live preview.

  1. 1Check before you build

    I want a website for Sparkle Cleaning, a home cleaning company in East London, where visitors can request a booking. Before you build anything, tell me which features need a database and which tables you would create.

  2. 2Build it with the database

    Build the website: a hero with a “Book a clean” button, three services with prices, how it works in three steps, and a booking request form with name, email, phone, service, preferred date and a message. Save every request in my database with a status of “New”.

  3. 3Add a private list for the owner

    Add a private admin page where I can sign in and see every booking request, newest first, and change a request’s status to “Confirmed” or “Done”. Only I should be able to see this page and these bookings.

Then test it like a visitor: send two booking requests, sign in as the owner and check both are there. Open the site in a private window too, and check the admin page asks you to sign in.

About the author.

Written by Humayun Rashed, founder of 3Edit. He also runs 3Edit’s free in-person AI website building and vibe coding course in London.

Questions people ask.

No. A website that only shows information, such as a portfolio, a menu or a one-page business site, works well without one. You need a database when visitors log in, or when the site has to remember something they did, such as a booking, an order or a message.

Yes. A login needs somewhere to keep each account and to remember who is signed in, and that is the database’s job. It also holds the rules that keep each person’s information apart from everyone else’s.

Yes. Many projects start as a simple site and connect a database when they add bookings, logins or orders. Connect it before you ask for the first feature that has to remember something, so the AI builds that feature with its tables and access rules from the start.

Supabase is the database 3Edit connects to: a full Postgres database in your own account. In 3Edit you sign in to Supabase and approve 3Edit, then choose an existing database or create a new one, and the connect guide shows every click.

You do. Your Supabase database lives in your own Supabase account, and your project is standard Next.js code that is saved on your computer and can be kept in your own GitHub.

Start vibe coding today.

Download 3Edit for Mac or Windows and build your first professional website in minutes.

Download now
macOSWindows