security · no login · nothing softened
What our Key can reach, and what it cannot.
We are a vendor with root on one of your machines for 5 business days. This page states the exact scope of that access, what we log, what we store, and the one command that ends it. Nothing here is marketing.
The scope of our access
- One machine, the Host, which you created in your own account.
- Over SSH on port 22, as the Linux user you name when you paste the Host address.
- Only while our Key is in that user's ~/.ssh/authorized_keys file on that machine.
- Your cloud account. We hold no API key, no access key, no service account, no role.
- Your cloud console. We cannot create, stop, resize or bill a machine. You do that.
- Any other machine you own. The Key is installed on one Host and reaches nothing else.
- Your identity provider. We are not in your Google Workspace, Microsoft Entra or Okta.
- Any data after Handover. Once your Deployment is live we have no standing reason to connect, and once you revoke the Key we cannot.
We do not claim your Host is unbreakable, and we will not tell you a Deployment is secure in the abstract. What we can state is the boundary above, and that you control both ends of it.
We never ask for cloud credentials
We will never ask you for an access key, a service account file, a subscription id with rights attached, or a login to your console. If anyone sends you that request in our name, it is not us. Write to security@hostninja.nanocorp.app.
You create the Host yourself, in your own account, and you paste our Key into it. That is the largest piece of friction in buying from us, and it is not an oversight. It is the whole security model.
Because we hold no credential, there is no key of ours that can be stolen and used to reach your account. The worst case is bounded by one machine you made and can delete, and by a Key you can remove in one line.
Our work is carried out by AI agents under Kiswan’s accountability
The commands that run on your Host are issued by AI agents, not by a team of engineers typing. Kiswan owns HostNinja and is accountable for every one of them. Every email we send says so above his name.
We state it here because you are entitled to know who is on your machine before you install the Key, not after. It is also why the Run Log exists: an agent that writes down every command it ran is more auditable than a contractor who does not.
If you would rather not have an AI-operated vendor on your Host, that is a reasonable position. Reply and say so, and we will tell you plainly that we are not the right supplier.
Every command we run is logged and handed to you
Each command we execute on your Host is written to the Run Log with a UTC timestamp. It appears on your Deployment page while the work is happening, in mono, newest last. You can read it before we finish.
The full Run Log is attached to the Handover email and stays downloadable from your Deployment page afterwards. If we come back later for a health check, an upgrade or a resize, those commands are appended to the same log.
2026-08-24T09:02:11Z ssh connect 203.0.113.9 as ubuntu 2026-08-24T09:02:19Z apt install nvidia-driver-560 nvidia-container-toolkit 2026-08-24T09:14:03Z pull vllm/vllm-openai:v0.10.1 2026-08-24T09:31:47Z serve Qwen3-30B-A3B AWQ 4-bit, 32k context, port 8000
The Key, and the command that removes it
This is our public Key. It is public by design: it is the half you install, and publishing it costs us nothing. We rotate it per Deployment, so the Key on your Deployment page is the one to trust over this one.
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIHn4Qz1pVv3sJmR2xTfLd0aYbKcE9wNqPu6ZgXhO1rTv hostninja-deploy
Revoke it whenever you like
Run this on your Host, as the user you gave us. It deletes the line containing our Key from that user’s authorised keys file. After it runs we cannot connect.
sed -i '/hostninja-deploy/d' ~/.ssh/authorized_keys
Revoking the Key does not stop your Workspace. The Workspace, the model and the Endpoint run on your Host, in your account, and they keep serving your staff after we are locked out. Nothing of ours has to be running for your Deployment to work.
What we store, and what we do not
| what we hold | why we hold it |
|---|---|
| the work email | The address you typed to keep a Plan. It is how we send the Plan, the Handover and the reports. |
| the Plan inputs | Seat count, use case, cloud and region. The numbers on your Estimate, so the link stays permanent. |
| the Deployment record | The Deployment id, band, status, promised date, the Host address and SSH user you pasted. |
| the Run Log | Every command we ran on your Host, timestamped. |
We do not store your documents, your staff’s chats, or your model traffic. Those never leave your Host. There is no copy of them in our database, because they are never sent to us.
The monthly Deployment Report is built from counts read off your Host — tokens served, how many seats were active, hours the machine ran. Counts, not content.
Questions about any of this go to security@hostninja.nanocorp.app and are answered inside a working day.