how to get ai toGet new guides

Explain / Back end

What is the back end of a website?

The part you never see: the program on a server that checks, saves and sends things when you press a button. Many small sites don’t need one.

In plain English

The back-end is the part working away behind the curtain. You click "book a table" and suddenly something needs to check if that table's actually free, save your booking somewhere, fire off a confirmation email. That's the back-end doing its thing. It's the part that remembers and decides. Some tiny sites skip it entirely, but most need one the second they want to do more than just display a page.

A worked example

Someone fills in the café's booking form and hits submit. That info shoots off to the back-end, maybe running on Cloudflare Workers or a Supabase edge function, doesn't much matter which. It checks the date's available, checks the party size makes sense, then saves the booking and sends the confirmation. The front-end only ever showed the form. The back-end made sure the whole thing actually worked. All the customer sees is a friendly "you're booked in" message. Everything else happens somewhere they'll never look.

Getting set up

Loads of small sites don't have a back-end at all, they're static, just HTML and CSS sitting there. When one's needed, it usually comes bundled with whatever's building the site (Cloudflare Workers, Supabase edge functions, a Node server). Take whatever the site builder offers rather than shopping around separately. It'll save you a headache.

The usual mix-up

People think every website needs a big complicated back-end. Most don't. Loads of small sites are static and completely fine that way. Only bother once there's something to check, save or send.

Where you’ll use it

Also comes up in: build me a website.

All the words