How AdminModule works
One prompt connects your app. AdminModule does the rest — and keeps up with every change your agent ships.
Add your project
Name the app in AdminModule and get its project ID and secret. Nothing to install locally.
Paste one prompt
Your coding agent reads the AdminModule protocol, installs a single server-side bridge and publishes a semantic manifest.
AdminModule renders itself
Resources, fields, saved views, relationships and actions come straight from the manifest — no configuration screens.
Run your app
Operate customers, listings, orders and support from one place. New actions appear the moment your app republishes its manifest.
Why not just ask Lovable for /admin?
You can build /admin.
Or you can stop rebuilding it.
Lovable can build a custom admin panel. But then you have another interface to design, prompt, maintain and rebuild for every app. AdminModule turns that second app into a service — resources come from your app's manifest, and actions run your app's real business logic.
No second UI project to maintain
Ask Lovable for a new action — AdminModule updates itself
One operating layer across every app you build
Your app stays the source of truth
Keep Lovable for building your app. Use AdminModule for running it.
Every app eventually needs a second app: the one you use to run it. AdminModule is that second app.