SHEET 03 · SITES YOU CAN OPEN
Three sites. One backend.
The quickest way to judge whether "keep your own front end" is real is to look at sites that did. These three run on EveryonePlans and look nothing like each other — or like this site.
These are our own sites, not customer case studies. We build and run them on the same platform we sell, which is why we can say what it does rather than what it should do.
01REAL BUSINESSES, RUNNING TODAY
Same engine, different front ends.
Events and ticketingutahsevents.comA public events site: listings, event pages, registration and entry, with a warm consumer design that looks nothing like this one.Open it next to this page. Same backend, same events and ticketing capability, completely different front end — which is the clearest demonstration available that the design and the engine are genuinely separate.Service businessgoholidaylogic.comA seasonal service business running its operations on the platform — customers, scheduling, jobs and invoicing behind a public site of its own.The everyday case: a business whose customers never think about the software, and whose owner is not running the company out of a spreadsheet.
02IF YOU WANT TO BUILD YOUR OWN FRONT END
Build your own front end
bringthefront.com
The deep end. BringTheFront is where the platform is documented as something you build ON: how to stand up your own site against this backend, what the template gives you, what the API expects, and how to keep your own design while the operations run here.
Start here if you already have a front end, or intend to build one. It is the practical version of everything the rest of this site describes — the guides, the setup walkthrough, and the AI-assisted build path.
This is where the technical story lives. If you want to see how a site is actually put together on top of this platform — the front end, the API calls, the upgrade path — go there rather than reading about it here. You do not need any of it to use EveryonePlans; it is for the people who want to build on top of it.
03IF YOU WOULD RATHER NOT BUILD IT
Or we build it for you — and it still gets our updates.
If you want a custom site but would rather not build it, we will. It is made from the same template our own sites use, so it stays on the upgrade path: when we improve the backend, your custom site merges the release like everybody else instead of drifting into a fork only you can maintain.
Bespoke, without becoming an orphan
Custom work usually means a codebase that stops receiving improvements the day it is delivered. Yours keeps the template as an upstream: releases merge in, and an automated check tells you if a customisation has taken you off the path so it can be moved into a supported seam instead.
The signed-in views are yours to brand too
It is not only the public site. The authenticated app takes your colours, type and radius, and which modules appear is driven by your organization’s mode — so the place your customers and staff actually work looks like you, not like us.
You can take it over whenever
It is your repository and your deployment from the start. If you want to bring it in-house, or hand it to another developer, nothing has to be extracted from us first.
YOUR TURN
The fourth one can be yours, and it can look like anything.
Create a free account and look around the back end. When you want your own front end on top of it, BringTheFront is where that is documented.