How Bnome works— from how your business works to the software it runs on.

How it works — one agent, one system, one database

A business on Bnome is a system: a few programs, each at its own address, that share a database — the app your clients open, the desk your team works from, the jobs that run on their own. One agent runs the whole system. It plans before it builds, writes and runs the code, checks that every program answers, and fixes what does not.

You talk to it in one chat, and you see everything it built on one canvas.

Start a system — describe the business, not the screens

1. 1
   Say how the business worksWho your clients are, what they buy or book, what you do for them, what you want to stop doing by hand. A sentence is enough to start.
2. 2
   The agent works out what it needsBefore any code it writes down the plan: the people, the data, the services worth connecting — and tells you what only you can do.
3. 3
   It builds the first programsUsually the app your clients use and the desk you run it from, on one database, each live at its own address within minutes.
4. 4
   It checks its workWhen it is done, the platform checks that every program answers. Anything down goes back to the agent with the report.

The canvas — the whole business on one plane

The canvas shows the system as it is: the programs, the databases they keep, the services they use, the links between them, and the board the agent draws for you — how an order moves, live tables, what is waiting on you.

Data opens every database the agent made, read-only, with search and CSV export. Click a program to open it right there, on a screen or on a phone.

Change it by talking — one chat for the whole system

Ask for anything — a new field, a page, a whole new program, a different flow. The agent changes every program the request touches and checks the system again. Point at something on the canvas to attach it to your message.

Each change costs what it took, in credits; the running total of your system sits under the chat.

Your clients and your team — the same records, from both sides

A client gets an app of their own, often behind a private link: they see only their things, choose, confirm or leave a note. What they do lands in the database at once, so your desk and your canvas show it within seconds — with their words.

Connect services — the agent asks for what it needs

When a program needs a service — Gmail, Google Calendar, Sheets, Stripe, HubSpot, Telegram, ad accounts — the agent asks for it and sends you a link. You sign in once; the program can use it from then on. More than 1,500 services are in the catalogue.

Programs that work together — events, queues and jobs

Programs of a system talk through the platform: one announces an event and the others react, one hands tasks to a queue another works through, one calls another directly. Delivery is kept and retried when a program is busy or down.

Recurring work runs on a schedule — every few minutes, or every day at a time in your time zone — with each run recorded.

Addresses and domains — live from the first build

Every program lives at its own address on bnome.app, which you can rename. On Pro you can put a program on your own domain: add the record Bnome shows you, and the certificate comes by itself once the internet catches up.

On the free plan, an app nobody opened for a day sleeps, and wakes in a few seconds on the next visit with all its data.

AI inside your apps — no keys, no setup

The apps can use AI themselves — answer in text, draw images, make video and music, turn speech into text — through Bnome, without API keys. It is paid from the same credits as everything else, at the rates on the pricing page.

Bring what you have — an app, or your data

Bring an app from GitHub or a zip, and the agent moves it onto Bnome. Keep your data in Airtable, and the agent builds the apps on top of the base you already have.

Plans and credits — one balance for everything

A credit is a cent. Every plan comes with credits, and they pay for the agent’s work and the AI inside your apps; packs top them up and never expire. If you run out, the agent waits — your apps stay up.

MCP — Bnome inside your AI agent

MCP is the open standard for connecting tools to AI. One command connects Bnome to Claude, Cursor, Codex or Windsurf, and your agent builds, changes and publishes apps right from the conversation.