the data center,
on your desk.

a home for your apps: your own pod, or one from the fleet.

it happened to the computer first.

  1. mainframe, then minicomputer, then the pc on your desk
  2. data center, then public cloud, then the inferpod on your desk

same capability. closer to you. under your control.

one box. a home for your apps.

  1. private

    your data stays on the pod. it never has to leave.

  2. close

    in your city, not a distant region.

  3. cheap

    nothing bills while it sleeps.

apps on a pod are agentic-ready.

  1. install one

    find an app in the catalog and put it on a pod — yours, or one from the fleet.

  2. work it yourself

    it opens in any browser, built for hands: click, type, done.

  3. or hand it to your agent

    its actions are open to agents too, so it can run the app for you. when nobody needs it, it sleeps.

awake 3 h 50 m. asleep the rest.

an example day on shop-01, an inferpod running erpnext. it wakes on the next request and nothing bills while it sleeps.

An example day: awake 08:40 to 10:10, 12:30 to 13:50 and 18:00 to 19:00, 3 hours 50 minutes in all. Asleep the rest.
example day, one unit per hour

a home for your agent and your apps.

  • your personal agent

    an agent that works for you, on an inferpod you control.

    next
  • the app you just found

    apps from the catalog at inferapps.com, one step away. erpnext, imaarat and memos run today.

    running
  • your own apps

    build an app for inferpods and list it in the catalog. office listings, a small example app, shows how.

    example

three homes for your apps.

an inferpod next to a cloud account and a rented server
cloud accountrented serverinferpod
who owns itthe providerthe hosting companyyou, or a person in the fleet
your datain their data centerin their rackon the pod
who runs ityou, in their consoleyou, on the serveryour agent
when idledepends on your setupkeeps runningapps sleep until the next request

where we are today.

works today
your agent deploys, sizes and runs apps from the catalog: erpnext, imaarat and memos. sleep and wake work.
next
your agent builds new apps from scratch, and your personal agent moves onto your inferpod.

01 rent

rent pods from the fleet.

the fleet is inferpods owned and run by individuals. put your apps on one nearby, or on any pod, anywhere.

join the waitlist to rent
  • nearby

    a pod near you.

  • anywhere

    any pod in the fleet.

billed per awake minute

1 min
each wake-up bills at least a minute.
5 min
a woken app stays up at least five minutes, so it doesn’t flap.
asleep
nothing bills while it sleeps.

02 buy

buy a pod of your own.

an inferpod for your desk, in five sizes. no prices yet: buying is in early access, and joining the waitlist places no order.

join the waitlist to buy
  • 8 GB, 4 slots
  • 12 GB, 6 slots
  • 16 GB, 8 slots
  • 24 GB, 12 slots
  • 32 GB, 16 slots
  • 2 GB app, one slot
  • 4 GB app, 2 slots
  • 8 GB app, 4 slots
each square is a 2 GB slot. an app takes 2, 4 or 8 GB: one, two or four slots.

03 contribute

contribute a pod to the fleet.

any linux machine that stays on can be an inferpod. your email is your account: two commands and one email, no sign-up and no password.

machine
64-bit intel or amd (x86_64), linux. not arm or apple silicon.
room
2 GB of memory and 20 GB of free disk, at least.
network
always on, wired if you can. a home connection behind a router is fine: nothing needs opening.
what runs on your machine

one docker container, inferapps-node. it joins the fleet and runs stateless copies of other people’s apps, never their databases or files. it runs privileged, which is root on the machine: use a machine you can give to it. it updates itself at night.

earnings and stopping

your pod earns credits for the time it is up and taking work; they go to your account, which is your email. the confirm page opens your pods at inferapps.com straight away, and the machine itself is signed in as you. no money rates yet: they will be announced.

to stop, run in4 node leave <pod> on the machine: it leaves within a day without breaking anyone’s app. sudo docker rm -f inferapps-node stops it at once.

  1. install in4 on the machine

    on the linux machine (x86_64) you want to contribute, in a terminal:

    wget -qO- https://inferapps.com/install.sh | sh
    doesn’t work?

    no wget there (fedora or rhel minimal)? this one tries wget, then curl, then python3:

    (wget -qO- https://inferapps.com/install.sh || curl -fsSL https://inferapps.com/install.sh || python3 -c "import urllib.request as u;print(u.urlopen('https://inferapps.com/install.sh').read().decode())") | sh
  2. run one command with your email

    it only fills in the command below: this page sends it nowhere.

    sudo in4 node contribute --here --email you@example.com

    it checks the machine, installs docker if it is missing, asks which city it is in, and emails you a link.

  3. open the email, press join

    the link opens a page here: read the agreement, press the button, and the machine joins as your inferpod. that email is now your account: no sign-up, no password. the link works for 30 minutes.

rent, buy or contribute.

tell us which, and we’ll write to you.

i’d like to

or write to hello@inferapps.com

how we keep your email: privacy. the terms.