Provider network · Not open yet
Turn your machine into an AgentOS compute node
AgentOS runs its AI on nodes — machines that answer requests. Today that is our own node; next, it can be yours. Owners of a node receive a 50% share of what their node serves.
This is not live yet — and we won't pretend otherwise
The node software and the earnings ledger are still being built. There is no download link on this page because there is nothing honest to link to yet. Register your interest below and we'll come back to you when node onboarding opens, with the exact requirements and payout terms in writing.
What it means
Your machine answers the requests
A node is a machine that runs the AI model and answers requests routed to it. Nothing about your own files changes — a node serves other people's requests through AgentOS; it is compute you lend, not data you hand over.
Your hardware does the work
The model would run on your machine and produce the answer. That is not happening yet: AgentOS currently serves one live model, qwen2.5:14b, on its own node, and the node design keeps qwen2.5:7b and qwen2.5:14b loaded so the router can pick either.
The broker decides what goes where
A central broker holds the model registry and the node credentials, classifies each request and routes it. Your node receives work through that broker — never straight off the public internet.
A node belongs to one account
Each node carries its own credential, separate from your personal sign-in, and can be revoked at any time from your account.
How it will work
Install, sign in, start serving
Three steps, one terminal. This is the flow the node software is being built around.
Install the agentos-node CLI
A small command-line program you install on the machine you want to lend. It manages the local model runtime and the connection to AgentOS.
Sign in with your account
You sign in once from the CLI. The node's credential is stored in the macOS Keychain — never written to a plaintext config file.
Start serving
The node registers itself, sends a heartbeat so AgentOS knows it is online, and starts answering the requests the broker routes to it.
Written as the intended flow, not as a shipped feature: the CLI is not published for download and node earnings are not being credited yet. When onboarding opens, everyone on the interest list hears first.
What your machine needs
Requirements, as far as they are settled
Only what we can state from the current design. Anything not listed here is genuinely still open — we would rather leave a gap than invent a spec you buy hardware against.
A Mac
The node software targets macOS first, and stores its credential in the macOS Keychain. Support for other operating systems is not decided.
Two models resident (reference design)
Only qwen2.5:14b is live today. The reference design has the node keep qwen2.5:7b and qwen2.5:14b loaded at the same time so the router could send either kind of work to it without a swap — plan your machine for that, not for today's single model.
Memory for both
In the reference design qwen2.5:7b occupies roughly 5GB and qwen2.5:14b roughly 9GB while resident, so your machine needs headroom for both plus whatever else you run.
Disk for the model files
In that same reference design the two model files together come to about 13.5GB on disk, which can live on an external volume.
A machine that stays on
A node only earns while it is online and answering, so it suits a machine you leave running. The connection is outbound from your machine, so no inbound port needs opening.
Still being finalised
Minimum CPU and GPU specifications, uptime expectations, and how many nodes one account may run are not settled yet. They will be published before onboarding opens.
Security and privacy
What we can state, and what we can't
Your node is not exposed to the internet
By design it listens locally and serves through the AgentOS channel, with no public endpoint on your machine for anyone to find. Like everything else on this page, that describes software that is not open yet.
Two separate credentials
Your node authenticates to AgentOS with its own node credential. In the other direction, AgentOS signs each request to your node so the node can check the work really came from us — that verification path is still being built.
Zero-retention by design — verification still in progress
The design says a node keeps nothing from the requests it answers. We have not yet run a verification test that proves it end to end, so we describe it as how the system is designed rather than as something we have measured. When the test exists, we will say so here.
The credential is not left lying around
The node's credential lives in the macOS Keychain rather than a plaintext configuration file.
Register interest
Tell us about your machine
No download, no commitment. Leave your details and we'll write to you when node onboarding opens, with the requirements and terms in full.
Common questions
Questions about running a node
Can I sign up and start earning today?
No. The node software is not published for download and the earnings ledger is not live, so nothing would be credited if you did. This page exists so you can register interest and be told first when it opens.
How much would I earn?
We are not going to give you a number. The share is settled — 50% of what your node serves, measured by our broker — but the rate card and payout terms are still being finalised, and any figure we printed today would be a guess dressed up as a projection.
How is the amount measured — can a node inflate it?
The broker measures each answered request on its own side, and that is what counts. What a node reports about itself is shown for convenience only, so self-reported numbers cannot inflate a payout.
Do people's files end up on my machine?
A node receives the content of the request it has to answer, and the design is for it to keep nothing afterwards. We have not yet run a verification test proving that end to end, so we state it as design intent, not as a guarantee we have measured.
Is this the same as the AOS Node page?
They are two sides of the same idea, and neither is open yet. The AOS Node page is about registering a machine to run your own AI work; this page is about lending your machine to serve other people's requests for a share of what it serves. Today, both kinds of work are answered by AgentOS's own node in Singapore.
Want in when it opens?
Register your interest and we'll write to you with the requirements and terms before onboarding opens.