Add your phone as a compute node

Launching soonYou opt in · charging on Wi-FiStop anytime

Turn your phone into compute

While your phone is charging on Wi-Fi and you’re not using it, it can quietly take on small AI jobs for the network and earn for the work it finishes — measured per job, never promised. It runs only when you allow it and only when the phone itself reports it’s charging, cool, idle, and on unmetered Wi-Fi. Phone earnings are small and honest — you’re lending spare, plugged-in time, not buying a mining rig.

Add your phone

See what it could earn →

You opt in

What runs on your phone, and when

Your phone never just starts working. It takes on a job only when it reports every one of these conditions met — and it stops the instant any of them changes. You set the limits; the phone enforces them.

Only while it’s charging

The node runs only when the phone reports it’s plugged in and charging — never off the battery you need for the day.

Only when you’re not using it

It waits until the phone is idle. Pick it up and the work steps aside — your phone stays yours first.

Only on unmetered Wi-Fi

Never on cellular or a metered connection. It won’t spend your data plan — only Wi-Fi the phone reports as unmetered.

Only when it’s cool enough

The phone reports its own thermal headroom. No headroom, no work — so it stays cool and the battery stays healthy.

Only with the screen off

Work runs in the background with the screen off. It doesn’t compete with anything you’re actually doing.

Low battery → it pauses

If the battery drops below your threshold — or anything above changes — it pauses on its own. You can stop it any time, too.

What your phone can run

The small end of the work — nothing heavy

A phone isn’t a graphics card, so it runs the small, quick jobs it’s genuinely good at — the kinds below. It’s paid for the work it actually finishes, measured per job.

Small text models
Text embeddings
Search reranking
Text classification
Speech-to-text
Small, device-gated images
Small isolated compute

It will not run arbitrary sandboxed code. Phones are never routed the general-purpose sandbox, code execution, benchmarking, training, or any confidential-tier job — only the small kinds above. That’s a routing rule the network enforces, not a promise this page makes.

Get the app

Add your phone

The phone app isn't out yet. The store buttons light up right here the moment it launches — we won't fake a link before then.

App Store

iPhone & iPad · iOS

Coming soon

Google Play

Phones & tablets · Android

Coming soon

One account across all of Zatabase — the same login and the same balance you build and earn with everywhere else. Nothing new to sign up for.

Phone earnings estimator

See what your phone could earn

Pick your kind of phone and how many hours a day it charges on Wi-Fi. We’ll show an honest range — phone earnings are small, and these are launch estimates, not a promise.

1 · What kind of phone?

Just a starting point — the installed app reads your phone’s real capability and earns on that, not on this pick.

2 · Hours a day it charges on Wi-Fi:8h

Most phones charge overnight — that’s the window a phone earns in. Only counts hours it’s actually plugged in, cool, idle, and on Wi-Fi.

Per day$—estimated range

Per month$—estimated range

The high end is your phone busy the whole charging window; the low end is launch, when the network routes little work to any one phone. Real earnings land between, and grow as more work routes to you.

Launch estimate · not measured

There’s no phone benchmark yet, so the throughput behind these numbers is an approximate device-class figure, not a measurement, and it leans low on purpose. Phones are paid for verified completed work, measured per job — never promised. Treat every figure as a conservative ballpark that we’ll replace with real, measured rates once phones are running.

Add your phone

How payouts work

Live

The network your phone joins

This is the real computing power everyday machines are already lending the network — the same network your phone helps out during its charging window.

Network capacity

Computing power available, last 24 hours

Graphics memory (GB) that everyday computers have made available to the network, grouped by the kind of machine. Live, from real machines people already own and put to work — not billion-dollar data-center racks.

Live network — collecting history…

The trend chart fills in as machines join and the network records each hour. Check back soon to watch it grow.

Figures come straight from connected machines and update through the day.

Is it safe?

Straight answers before you switch it on

A fair question before you let a network use your phone — and it deserves a real answer. The app runs only under the conditions you allow, each job it takes on stays sealed off from the rest of your phone, and you can stop it any time. Here’s exactly what runs, and how builders’ work is kept private.

