How it works
How it works
How work would move from a business to idle devices and back. Nothing here is running yet.
The design
The path of a job
Six stages. Four are designs we intend to build; two still have open questions.
Stage 1: Submit
PlannedA business would describe a batch job: the software, the inputs, the hardware it needs, and the window it must finish in.
Stage 2: Split
PlannedThe job would be cut into many small, restartable tasks, each short enough that losing one device costs little.
Stage 3: Match
PlannedEach task would go to a device that meets its needs and is available under its owner's limits, in any countries the buyer has allowed.
Stage 4: Run in sandbox
PlannedThe task would run in an isolated virtual machine with no access to the owner's files or home network, and pause the moment the owner needs the device.
Stage 5: Verify
ConceptualResults would be checked by replication, known-answer tasks or re-execution before anything is accepted. Some workloads have no cheap check.
Stage 6: Settle
ConceptualThe buyer would pay in ordinary currency for verified work, and the contributor would be paid from that, less a platform fee. Terms are not set.
Two sides
Two views of the same network
If you contribute a device
- 1You would install Jetpack on a supported device and set the hours, power and temperature limits you are comfortable with.
- 2Jetpack would benchmark the device, so it is only offered work it can actually do.
- 3In the hours you allowed, while you are not using it, the device would take small tasks in a sandbox.
- 4You would see what ran, the electricity it used, and what it earned after costs.
- 5Payouts would be in ordinary currency. You could stop or uninstall at any time.
If you bring a workload
- 1Describe the workload, the hardware it needs, the data involved and when it must finish.
- 2We would assess whether it fits, and say so plainly when it does not.
- 3If it fits, a small pilot on non-sensitive data, with results you can check yourself.
- 4Pricing per verified unit of work, agreed before anything runs.
- 5Results delivered as tasks are verified, with job-level progress you can follow.
Failure is normal
When things go wrong
Home devices are unreliable by nature, so the design treats failure as the normal case.
A device disconnects
Its task would return to the queue after a missed heartbeat and run on another device, resuming from a checkpoint where the task has one.
The design and its limitsA result is wrong
It would fail verification, go unpaid, and count against that device's reputation. The task would be run again elsewhere.
The design and its limitsThe owner comes back
Jetpack would pause the task immediately. The owner's use always wins, and the task would be rescheduled.
The design and its limitsA job misses its window
Slow tasks near a deadline would be duplicated and the first verified result kept. Until pilots measure real behaviour, there are no completion-time guarantees.
The design and its limits
Questions
Frequently asked
Is it running?
Is this crypto?
What could my device earn?
Will it slow my computer?
What kinds of jobs would run?
Is my data safe as a buyer?
When does the beta start?
Which side are you on?
You have a device
Join the early-access list and tell us what you would contribute.