Locked down, specifically.

Every Consinna agent ships with the same posture. Here is what it is, in plain terms.

No public ports

After setup your server accepts no inbound connections at all. It dials out to Consinna's gate over an encrypted tunnel, and that is the only way in.

Every request is signed

Traffic reaches your agent only after Consinna login, and each request carries a signed assertion that expires in 120 seconds. The box holds only the public key. If the key is missing, it rejects everything.

Secrets never ride in setup scripts

Provisioning carries a single one-time token. Real credentials are fetched once over HTTPS and kept encrypted on the box. Server-side, tokens are encrypted with AES-256-GCM. Your model key is stored the same way and used only by your agent.

New devices need your approval

A sign-in from an unfamiliar browser waits until you approve it from your dashboard.

Backups are encrypted before they leave

Client-side encrypted, one repository per agent, keyed per agent. Restored into a fresh server on request.

Pinned releases, staged upgrades

We run a pinned OpenClaw release and upgrade on our schedule. Our on-box agent rolls itself back if a new build doesn't come up healthy.

Dedicated server, unprivileged process

One customer per server. OpenClaw runs as its own user; the firewall denies inbound by default; the cloud metadata endpoint is blocked.

Read-only diagnostics, human-approved fixes

OpenClaw's doctor runs read-only. A person approves any fix from our console; nothing is auto-applied to your configuration.

What we can see, and what we can't

Health, version and usage metrics are reported to us so we can page an engineer. Your conversations and files stay on your server. Our engineers reach it only through an authenticated support tunnel; there is no public SSH.

The checklist every agent passes before handoff

  • No inbound ports after lockdown
  • Support access only over the authenticated tunnel
  • Gateway bound to loopback behind the signed-request proxy
  • Firewall default-deny
  • OpenClaw running as an unprivileged user
  • Secrets encrypted at rest; none in setup scripts
  • Cloud metadata endpoint blocked
  • Pinned OpenClaw release recorded
  • Encrypted backup completed and verified
  • Device approval enabled
  • Health and channel probes reporting
  • Time sync and unattended OS security updates on

Same posture on every agent, at no extra cost.

We use one cookie to remember your theme and your choice here, and analytics only if you accept.