The same backend, every project
Pages, a diary, payments and traffic, already built and kept running. You write the front end the client is paying for.
For developers
A backend for the websites you build
In short
Content, bookings, payments and analytics for the websites you build, through one API and a TypeScript SDK, with a key per website.
- Bookings
- Content
- Payments
- Web analytics
- Inbox(not used here)
Every part in every plan, USD 9.00 a week or USD 29.00 a month. Updated 8 October 2026.
site.ts
import { Client } from '@backendfree/core'; import { Cms } from '@backendfree/cms'; import { Bookings } from '@backendfree/bookings'; // One key per website: the key says which site is asking. const client = new Client({ origin: 'https://backendfree.com', key: 'pk_live_...', }); const cms = new Cms(client); const bookings = new Bookings(client); const home = await cms.page('home'); const { slots } = await bookings.availability({ service });
The part of every client site you keep rewriting
Becoming the host forever
The account and its keys are your client's. You build the front end and hand it over, and the backend is not yours to keep alive.
Webhooks you cannot trust
Every delivery is signed with a timestamp, and verifyWebhook checks both before it parses a byte.
What you build with
6 packages, one key per website
Plain ES modules with no dependencies. The limits are read from the code that enforces them.
Packages
- @backendfree/coreThe client every other package is built on: keys, errors, caching, idempotent writes and verifying a webhook.
- @backendfree/cmsPublished pages as the typed sections the owner edits, and knowing when to rebuild.
- @backendfree/bookingsServices, staff, free times and taking a booking, with a token the customer manages it by.
- @backendfree/paymentsTaking a payment into the business's own account, from your own server with a secret key.
- @backendfree/webanalyticsReporting page views from your own server, for the visitors and crawlers a script never sees.
- @backendfree/inboxSending a contact form's message to the website's inbox, past the spam checks, and reading them back.
Limits
- 250,000 requests a month per account
- 300 a minute per visitor with a publishable key
- 600 a minute with a secret key
- 4 signed webhook endpoints per website
Questions
What developers ask
Each answer starts with the answer.
Which frameworks does it work with?
Any that can make an HTTP request. The SDK is plain ES modules with no dependencies, and the API is JSON over HTTPS.
Can one front end serve several websites?
Yes. No path names a website: the key says which one is asking, so swapping the key swaps the site.
Can I manage several clients from one login?
No. An account has one person on it. Each client holds their own account, which is also what makes handing a site over clean.
Is there a test mode?
Yes, a full one. Test keys read the same services and pages as live ones, and what they book or pay is test data: it holds no real customer's slot, its emails go to you, its payments run at the provider's test mode, and no report counts it.