build aninferapp.
Package the web app you already have, so it runs on anyone’s inferpod, opens in any browser and can be run end to end by an agent.
The in4 command line is shipped. The manifest, the test runner and listing in the store are a draft for review, marked coming below.
~/your-appin4$ curl -fsSL https://inferapps.com/install.sh | sh$ in4 login # approve the code in your browser$ in4 catalog list # the apps live today$ in4 app create imaarat # prints its address$ in4 deploy https://github.com/you/your-app$ - runs on
- an inferpod
- opens in
- any browser
- sizes
- s, m or l
- live today
- 2 apps
one build, five promises.
An app that keeps all five can be listed. ERPNext is the example all the way down this page.
one web build
erpnext.shop-01.inferapps.comis one app: a single container image that serves a web app, likeghcr.io/frappe/erpnext:15.4.0. It runs on the inferpod and opens in any browser on any device.the api-only test
An agent can do everything in the app through its API, end to end, with no browser and no clicks. A test runner that checks this for you is coming.
a size: s, m or l
2, 4 or 8 GB of the inferpod while awake. You choose it; the inferpod holds the app to it. ERPNext is m.
sleeps until asked
When nobody uses it, it sleeps and nothing bills. The next request wakes it.
its own database
Each install gets its own database, run beside the app, like MariaDB 10.11 for ERPNext. Data never mixes between apps or inferpods.
install in4, the command line.
in4 is the inferapps command line, and it is shipped: install it, sign in, then install a live app or deploy your own. in4 --help lists every command and in4 cli <word> finds one.
First, install in4.
One binary, checked against its SHA-256, into /usr/local/bin (or ~/.local/bin without sudo).
in4 runs on Linux (x86-64).
$ curl -fsSL https://inferapps.com/install.sh | shThen sign in.
in4 shows a short code and opens the sign-in page. Approve the same code there and it keeps a key for you, valid for 90 days. A key is never typed on the command line.
$ in4 loginSee what you can install.
Two apps are live today: Imaarat and Rakazo. The list is the catalog's own, so it is always today's.
$ in4 catalog listInstall one.
It adds the app to your workspace, waits until it is ready and prints its address. It is safe to run again: it never adds a second copy.
$ in4 app create imaaratOr deploy your own web app.
Point it at a Git repository: it builds it, follows the build until the app is live and prints its address. A private repository deploys once you connect GitHub with in4 github connect.
$ in4 deploy https://github.com/you/your-app
inferapp.json, field by field.
coming One file, inferapp.json, at the root of your project, to tell the inferpod how to run the app, how big it is and where its actions are. The format is a draft for review and nothing reads it yet: in4 deploy builds your repository as it is.
| Field | Type | What it does |
|---|---|---|
name | string | What people see in the store. |
id | string | Lowercase and unique. It becomes the address: erpnext.shop-01.inferapps.com. |
version | semver | The version of this build. A new version is a new submit. |
image | string | The one web build: a container image that serves HTTP. The same image runs on every inferpod. |
port | number | Where the build listens. The inferpod puts it behind the app’s address. |
size | "s" | "m" | "l" | 2, 4 or 8 GB of the inferpod while the app is awake. The database counts inside it. |
databaseoptional | object | null | { engine, version }: mariadb, postgres or sqlite. One per install, run beside the app. null if the app keeps plain files in /data. |
opens | path | Where a browser lands when someone opens the app, on any device. |
sleeps.after | duration | How long without a request before the app sleeps: 5m to 60m. |
health | path | Answers 200 once the app can take requests. The inferpod holds the first request until it does. |
actions | path | Your OpenAPI 3.1 file. Every operation in it is an action an agent can call. |
build one
Change the name, the size, the database or the sleep time. The file updates as you go, as valid JSON in the draft format.
inferapp.jsonvalid JSON{ "name": "ERPNext", "id": "erpnext", "version": "15.4.0", "image": "ghcr.io/frappe/erpnext:15.4.0", "port": 8000, "size": "m", "database": { "engine": "mariadb", "version": "10.11" }, "opens": "/app", "sleeps": { "after": "15m" }, "health": "/api/method/ping", "actions": "openapi.yaml"}The name is what people see in the store. The id and the address are made from it.
Its id is erpnext, so it opens at erpnext.shop-01.inferapps.com.
Pick a size.
The share of the inferpod the app may use while it is awake, database included.
4 of 16 GB on a 16 GB inferpod: size m takes 25% while awake, and 4 of these fit side by side.
Choose its database.
One per install, run beside the app. mariadb counts inside the 4 GB.
Say when it sleeps.
How long without a request before the app sleeps and stops billing. The next request wakes it.
every action, named once.
An action is one operation in your OpenAPI file. The agent reads the file, not your screens, so the file is the whole interface. The list here is a draft of ERPNext's actions, to show the shape.
openapi.yamlopenapi: 3.1.0info: title: ERPNext version: 15.4.0paths: /invoices: post: operationId: invoice.create summary: Raise a sales invoice as a draft. requestBody: content: application/json: schema: $ref: "#/components/schemas/NewInvoice" responses: "201": description: The draft invoice, with its number. "422": description: What is missing, in a sentence. /invoices/{name}/submit: post: operationId: invoice.submit summary: File a draft invoice in the books. x-inferapps-confirm: trueoperationIdis the action’s name:noun.verb, lowercase.summaryis one plain sentence. The agent reads it to choose.x-inferapps-confirm: truemarks an action that waits for a person’s yes, like filing an invoice or recording a payment.
- post
customer.createAdd a customer - get
customer.getRead one customer - patch
customer.updateChange a customer's details - post
supplier.createAdd a supplier - post
item.createAdd an item you sell or stock - get
item.listList items, with filters - post
invoice.createRaise a sales invoice as a draft - get
invoice.getRead one invoice - get
invoice.listList invoices, with filters - post
invoice.submitFile a draft invoice in the books - post
invoice.cancelCancel a filed invoice - post
payment.recordRecord a payment against an invoice - get
payment.listList payments - post
purchase.orderRaise a purchase order - post
stock.moveMove stock between warehouses - get
stock.levelRead stock on hand - get
report.weeklySales, payments and stock for a week - get
report.ledgerThe general ledger for a period
what a good action looks like
- does one job
invoice.createmakes a draft. Filing it isinvoice.submit. An agent can stop between the two.- takes typed inputs
- Every field in a JSON schema, with the required ones marked. No free-text blobs to parse.
- returns what it made
- The new invoice and its number, so the next action can use it without a second lookup.
- says what went wrong
- A 422 with a sentence: “customer Hotel Annapurna does not exist.” The agent can fix that and retry.
- works with a key
- An API key in a header is enough. No cookies, no browser session, no captcha.
if an agent can’t, it isn’t an inferapp.
An agent gets your OpenAPI file and an API key, and nothing else. It has to do every action on a fresh copy of your app. If it can, you pass. the test runner is coming Below is a preview of a run.
what it checks
- does it wake?
- The app starts from sleep and its health path answers 200.
- can it be reached?
- Every operation in the spec answers with the API key alone.
- does each action work?
- Each action, run with sample data, does what its summary says.
- is the shape right?
- Responses match the schemas in the spec.
- does it ask first?
- Actions marked confirm wait for a yes before they change anything.
what a failure looks like
One action failed, so the test does not pass. It tells you which, why, and the smallest change that fixes it.
a failed run · previewok customer.create doneok invoice.create donefail payment.record failed 302 to /login: this route wants a browser session fix: accept the api key on POST /paymentsnot passed · 17 of 18 actionswake on the first request
- asleep
Nothing runs and nothing bills. The data waits on disk.
- a request arrives
Someone opens the address, or an agent calls an action. The inferpod holds it.
- it starts
The app and its database start from where they stopped.
- health says yes
Your health path answers 200. That is the only signal the inferpod waits for.
- awake
The held request goes through. Every request after it goes straight in.
- quiet again
No requests for sleeps.after, and it goes back to sleep.
what your app has to do
- start fast from cold
- Run migrations when a version is installed, not on every start. Load lazily.
- answer health honestly
- 200 only when a real request would succeed; anything else while it is still starting.
- keep state on disk
- In the database or in
/data. Memory is gone after sleep. - stop cleanly
- Finish writes when it gets
SIGTERM. Sleep is a normal stop, not a crash.
submitted, reviewed, listed.
A person at inferapps reads every submission and writes back either way. a submit command is coming Until then, write to us with your repository.
Send the repository, or the image, with your OpenAPI file to hello@inferapps.com.
list your appIn review we check that the api-only test, run again on our side, the size holds under real use, it sleeps and wakes cleanly, each summary says what the action does, data stays in its own database and that it says plainly if anything leaves the inferpod.
preview how a submission will move through review
submitted
ERPNextBusiness · size m, 4 GB · 18 actionssent today at 14:02 · erpnext 15.4.0in review
ERPNextBusiness · size m, 4 GB · 18 actionsapi-only test passed againlisted
ERPNextBusiness · size m, 4 GB · 18 actionsliveon every inferpod
questions.
- what can an inferapp be built with?
- Anything that builds into a container image and serves HTTP: Node.js, Python, Go, Ruby, PHP, Java. The inferpod only sees the web build, the manifest and the OpenAPI file.
- do i need a separate mobile app?
- No. An inferapp is one web build. It runs on the inferpod and opens in the browser of whatever device someone has, so there is nothing per device to build or list.
- my app needs more than 8 GB.
- Then it does not fit yet. l is the largest size in this draft. Tell us what it needs when you write in; the sizes are part of what is under review.
- can it keep running in the background?
- Only while it has requests. Work that has to happen on a schedule should be an action an agent can call, so it runs, finishes and lets the app sleep again.
- how do updates reach people?
- Today, an app you deploy with in4 builds again from its latest commit (in4 app build), or on every push once you add a webhook (in4 webhook). Coming with listing: you submit a new version, the owner of each inferpod approves the update, and migrations run then, not on wake, so waking stays fast.
- is this spec final?
- The in4 command line is shipped. The manifest, the test runner, the submit step and the review are a draft for discussion, and everything marked coming is not there yet. If something here would not work for your app, that is exactly what we want to hear.