Your team can add features with AI coding tools, on code prepared for them, while the core stays sealed. Describe the feature. Your tool builds it next to the engine, the gate checks it, you approve it on staging.
Not magic. Named files, a typed SDK, and a gate that says no. Every item below ships with your copy.
Tells Claude Code, Cursor, Codex or Replit what the system is, where it may write, what is sealed, how to test and how to roll back.
Typed contracts and a worked plugin. An AI tool adds a feature as a plugin without touching the core.
Typecheck, guards, engine integrity and a full order run before anything goes live. A broken change never reaches a shift.
Ready plugins for the common asks, free with updates. The no-code rung.
Our own vibe-coding surface, inside your admin, with the guardrails built in. The recommended path once it lands.
Not the part that costs money. Totals, kitchen stages, migrations and card capture live in the sealed engine. AI tools work next to it, never inside it.
of developers use or plan to use AI coding tools. 46% distrust the output. That is why the core is sealed and every change is gated.
Changed code is yours to maintain. Updates never overwrite your workspace. If you would rather not touch it, ask us: custom features are a service, built into your copy and yours afterwards.
Most systems give you one answer: wait. Your copy gives you three.
139 features across 14 areas. 71 included today, 68 labelled coming soon. Nothing hidden behind a tier.
See all 139 ›Common additions ship as RestaKit plugins. Install, configure, done. New plugins arrive with updates. No code.
How plugins work ›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 ›Beta invites go out in small groups. Tell us what you want to change and we show you how it ships: plugin, your tool, or us.