TALVINDER
  • Frameworks
  • Build Logs
  • Field Notes
  • Bets
  • Products
    • Elsewhere
    • Ostronaut
    • Pragmatic Leaders
  • About
    • About Me
    • Library
    • Contact
  • Subscribe

Elsewhere — Your work doesn’t need your laptop

Start heavy builds, tests, and coding-agent work here. Elsewhere decides where they should run and keeps them moving when your laptop cannot.
Author

B. Talvinder

Elsewhere
How it works Trust GitHub
Public alpha

Your work doesn't need your laptop.

Start it here. Let it run anywhere. Close the lid.

Elsewhere decides whether builds, tests, and coding-agent work should run on the machine in front of you or move to available cloud compute.

View on GitHub ↗ Install Elsewhere ↓
A real handoff
elsewhere
$ elsewhere route \
  --workload test \
  --source-path . \
  --image node:22 \
  --command "npm test" \
  --execute

Local capacity is tight.
Mumbai has no capacity.
→ Moving this run to Singapore.

Job started · source protected
cleanup enabled

✓ You can close this laptop.

Location, cost boundary, source movement, and cleanup stay visible.

START HERE→RUN ANYWHERE→CLOSE THE LID→
01 / THE LIMIT

Your machine is a starting point.
Not a limit.

Codex starts workers. Claude runs tests. A build spikes. Suddenly your expensive laptop is swapping memory and you are babysitting a progress bar.

Cloud compute already exists. The missing piece is one decision layer that knows when work belongs here, when it belongs elsewhere, and how to move it without turning you into a cloud operator.

02 / THE HANDOFF

One command. Three decisions.

1

Can it run here?

Elsewhere reads current memory pressure and shared reservations before admitting more work.

2

Where should it go?

It chooses from the providers and credits you already have, with regional and provider fallback.

3

What crosses the line?

Source exclusions, short-lived transport, job state, and cleanup remain explicit and inspectable.

03 / PROVEN, NOT PROMISED

The first run already left home.

Elsewhere packaged an uncommitted folder, excluded its .env, moved one manifest-tracked file through a short-lived Azure Blob URL, retried a capacity-constrained Fly region, and started the workload in Singapore.

The saved job contained no source credential. Cleanup left zero source blobs and zero Fly Machines.

LIVE ROUTE 001VERIFIED
LOCALBOMSIN
Secret files
Excluded
Source URL
Redacted
Compute left
0
Artifacts left
0
04 / TRUST IS THE PRODUCT

No mystery cloud.
No weekend bill.

01

Dry by default. A route is only a plan until you explicitly execute it.

02

Bring your own cloud. Fly and Azure today. OpenSandbox, ZopCloud, GCP, and others can use the same contract.

03

Source boundaries are visible. Common secrets, keys, Git history, dependencies, and generated output are excluded.

04

Cleanup is part of done. Cancel, expiry, and artifact deletion are lifecycle operations, not documentation chores.

05 / TRY IT

Give your agents somewhere else to work.

Elsewhere is open source under Apache 2.0. Bring your own infrastructure, inspect every decision, and help shape the provider contract.

Install from GitHub uv tool install git+https://github.com/talvinder/elsewhere.git Read the dogfood guide →
THE ACCEPTANCE TEST
CTFL.

Close the f**king lid.

Not just a line. If a workflow still depends on the originating device, Elsewhere is not done.

Start it. Send it. Close the lid. ↗

© 2026 B. Talvinder

Building Elsewhere · Zopdev · Pragmatic Leaders · Side B

GitHub · LinkedIn · X


B. Talvinder is a serial founder (ex-OYO, YC, 500 Startups) who has built four companies across four different technology eras in eighteen years. He writes about AI, infrastructure, and the India tech ecosystem at talvinder.com.

See a gap in this argument? Say so below.

Enjoyed this?

Get frameworks, build logs, and field notes in your inbox.

No spam. Unsubscribe anytime.