Public alpha · Remote execution for developer workloads
Run builds, tests, and AI agents on remote compute.
Elsewhere checks your laptop’s capacity, shows a plan to run the command on Fly or Azure, and waits for your approval. When the remote job finishes, Elsewhere verifies the result, copies it back into this project, and deletes the temporary cloud resources.
The job runs remotely only after you approve the plan.
37-SECOND PRODUCT DEMO
See a build run remotely and return its result.
One command. One plan.
One approval. One verified result.
CHECK LOCAL CAPACITYRUN REMOTELY AFTER APPROVALRETURN THE VERIFIED RESULT
LOCAL TEST
Install Elsewhere and run a job locally.
This first command runs only on your laptop. It uploads no files and creates no cloud resources.
$ uv tool install git+https://github.com/talvinder/elsewhere.gitEXACTLY WHAT HAPPENS
Elsewhere performs these four steps.
- 1
Check local capacity
Elsewhere reads current memory pressure and active reservations on this laptop.
- 2
Show the remote execution plan
You see the provider, region, project files, memory, runtime, and estimated cost before anything is uploaded.
- 3
Wait for your approval
The plan makes no changes. Remote execution starts only when you add --execute.
- 4
Return the result and clean up
Elsewhere verifies the returned files, copies them into this project, and confirms that temporary compute and uploaded source files are deleted.
A remote job continues if the laptop sleeps. Use the same laptop to check status, download results, change provider settings, and confirm cleanup.