# Vers

- [What is Vers?](https://docs.vers.sh/overview.md): Run remote Linux computers without maintaining local project state.
- [Installation](https://docs.vers.sh/installation.md): Install the Rust Vers CLI on macOS or Linux and configure an API key.
- [Get your API key](https://docs.vers.sh/get-api-key.md): Create an account and mint an API key from the Vers dashboard.
- [Quickstart](https://docs.vers.sh/quickstart.md): Run your first Vers workload and manage a detached computer.
- [Static Web App (GitHub Import)](https://docs.vers.sh/examples/static-web-app-github.md): Deploy a static web app to a Vers computer using GitHub import
- [Building pi extensions](https://docs.vers.sh/tutorials/pi-extensions.md): Give a coding agent a Vers computer and transparently route every bash call to it. ~80 lines of TypeScript.
- [Vers CLI reference](https://docs.vers.sh/cli-reference/overview.md): The complete command, configuration, output, and exit contract for the pre-launch Rust CLI.
- [Essays](https://docs.vers.sh/essays/overview.md): Long-form pieces on branchable compute, stateful infrastructure, and why the shape of the work changes when forking a live machine is cheap.
- [Why stateless compute ran out of runway for agents](https://docs.vers.sh/essays/stateless-compute-ran-out.md): Stateless compute was the right answer for request/response. It is the wrong answer for agents. Context is not a message array — it's everything the worker has built up, and statelessness throws all of it away.
- [The cost of rebuilding state](https://docs.vers.sh/essays/cost-of-rebuilding-state.md): Most engineering time is not spent doing work. It is spent re-creating the conditions under which work can be done. Once you see the pattern, you cannot unsee it.
- [Content-addressable everything](https://docs.vers.sh/essays/content-addressable-everything.md): Git's quiet revolution was that it made code identity a function of content, not location. Apply the same idea to running machines and three decades of problems dissolve at once.
- [Time-travel debugging, productionized](https://docs.vers.sh/essays/time-travel-debugging.md): Most bugs are hard because by the time you notice them, the state that produced them is gone. Make every commit a restoration point and branches a way to explore alternate pasts, and debugging stops looking like archaeology.
- [A short history of fork()](https://docs.vers.sh/essays/short-history-of-fork.md): fork() is fifty-five years old. It's the primitive that made Unix generative, the one every serious system still borrows from, and the one whose logical conclusion is to branch whole running machines.
- [Every infrastructure primitive is secretly a way to avoid paying a cost](https://docs.vers.sh/essays/every-primitive-avoids-a-cost.md): Indexes, caches, CDNs, fork(), git, containers — every durable primitive you can name started as someone's answer to a recurring cost. The frame is useful because it predicts where the next primitives are coming from.
- [Overview](https://docs.vers.sh/shell-auth/overview.md)
- [Initiate](https://docs.vers.sh/shell-auth/initiate.md)
- [Verify key](https://docs.vers.sh/shell-auth/verify-key.md)
- [Verify public key](https://docs.vers.sh/shell-auth/verify-public-key.md)
- [Api keys](https://docs.vers.sh/shell-auth/api-keys.md)

## Optional

- [GitHub](https://github.com/hdresearch)
- [Support](mailto:support@vers.sh)