What you can make with it
Images today, video as the grid grows. You send a job, the swarm does the work, and you get back a result checked piece by piece.
Images from words
Describe what you want, choose how many. The grid splits the batch across the swarm, renders every image, checks each one, and hands you back the set. You never see unchecked work.
Photos, 4× sharper
Upload a photo and get it back four times sharper. Big photos are cut into tiles, enhanced in parallel on different machines, and stitched back so cleanly you can't find the seams.
Video, when the grid grows
Designed into the protocol from day one: clips become pieces, and each piece gets the same checks as images. It is not running yet; video needs bigger cards than the grid has today, so it switches on as nodes join. Until then, this card says next, not now.
Send a job
Type what you want, or drop in a photo. That's the whole form.
The swarm gets to work
Your job becomes pieces. Idle GPUs pick them up and render, and each piece is checked as it lands.
Get the result
Verified pieces come back together as one finished result, ready to download.
Where this stands: Reshoot runs today in private early access, on the founder's own hardware. It opens as the network grows. Want in early? Request an invite.
Have a gaming PC? Join the swarm.
Most graphics cards sit idle most of the day. Reshoot gives yours real work: pieces of real jobs, run whole on your card, checked, and credited to you. Only work that passes the check ever counts.
Install one small app
It creates a key that is yours alone. When the network opens, joining is a key, not an application.
Flip the switch
You decide what your computer will and won't run, and when. Pause any time; it stops instantly.
Watch real numbers
Pieces rendered, pieces verified, your ratio of work given to work taken. All from your own machine, live.
Where this stands: the one-app client is being built right now, and early nodes join by invite while the network is small. Ask for one on the start page. One promise holds either way: we will never show you an earnings estimate we haven't measured. When you join, you see real numbers from your own machine, and nothing else.
Chunk
A job arrives: a render batch, a photo to enhance, and one day a video clip (designed in, not running yet). The coordinator splits it into pieces sized for one GPU. A piece always runs whole on one card. We never split a single inference pass across the internet; the physics says no, so we don't pretend.
Swarm
Nodes pull pieces they have consented to run. Connections are outbound only, so a node works behind any home router with no ports opened. A node that goes quiet loses its lease and the piece re-queues for someone else. Nothing waits on anyone.
Verify
Disguised known-answer pieces are slipped into the work, indistinguishable on the wire. Real pieces are spot-checked by a different machine re-running the same piece and comparing results perceptually. Caught work earns nothing, ever.
Reassemble, then receipt
Verified pieces blend back into one result, deterministically. Every passing piece gets an Ed25519-signed receipt, sealed daily into a hash-chained Merkle log. A standalone tool recomputes the whole log from public evidence: if it's not in the log, it didn't happen.
What runs today
Measured on the live grid, 10 June 2026. Updated by hand when the numbers change, not by hype.
Network size today: one coordinator, two nodes, one physical GPU. Small, real, and verifiable beats large and imagined.
- Chunking engine. Image batches and tiled upscales become independently verifiable pieces with deterministic seeds and overlap-aware reassembly.
- Pull-lease dispatch. Outbound-only long-polling, heartbeats, dead-man requeue. Works behind any NAT.
- Verification plane. Perceptual-hash canaries, cross-node duplicate checks, node trust tiers, escrowed verdicts: a receipt is minted once, at a terminal pass, never retracted.
- Receipt log. Signed piece receipts sealed into hash-chained epochs, plus a standalone verifier that recomputes every root independently.
For node operators
The three questions every GPU owner asks, answered the way we answer everything.
What a job can never do
Jobs are data, never code: pinned, signed runtime packs run an audited vocabulary of workflows, and a job cannot reach the internet from your machine, ever. The sandbox that enforces this for strangers' jobs ships with the public client; until it does, no stranger's piece touches anyone's hardware.
What your card needs
Today's jobs run on a 16 GB NVIDIA card; model weights take tens of gigabytes of disk; pieces upload as a few hundred kilobytes to a few megabytes. The client targets Windows first, headless Linux planned. The switch is yours, so it never competes with your game unless you let it.
Electricity, counted honestly
Your card draws real watts, and at some electricity prices this is a net loss. The client subtracts electricity from every number it shows you, and where the math says don't join, it will say don't join. Worth doing on hardware you already own; never a reason to buy a card.
Your photos, on the grid
A node can see the tiles it renders; that is physics, and we won't pretend otherwise. Today every node is the founder's own hardware. Before strangers' nodes render your photos, the consent and privacy story ships in the open, written before it is needed.
The rules we build by
Written down before launch, so you can hold us to them.
One piece, one GPU
All parallelism lives between pieces, never inside one. Anyone who claims to split a single inference pass across home internet connections is selling something the interconnect math does not allow.
Only verified work counts
Nothing is earned for capacity, uptime, signups, or recruiting. Delivered, verified pieces are the only unit that matters, and every one of them traces to a signed receipt in a public log.
No unmeasured numbers
The network is new. We do not estimate earnings we have not measured, and no number ships on any Reshoot surface before it is measured on real hardware. This page obeys that rule.
There is no token
No coin exists, none is for sale, and nothing on any Reshoot surface promises one. If a settlement design ever ships, it pays only against verified work receipts, and you will read it here first, in this register, with the same rules applied.
Honest about today
Right now Reshoot is a company-operated service implementing an open protocol: one coordinator, founder hardware. Every object is signed and content-addressed, so the exit from that is checkable, not rhetorical: anyone will be able to run a coordinator without asking us.