Agent-first business admin
Run your business with agents, on data you control.
- Secure
- Your own database
- One revocable key per agent
Your coding agent builds the admin on AdminForth: customers, orders, jobs and money in your own database, with sign-in, team permissions and a change history that names the agent. Then you and your team work through Claude Code, Codex or any agent that speaks MCP. Screens are there when you want to look.
No development team. Open source, MIT, on your server.
Audit logToday 09:04Mayacodex@0.46 · Maya’s laptopUpdate · REQ-1042
An example business admin built with AdminForth. Northstar Services and its records are made up.
What AdminForth gives you
Your agents can already do the work. This is what keeps it safe.
01 · Security
Your data stays yours, and stays patched.
Your records live in your own database on your server. Agents get in through one locked door: sign-in, a separate key per agent that you can revoke, two-factor and passkeys for people.
The parts you can’t review yourself come from AdminForth, one framework our team maintains. Security fixes ship with its updates. Updating is a version bump your agent runs; skills tell it how.
02 · Your team and their agents
Everyone works inside your rules, and you see who did what.
Your team uses agents too, on the same records. Each person, and each of their agents, sees and changes only what their role allows. The server checks every request, from a browser or from an agent.
The audit log names the person and the agent for every change. When something looks wrong, you know who, when, through what, and what it was before.
03 · Screens, optional
Ask your agent. Open a screen when you want to look.
The admin is where your business is administered: records, rules, access, history. The panel is one way in; your agent is another. Most days you won’t click through forms: you ask, the agent does it. The screens and dashboards are still there, for the overview, for a teammate who prefers them, and for checking what the agent did.
Sound familiar?
What stops a founder from letting agents run the business.
“My customers and orders live in chats and spreadsheets. The agent can’t reach them, or reaches them with no control.”
One back office, one locked door.
Your data in your own database. Every agent connects with its own key, under one person’s permissions.
“An app my agent generated is a hole waiting to be found.”
The security parts come from a maintained framework.
Sign-in, sessions, two-factor, permissions, audit: not generated once and forgotten. One framework, maintained by us.
“If my team’s agents can change anything, who stops a wrong change?”
Rules on the server, for people and agents alike.
A manager’s agent sees the manager’s requests. Nothing else, no matter how it asks.
“An agent changed something and nobody knows what.”
A change history that names the agent.
Who, when, through which agent, old value and new value.
“I don’t have developers, and I don’t want to depend on one.”
Your agent builds it. You own it.
Open source, MIT, your server. The next change is a sentence to your agent.
How it gets built
You don’t need a development team. You need these three.
You
Describe the work in plain words: what you track, who does what, what keeps slipping. Check the result in your browser.
Your AI agent
Claude Code or Codex writes the code, runs the app and connects itself to it. Afterwards it is how you work with the data.
AdminForth
The maintained foundation: sign-in, permissions, audit log, MCP, record screens. One framework and its plugins, maintained by us.
Your business admin
Your records, your rules, your server. Agents and people work in it; the history shows who did what.
How it works
One operation, through the agent.
Northstar Services, a made-up maintenance company, runs on an admin built with AdminForth. Maya owns it; Tom and Priya are managers. Each of them talks to their own agent.
“Which follow-ups are overdue?” then “Set the next action for REQ-1042.” The agent reads and writes through the app’s MCP tools, as Maya, with her permissions.
Tom is a manager. His agent asks for Maya’s request; the server refuses, not the agent. The same rule holds for a browser, an export or a direct request.
Every change is a row: who, when, through which agent, what it was before. Maya opens it when something looks off, or asks her agent what changed.
Build yoursNorthstar Services and its records are made up for this example.
Start with your agent
Describe one part of your business. Your agent builds the rest.
Fill in three lines, copy the build instructions, and give them to Claude Code or Codex in a project folder on your computer. The instructions include MCP and the audit log from day one.
- 1
Describe
- 2
Open your agent
Press Prepare my instructions to get the text for your agent. It includes your answers and everything the agent needs to start.
Your agent runs on a computer. Copy or download the instructions now and continue there.
- Install the Claude desktop app and sign in with an account that includes Claude Code. Setup guide
- Create a folder for the project, for example
my-business. - Open the Code tab, choose your computer as the environment and pick that folder.
- Paste the instructions into a new conversation and send them.
Use your own coding-agent account. Access and usage costs depend on your provider.
Prefer the terminal?
Run this in your project folder. When the agent opens, paste the build instructions into its prompt.
claudecodexNot installed yet: Claude Code CLI · Codex CLI
- 3
Connect and work
The agent builds the first part with sample data, runs the app and connects itself to it. From then on you talk to your business. Prompts for the first day, with the example above:
- What needs my attention today?
- Which follow-ups are overdue, and whose?
- Add a request from Harbor Café: office maintenance quote. Owner Maya, next action: send the quote by Friday.
- Create a follow-up for Priya: call Brightside School tomorrow at 9.
- Which invoices are unpaid for more than 30 days?
northstar.app/settings/agentsThe Agents settings page with the Connect agent button and one row per connected agent. Each teammate connects their own agent from their own account. A revoked connection stops on the agent’s next request.
Questions
What it costs and who looks after it.
Free
- The AdminForth framework: MIT license, no paid tiers
- The 30-minute call about your process
Paid separately
- Your coding-agent subscription and model usage
- Hosting for your app and database
- Paid services you connect
Do I need a developer?
No. You describe the work, your agent writes the code on AdminForth, and you check the result in the browser. You still decide when a change is ready for your team. Hosting and backups are set up with the agent, and you own them.
Is this a ready-made CRM?
No. AdminForth is an open-source framework for building your own business admin: customers, orders, jobs, stock, invoices, whatever you run. Your agent builds the parts you need, around your fields and your rules.
Does an AI provider see my data?
Your app and database run where you host them. Whatever your agent reads through MCP goes to that agent’s model provider, under the permissions of the person who connected it. Compatible self-hosted models work too.
What about updates and security fixes?
The security parts, sign-in, sessions, two-factor, permissions, MCP, audit, live in the AdminForth framework and its plugins, which our team maintains. Your app updates by bumping their versions, which your agent can run. Your own code stays small: your fields and rules.
Can I change the admin later?
Yes. Ask your agent for the next field, stage, part or report. Every generated app carries instructions and skills for coding agents, so each change builds on what is there. Check changes before your team relies on them.
Where will the app run?
The first version runs on your computer. For your team it goes on a server you control; your agent prepares the deployment, you decide where it runs and how it is backed up.
What happens on the free call?
We talk about one process in your business, where the current approach gets in the way, and whether AdminForth is a good foundation for it. Implementation and hosting are separate from the call.
Talk through your workflow with Ivan BorshchovMaintainer of AdminForth
Bring one messy process. Let’s map a better way to run it.
Book a free 30-minute consultation about your business workflow. We’ll discuss what you track today, where work gets stuck, and whether an admin built on AdminForth is a good fit.
- What should your agents and your team be able to do?
- Which part could you build first?
- What would hosting, integrations and ongoing support involve?
Bring a description of one process or an anonymized example. The consultation is free; implementation and hosting are separate.