Security
What protects your machine and your credentials, what stays private to you, and what Hoshi does not promise yet.
Your machine holds real work: repositories, credentials, documents. This page is what protects it, in plain terms.
Your machine is yours alone
Machines are never shared. Every request to a machine is checked on that machine, and it verifies that the caller is the owner — so an account that authenticates perfectly well elsewhere is still refused by a machine that does not belong to it. Another person cannot reach your machine even knowing its address.
Your agent has no public entrance
The agent running on your machine is not reachable from the internet on its own. Everything — every message, file read and tool call — arrives through the authenticated front door of your machine, which establishes who you are first.
Credentials stay on your machine
Git tokens for private repositories, API keys for connectors and provider keys are held in a vault on your own machine rather than centrally. Values are write-only from the outside: you can set a secret and confirm that it is set, but you cannot read it back, and neither can anyone else. Provider keys are resolved on the machine and are never sent to your browser or included in what the model sees.
What happens to your data
- Your files stay on your machine between sessions, and go with it when it is deleted.
- Deleting a machine destroys its contents — every checkout on it, wiped. That action is deliberately hard to trigger by accident.
- Stopping, starting or updating a machine never loses data.
What we do not promise yet
Hoshi is in open alpha, and it is worth being direct about the limits.
- We hold no security certifications — no SOC 2, no ISO 27001, no HIPAA. What is described above is how the system works, not an audit anyone has performed.
- There is no uptime guarantee and no service level agreement; the Terms page says so too.
- Machines are restarted for updates, and features change week to week.
Use that to judge what is appropriate to put on a machine today. If you have a specific security requirement, contact us rather than guessing — and if you find something that looks wrong, contact us directly rather than posting it publicly.