The first restaurant system you own.
Pay once. No monthly licence. You pay only your own hosting. Your copy runs in your account, your developer or your AI tool can change it, and it keeps running whatever happens to us.

One licence fee for your copy. No monthly software fee, ever. Hosting is yours and stays small.
Run it where you choose: your own cloud account, your database, your security setup. We install it for you if you want.
Screens, workflows, integrations, new features. Your developer, any developer, or your AI coding tool.
The engine never phones home to keep running. Source escrow ships with your copy. If we stop, you don't.
Six layers in every RestaKit copy.
Six things, delivered together. Only one of them is sealed, and it is sealed for your protection.
The licence text is published before any payment is taken. You may not resell or relicense RestaKit itself.
Three ways to add a feature: included, plugged in, built.
Most systems give you one answer: wait for the roadmap. A copy you own gives you three.
It already does it
139 features across 14 areas. 71 included today, 68 labelled coming soon. Nothing hidden behind a tier.
See all 139 ›A plugin covers it
Common additions ship as RestaKit plugins. Install, configure, done. New plugins arrive with updates. No code.
How plugins work ›Build it
Your developer, or your AI coding tool, on a kit prepared for exactly that. Or ask us and we build it into your copy.
The vibe-coding kit ›Plugins: small packages with declared permissions.
A plugin is a small package with a manifest that says what it may touch: which routes, which tables, which events. The engine enforces it. Install one from the RestaKit catalogue, or write your own against the SDK.
- Catalogue plugins are free with updates
- Every plugin declares its permissions; the engine refuses anything else
- Payments arrive as the first plugin: card data never touches your engine
- Third-party plugins install with a named source and a permission review

Source escrow: your copy keeps running without us.
Nothing, for you. The engine has no kill-switch and no licence check at boot. Your copy keeps serving tables.
The source escrow archive delivered with your copy means you, or any developer you hire, can keep it alive and keep improving it. That is the difference between a licence and a subscription.
Subscription vs owned, side by side ›Questions owners ask before they buy
Get your own copy of RestaKit.
Beta invites go out in small groups. We set it up on your menu, walk you through it, and put your package in writing. One payment, then it is yours.