Security
Security at HelmSwarm
HelmSwarm protects accounts with TOTP two-factor authentication and login lockout, isolates each organization's devices and data, encrypts stored secrets, records sensitive actions in an audit log, and serves the panel behind Cloudflare. We list the controls that exist — and say plainly what we don't have, such as certifications.
Accounts and access
Two-factor authentication
Turn on TOTP 2FA with any authenticator app. Sign-in then needs both your password and a current code.
Login protection
Passwords are stored as bcrypt hashes. Repeated failed sign-ins lock the account temporarily to slow down guessing.
Roles and sessions
Role-based permissions decide who can view, control or automate devices. You can see active sessions and sign them out.
Isolation and data protection
Organization isolation
Devices, scenarios, runs and agent tokens belong to one organization. Requests are checked on the server against your organization, not just hidden in the interface.
Encrypted secrets vault
Credentials used in scenarios are encrypted at rest and referenced by name, so they don't appear in steps or exports.
Audit log
Sensitive actions — sign-ins, scenario runs, administrative changes — are written to an append-only, hash-chained audit log.
Connections and infrastructure
- Encrypted in transitThe panel is served over HTTPS behind Cloudflare. Agents connect with an encrypted WebSocket.
- Outbound-only agentThe Mac agent for your own iPhones dials out with a revocable connect token. No inbound ports or VPN on your network.
- Locked-down staff consoleHelmSwarm's internal backoffice is separate from the customer panel and requires a staff account, mandatory 2FA and Cloudflare Access.
- BackupsThe service database is backed up regularly, including before every deployment.
What we don't claim
HelmSwarm doesn't currently hold SOC 2, ISO 27001 or similar certifications, and there's no published uptime SLA. We won't show badges we haven't earned. If your review needs a questionnaire answered, send it to us and we'll answer it honestly.
Using HelmSwarm responsibly is part of security, too: our Acceptable Use Policy forbids using the service to get around other platforms' security or anti-fraud measures.
Security questions
Is HelmSwarm SOC 2 or ISO 27001 certified?
No. HelmSwarm doesn't hold security certifications today, and we don't claim any. This page lists the controls that are in place so you can assess them yourself.
Does HelmSwarm offer an uptime SLA?
There is no published uptime SLA. Every package includes Ultra Support 24/7; if you need contractual terms, ask us before you order.
Can HelmSwarm staff see my devices?
Access to customer workspaces is limited to HelmSwarm's internal staff console, which requires a staff account, two-factor authentication and Cloudflare Access, and staff actions are recorded in the audit log. Staff use it to operate the service and to help when you ask for support.
How do I report a security issue?
Email hello@helmswarm.com with “Security report” in the subject. Please give us a reasonable chance to fix the issue before disclosing it.
Where is the panel hosted?
The HelmSwarm panel runs on servers operated for HelmSwarm, behind Cloudflare. Rented iPhones are hosted by HelmSwarm. Ask us if you need specifics for your security review.
Questions from your security review?
Send them over. We'll answer with what's actually in place.