Designs and ships pages
Custom pages, forms, and dashboards built from your real tables, then styled to your brand instead of a default template.
Proto · the AI coworker in ERP•AI
An AI coworker
with hands.
Proto designs pages, writes code, ships deployments, and cleans your records, while you stay in charge.
- Tables
- Columns
- Views
- Pages
- Forms
- Records
- Workflows
- Documents
- Roles
- Analytics
- Deploys
- Skills
Capabilities
It does the whole job.
Not a chat window that describes the work. A coworker that reads your schema, makes the change, checks it, and hands back something you can open.
Writes and runs code
Scaffolds the app, wires the API, runs the build, and keeps going until the checks pass. You get working software, not a diff to review line by line.
writesapp shell · routes · types
runsbuild · lint · smoke test
shipsapi · jobs · hosting
scaffoldapi routesbuildsmoke testdeploy
Keeps records honest
Finds duplicates, normalises values, and bulk-processes rows so the app runs on numbers you can defend.
dedupemergeimportvalidate
Takes the routine
Turns a repeated chore into a workflow that fires on a record change or a schedule, and reports back when it runs.
triggersschedulesnotifications
Puts it on a real URL
Deploys the finished thing to a live address, looks it up in a browser, and tells you what it saw.
https://your-app.build.hostThree moves,
no ceremony.
-
01
Say it plainly
Describe the outcome in one sentence. Proto reads your schema and your permissions before it touches anything.
-
02
Watch it work
Every table read, file written, and record changed shows up as it happens, so you are never guessing what it did.
-
03
Keep it or undo it
Approve the result, or roll it back. Version history and snapshots keep every change reversible.
It works inside your rules.
Permissions, approval gates, and audit trails are enforced by the platform, not promised by the model. Proto can only do what your role already allows, and anything that needs a sign-off waits for one.
Questions worth asking.
Where does Proto actually live?
Inside ERP•AI, next to your apps, tables, and records. There is nothing to install and no separate account: it works on the data you already keep there.
What is it allowed to change?
Tables, columns, views, pages, forms, workflows, documents, records, and deployments. Every write goes through the same permissions your own account has, and actions that need approval stop and ask.
Do I need to know how to code?
No. You describe the result in plain language. Proto handles the schema, the page building, and the deployment, and explains the trade-offs in the same conversation.
What if it gets something wrong?
Ask it to fix it, or roll back. Branches, version history, and snapshots mean a bad change is recoverable rather than permanent.
Does it work on more than one app at a time?
Yes. Proto can work across apps in your organisation, including cloning a proven app and adapting it to a new vertical, or running the same change across several apps.