Start here
What Cnter is
One dashboard your customer edits, one API your site reads. How the two halves fit together.
Cnter is the back office behind a website. Someone non-technical edits content, takes orders, answers reservations and gets paid from one dashboard. Your site reads all of it over HTTP. The two halves never share a codebase, a deploy or a database.
That split is the whole idea. A restaurant that wants to stop delivering on a quiet Monday should not need a developer, and a developer should not have to build a menu editor before rendering a menu. So the editing surface ships once, for everyone, and your site stays a site.
The shape of an integration
Every integration, whatever module it uses, is the same three pieces.
- 01
The dashboard
Where your customer works. Content, orders, reservations, bookings, payouts, email. You do not build any of it and you cannot break it.
- 02
The API
One host, one organization id, one API key. Some endpoints are public and safe in a browser, the rest need the key and belong on your server.
- 03
Your site
Anything that speaks HTTP. Next.js, Astro, WordPress, a static build. Cnter has no opinion and no SDK you are obliged to install.
Organizations
Everything in Cnter belongs to an organization. It is the tenant boundary: content, orders, reservations, API keys, payouts and members all hang off exactly one of them, and nothing crosses over. One person can belong to several organizations and switch between them in the dashboard, which is how an agency runs twelve restaurants from one login.
For you this means the organization id is not a routing detail you can leave out and add later. It selects the tenant. Every request carries it, either in the URL for public endpoints or implicitly through the API key, which belongs to one organization and cannot read another.
Modules
The dashboard is not one product. It is a set of modules an organization switches on individually, and a module that is off is absent rather than empty: no sidebar entry, no settings panel, and no place in the manifest the client reads.
| Module | What it does | Docs |
|---|---|---|
| Content Management | Structured content types and entries. Also the catalog every order flows through. | Content Management |
| Online Ordering | Cart to paid order, with Stripe or pay in person. | Online Ordering |
| Restaurant Ordering | Pickup, delivery and dine-in, a live kitchen board and printed tickets. | Restaurant Ordering |
| Promotions | Automatic discounts and codes, applied server-side. | Promotions |
| Bookings | Appointments with a date, a time and a meeting type. | Bookings |
| Reservations | Table reservations, opening hours, slots and approval. | Reservations |
| Contact Form | Form submissions, notification email, and replying from the dashboard. | Contact Form |
What Cnter is not
- Not a site builder. There are no themes, no page editor and no hosting. You build the front end.
- Not a database you can write to freely. The API exposes the operations the modules define, and nothing underneath them.
- Not a payment processor. Payments run through AgnusPAY on top of Stripe, and the money moves between Stripe and your customer.