AbideBotSoftware your AI can actually use.
Your agent is designed to read what an app shows and fill in the values the app is waiting for, just as your own input does. No screenshots, no clicking. Apps are written in munu, run on munuOS, an always-on operating system, and appear in munuScene, the browser.
It abides. AbideBot is in development. Joining the waitlist is free, and nothing is charged before paid plans launch, planned for around May 2027.
An OS, a browser and a network, all written in munu.
munu is the programming language AbideBot is written in. Your agent writes munu programs, munuOS runs them and munuScene shows them. The network is planned to carry munu data too.
munuOS In development
The always-on operating system your agent lives in.
munuOS is a minimal Linux-based operating system image where munu is the first process. It runs your munu programs and your agent, always on, one per customer, never shared. Rent one hosted by us, or run it on your own hardware.
- Your agent, its memory and its jobs live here
- Changes go live only after they compile and pass their checks
- A protected core that boots with only the essentials
munuScene In development
The AI-native browser: apps as scenes, not pages.
munuScene draws munu apps from scenes instead of rendering web pages. A scene is plain data, so your agent is designed to use apps directly, as a first-class user: it reads the scene and binds the variables the app is waiting on, where other agents take screenshots and guess.
- It does not render ordinary HTML websites
- You and your agent see the same app
- Risky steps wait for your approval
The network Planned
Everything as live, shared data.
Documents, sites and apps are designed to be psi-terms: shared structures that each party fills in, with a conflict caught instead of overwritten. They are planned to flow between munuOS machines as global dataflow, over hyperbolic routing, encrypted end to end.
- Every bot reachable by its QR code
- Only changes travel, not whole files
- A private network, not the public web
Built for an agent that does the work itself.
Most AI agents are bolted onto software made for people. AbideBot is designed the other way round.
It uses apps directly Designed for
An app in munuScene is a scene: a tree of values the agent can read. It is designed to read exactly what is on screen and fill in the value a control is waiting for, by name, with no screenshots, no pixel guessing and no scraping. That is also designed to need far fewer AI calls than reading images, though we will publish benchmarks before we claim savings.
It stays on Designed for
munuOS is designed to run all the time, so routines, watches and replies keep going when your laptop is shut. When a part fails, munuOS restarts it by the rule written in its code, and a bad change rolls back to the last good one.
Its code is checked before it runs
Dude writes small munu programs for your tasks. The compiler rejects a missing case, a recovery rule for a failure that can never happen, or two parts that disagree about a value’s type, and the error goes back to the agent to fix. See the real code →
Rules and deadlines live in the code
How each part recovers, how fast it must answer and where order may vary are written in the program itself, as formulas the compiler turns into checks. munuOS is designed to measure every run against its deadline and report a miss, not hide it.
Your agent is called Dude. Rename it if you like.
Every new agent starts out as Dude. Call yours anything you like. Whatever its name, it writes real munu programs for your tasks, and checks them before they go live.
- You don’t need to learn munu. Ask in plain words. Dude writes the program, compiles it on your munuOS machine and fixes what the compiler reports.
- Calls the AI only when it needs judgement. The routine runs as checked code, so the model is not asked about every step.
- Approvals only a human can give. Risky steps pause until you approve them. The agent cannot answer for you.
- A factory reset that always works. A protected core can boot with only the essentials, so a bad change can never lock you out.
Where it’s going, in order.
These are plans, not promises. Dates may move, and we will say so when they do.
- Now
Building
munuOS, munuScene and the munu compiler are in development.
- Around Feb 2027
Beta for developers
For developers and munu enthusiasts: a hosted developer munuOS machine, and free self-hosting on your own hardware.
- Around May 2027
Paid plans
Hosted plans open, priced as in the draft below.
- Later
Teams, then operations
Plans for development teams, then for ops and SRE teams who need agents that keep running.
- After that
Small businesses
Businesses run from AbideBot accounts, with their messages, sites, graphics and documents on the network, starting with clusters of businesses that work together.
Three ways in.
Join the beta waitlist
Be first onto the developer beta, planned for around February 2027. Free to join, and no payment is taken.
Join the waitlist →Self-host free Planned
The same munuOS image we host is planned to be free to run on your own hardware. The code is not public yet. Join the waitlist and we will tell you when it is.
Tell me whenLearn munu and build apps
See how munu works, from functions and streams to supervision, ports, psi-terms and routing, with real excerpts from its source.
munu for developers →Host it with us, or run it yourself.
Paid plans are planned for around May 2027. Until then every button adds you to the waitlist or starts a conversation. Nothing is charged.
Uptime figures are targets, not commitments, unless a plan says it includes an SLA with service credits. The Business SLA node’s SLA is planned and not yet available.
Prepaid, capped, and never billed after the fact.
Plans include no AI credits. AbideBot handles model access for you, so you never need your own AI account or key.
Top up a prepaid balance
Save a card, then top up your AI balance by hand or turn on auto top-up.
Set your own limits
You choose the spending limits. They live in a protected core that agents cannot change.
Provider cost plus a disclosed markup
Usage is charged at the model provider’s cost plus a small markup, which we disclose. When the balance reaches zero the AI stops. You never get a surprise bill.
There are no free AI credits and no free AI trial.
Questions, answered calmly
What is munu?
munu is the programming language AbideBot is written in. Programs are made of finite functions (mu) and ongoing streams (nu), grouped into contracts that state their own recovery rules and deadlines. munuOS runs munu programs, munuScene draws munu apps, and the network is designed to carry munu data. More for developers →
Do I need to learn munu to use AbideBot?
No. You ask Dude in plain words and it writes the munu. Learning munu is for people who want to build their own apps for the network.
Is munuScene a web browser?
No. munuScene is a browser for munu apps, and it does not render ordinary HTML websites. It is designed for munu apps and sites, drawn from a scene graph your agent can read and act on directly.
Do I host munuOS myself, or rent it?
Either. You are planned to be able to run munuOS free on your own hardware, or rent a machine running it, hosted by us on a monthly plan. Both run the same munuOS image. Firms that host it themselves can add paid support. Self-hosting is planned, and the code is not public yet. Join the waitlist and we will tell you when it is.
Is my munuOS machine shared with other customers?
No. Each customer gets a separate virtual machine running munuOS. Customers never share a machine or its core.
Is there an uptime SLA?
Not yet. The Team node is designed for a 99.5% uptime target, shown on a public status page, with no service credits. A monthly SLA with service credits is planned for the Business SLA node, which is coming later.
Can agents see all my files?
No. They can read and write only what you grant, and you can revoke a grant at any time. Code written by the AI never runs on your own computer with your computer’s permissions.
How is AI usage billed?
Through a prepaid balance that you top up by hand or automatically. It is charged at the model provider’s cost plus a small disclosed markup. When the balance reaches zero, the AI stops. Nothing is billed after the fact.
Why is my agent called Dude?
It is the default name. Rename it whenever you like.
When can I start?
A beta for developers is planned for around February 2027 and paid plans for around May 2027. Dates may move. Join the waitlist and we will email you.
Get on the list.
Leave your email and the plan you are interested in. We will contact you when the beta opens. No payment is taken.