For people running jobs

An app you install — and every job runs walled off from your computer

Here's the part that matters: the work the network sends you runs inside its own locked-down micro-VM — a throwaway virtual machine with its own kernel — not in the app's own process and not under your account. It can't see your files, your logins, or anything else on your computer, and when the job finishes its VM is gone. Below is exactly what the app does, what it doesn't ask for, and how to stop it.

Every job runs in its own locked-down micro-VMThe work the network sends you doesn't run in the app's own process or under your account — each job runs inside its own throwaway micro-VM, a separate virtual machine with its own kernel, walled off from your files, your logins, and everything else on your machine. When the job finishes, its VM is gone.
A normal install, then it runs in the backgroundYou install it like any other app. Because each job runs in its own micro-VM, setting up that sandbox may ask for permission once — the same as installing anything that adds a system component. After that the app just supervises the work quietly in the background.
You choose what it takes onYou pick which graphics card it uses, which kinds of work it advertises, and whether it serves paid public jobs, only your own jobs, or both. It never quietly opts you into more than that.
You never hold the sensitive end of a jobOpen work is public and best-effort by design. Trusted jobs are split into slices, and the two that matter — the one that reads the customer's input and the one that produces their output — are reserved for vetted machines, so an unvetted machine only ever gets a middle slice. Private work never routes here at all. You're not made the custodian of someone else's secrets.
Both higher tiers are earnableGet vetted and Trusted work routes to you as well — there is no hardware requirement for that, a vetted operator on a consumer card counts. Private work is gated on the hardware rather than on who owns it: a machine with a confidential-computing graphics card behind a matching processor qualifies whether it sits in a data center or your spare room.
Stop it whenever you wantIt's a background service, so it keeps running across logout and reboot until you say otherwise. Stop it and the work stops; uninstall it and it's gone. No notice period, no penalty.

The plain version: the app runs like any background program, but the jobs it takes on never touch your session — each one runs isolated in its own micro-VM and is thrown away when it's done. It works with most gaming PCs and Macs.

For people building with the API

Three tiers. Pick one per job.

The tier decides which machines see which part of your job, and what you can check afterwards. Open runs whole on one machine; Trusted and Private split the work and place the sensitive slices deliberately. One field on the request moves a job between them.

Open

Default · best-effort

Anonymous machines, any hardware, cheapest rates. Your job runs whole on one of them, so whoever runs that machine can read your prompt and your output. This tier is not private and we won't dress it up as private — it's the right call for public or synthetic data, batch evals, benchmarking, and prompts you'd be comfortable posting in public.

Trusted

Vetted where it counts

A Trusted job is split into slices and the machines mix. The two slices that matter go to vetted operators — the first one, which sees your raw input, and the last one, which produces your output — while the middle is filled with cheap anonymous capacity.That mix is exactly why Trusted costs less than Private. The default is a solid majority vetted, and you can turn the dial up to every slice if you'd rather pay for it.

Straight about the rest: a contributor holding one middle slice sees intermediate math, not your prompt or your result, and getting anything useful out of it takes a deliberate attack — a small risk we price in, not a guarantee we're selling you. Vetting is the bar, not hardware: our own machines, bare metal we rent and run our own image on, RunPod, and any operator we've vetted and hold under contract — a consumer card qualifies.

Private

Encrypted & signed

Confidential in the literal sense. Your job runs inside a confidential VM on a GPU in confidential-computing mode:system memory is encrypted, the GPU's own memory is encrypted, and the traffic across the link between them is encrypted under a session the hardware negotiates.The operator of that machine — us included — cannot read your prompt, your weights, or your output.

Then the hardware proves it. The launch is measured and the GPU signs an attestation of the work it did, checked before a single weight or prompt is shipped — so the result is attributable, tamper-evident, and yours to verify rather than take on faith. This is also the only tier that can carry a whole payload.

The short version: Open is public and says so. Trusted keeps the sensitive ends of a job in vetted hands and buys the middle cheap. Private encrypts the whole thing away from the host and hands you a signature to check.