your own erp,
running in minutes,
on a machine you own.
tell the ai what your business needs and it sets the app up on a machine you own. then you just use it: say what happened and it's entered. forms are still there if you like, but why, when the ai can fill them in? and when nobody's using it, the app sleeps and you stop paying. no it person. no vendor's cloud holding your data.
you i run a 10-person shop. i need accounting and inventory. agent that's erpnext. needs 4 gb, so a size-m node. creating it. node create --pool home --size m ........ ok install erpnext ......................... ok agent done. your erp is live at your-shop.apps.inferapps.com you invoice acme for 40 hours at $120, due in 30 days. agent done. invoice for $4,800 created and entered under acme. (no form. the app is headless; the agent used its api.) ... six hours of nobody using it ... the app is asleep, the meter is off. you what's still unpaid? waking ... agent acme owes $4,800, due in 30 days. nothing else is open.
to use software, you first become an operator.
pick a vendor. pick a plan. pick a region, a size, a database, a backup tool. then upgrade it, patch it and hope it survives the weekend. or hand your books to someone else's multi-tenant stack and rent your own data back by the seat.
the work was never the accounting. it was everything around it.
and after setup it gets worse. you type the same invoice into the same form every day, and the server you chose runs, and bills, all night while nobody's there.
setup and data entry are decisions, not jobs. decisions are what agents are for.
an inferapp.
the "infer" is the point, and it doesn't stop at setup. you state the intent. the agent works out which app, how much memory it needs and how it's configured. then, every day after, you say what happened and the agent enters it, through the app's api, with no form.
| it is not | because | |
|---|---|---|
| saas | someone else's stack | it runs on a node you own |
| paas / one-click | a human picking a template | an agent makes the decisions |
| generated app | code a model wrote just now | a mature app, like erpnext, that has run for years |
say it once. keep saying it. pay only while it's awake.
- ①intentsay what the business needs, in plain words, to an agent or in the app.
- ②provisionthe agent picks the app and the node size it needs (s, m or l: 2, 4 or 8 gb), creates the node in your account and installs the app, with its own database where it needs one.
- ③usea real, persistent app at its own address. your people can sign in and click, or tell the ai what happened and it's entered. same app, same data, either way.
- ④sleep and wakeno requests, no running app. the next request wakes it. you're billed for the minutes it's awake.
- ⑤operatebackup, upgrade, resize, delete. the agent drives them through the same cli you can.
pay per minute. not per month.
most business apps sit idle most of the day. a shop's books are open for a couple of hours. an always-on server bills for the other twenty-two.
an inferapp sleeps when nothing is asking for it and wakes on the next request, so you pay for the minutes it's awake. an app in use about two to three hours a day costs roughly 90% less than the same app running around the clock.
the trade: the first request after a sleep waits while the app wakes. for erpnext that's a short wait, not instant. the agent can wake it ahead of the work you ask it to do.
only apps an agent can fully run.
an app earns the inferapp label by passing one test: an agent can operate it end to end through its api, with no clicking through a ui. each entry declares what it needs, so sizing is a fact and not a guess.
erpnext
accounting, inventory, sales, purchasing, hr. runs with its own mariadb, and sleeps to zero when idle.
more back-office apps
added to the catalog one at a time, each passing the same api-only test first.
bring an app
the catalog is managed from the cli and a screen. an entry is a declared need, an image and a minimum node size.
$ inferapps node create --pool home --size m $ inferapps catalog list
owned, not rented.
apps are becoming something agents operate. when that happens, someone has to host them, and the box and the data should belong to the people who use them.
your node. your machine, your region, sized to the app. your data. it stays on your node, awake or asleep. your exit. it's a normal app on a normal machine. nothing to unwind.
what this is today.
inferapps is early. erpnext is the first app in the catalog. the agent and the command line are real, and so is the node. the catalog is short on purpose.
"infer" means a model sits at the front of the app, not only at setup. today that model deploys, sizes and operates it, and the app sleeps and wakes on its own. telling the ai what happened, instead of filling in forms, is where this is going: the example at the top shows the goal, not a shipped feature.