Prebuilt modules you switch on

Tick a box in project settings and get working login, payments or a settings page, instead of generating that plumbing from scratch every time.

Every extension needs roughly the same foundations. A configuration page. Somewhere to store things. User accounts, if it has users. Payments, if it charges for anything.

Today all of that gets written fresh for each build. That means it is subtly different every time, and differently broken every time. It also means the same person builds the same login screen five times across five extensions.

What this should be. A short list of modules in project configuration. User registration and login. Payments. Settings and configuration page. Basic content management. Tick what you need and it is generated into the project, already wired together and already tested.

The important design decision. These must point at your own backend, not ours.

Tick login and it generates Supabase auth into your project using your keys. Tick payments and it wires Stripe to your account. You get plumbing that has been tested once and used by everybody, and we never hold your users or your money. You can still take the code and run it without us, which is the promise we make everywhere else and are not going to quietly break here.

The alternative, where login and payments run on our servers, would ship faster and make every customer dependent on us. Not doing that.

Honest scoping. This is a real project rather than a small addition. Auth and payments both need something server side, and getting that right once is exactly the reason to do it centrally. The first module matters more than the list: better to have one that people actually use than four nobody switches on.

Requested by a customer, 5 September 2026, who put it well: "you know it works, it is tested, and it is secure, because it is done once for all."