Deploy anything. Pay almost nothing.
A coordinator, a fleet of idle laptops, and a WebSocket tunnel. Run batch jobs or host web apps on consumer hardware, no public IPs required.
How It Works
From code to production
in seconds.
Submit a job or app
Send files + a shell command via the web form or `passive submit`, or push a Docker image with `passive deploy`.
Coordinator splits the work
Batch jobs are chunked by file or by line; hosted apps are pinned to workers. The scheduler dispatches to idle nodes over a single WebSocket.
Sandboxed Docker on real devices
Each chunk or app runs in an ephemeral, resource-capped Docker container on someone's idle laptop or VPS.
Results stream back
Batch jobs aggregate to a single output. Hosted apps get a `<name>.passivedev.com` URL routed back through the coordinator.
Pricing
Same performance.
Fraction of the cost.
Real per-workload costs measured on the demo fleet, against the AWS service you’d normally reach for.
cheaper on the demo workloads below
| Feature | Cloud | Passive |
|---|---|---|
| Batch jobs (shell, python) | ✓ | ✓ |
| Hosted web apps | ✓ | ✓ |
| Sandboxed Docker per chunk | ✓ | ✓ |
| Workers behind NAT (no public IP) | — | ✓ |
| Auto-requeue on worker death | Manual | Built-in |
| Per execution-second pricing | — | Demo only |
For Developers
Deploy anything.
One command.
$ passive submit --type shell \
--command "wc -w" \
--input ./tweets/ --split-by file \
--timeout 60
Job submitted: 7a2f8c1b9e4d
$ passive status 7a2f8c1b9e4d --watch
[7a2f8c1b9e4d] status=running completed=12/47
[7a2f8c1b9e4d] status=running completed=38/47
[7a2f8c1b9e4d] status=completed completed=47/47
$ passive results 7a2f8c1b9e4d -o ./out/
Output written to out/7a2f8c1b9e4d.txtBatch jobs
Shell or Python commands chunked across idle workers. Submit, watch, download.
Hosted web apps
Push a Docker image, get a routed <name>.passivedev.com URL backed by 1+ workers.
Failure recovery
Workers die; in-flight units automatically requeue and finish on another worker.
Live observability
Watch chunks land per-worker in real time on the public admin dashboard.
For Device Owners
Your laptop earns credits while you sleep.
Install the desktop app
Tauri-built native app for macOS, Windows, and Linux. Manages a sandboxed worker subprocess; no manual setup.
Set your sharing rules
Cap CPU/RAM/disk, set a 7×24 availability schedule, throttle on battery or metered networks.
Earn credits while idle
Workers earn credits per execution-second. The app shows live status, recent jobs, and an estimated USD value at the demo rate.
Earnings estimator
Demo-rate math. USD payouts launch at GA.
Monthly credits
648,000
≈ $0.65 at demo rate
Estimate assumes 1 credit/sec while running. Real rate varies with job mix and capability score.
Security & Trust
Trust by design,
not by promise.
Docker sandbox per chunk
Each work unit runs in an ephemeral, resource-capped container. No sidecar state. Demo fleet runs with sandbox always on.
TLS via Caddy
Every hop into the coordinator is HTTPS / WSS. Worker tokens are short-lived JWTs; user sessions live in httpOnly cookies.
Heartbeat-driven recovery
Five coordinator loops watch dispatch, ping, heartbeat, timeout, and per-app health. Silent workers get reaped and their units requeued.
Workers behind NAT
Workers dial out to the coordinator over a single WebSocket. No inbound ports, no public IPs, no exposed services on the host.
Security Roadmap
See it run, then sign up.
The 5 reviewer demos are open and unauthenticated. Sign up after you’ve seen the system fan a job out across real workers.
No credit card. Payouts launch with GA.