Local
Run Hermes directly on your own machine to understand how it works before adding more infrastructure.
- Fastest way to evaluate Hermes
- Good when a terminal-first workflow is fine
- Best first stop for new users
Start locally, use Docker for a cleaner runtime, move to VPS or cloud for always-on use, and keep an eye on managed hosting later.
Hermes can start small and grow with you. The right path depends on whether you want quick evaluation, repeatable runtime boundaries, or an always-on system.
Every option answers the same question: how close do you want Hermes to be to your real systems, and how much setup do you want to own?
Run Hermes directly on your own machine to understand how it works before adding more infrastructure.
Use Docker when you want a more repeatable runtime and a cleaner path from laptop to server.
Run Hermes on a VPS or cloud machine when you want it online continuously and close to the systems it should help with.
For people who want the Hermes outcome without running the infrastructure themselves.
If you want the Hermes outcome without owning the infrastructure surface yourself, hosted deployment is the direction to watch.
For now, the right move is to contact us if you want to be included when hosted access starts.
Contact for Hosted AccessStart Local. It is the fastest way to understand the mental model before you add runtime complexity.
Use Docker when you want a cleaner runtime boundary and a setup that travels more easily between environments.
Choose VPS or Cloud when you want Hermes close to your logs, services, automations, and recurring tasks.
Once you know which runtime shape fits you, use the official quickstart and repository to get Hermes running.
Answers to the deployment questions people usually search first: local setup, Docker, VPS, Open WebUI, and hosted access.
If you are deciding between options, optimize for the simplest setup that gets Hermes running in your environment.