Haltless is built multi-tenant on a tamper-evident audit chain designed to produce SOC 2 evidence. PostgreSQL Row-Level Security pins every query to the current tenant, multi-factor authentication is built into the application and recommended for every user, and a HMAC-SHA256 audit log retained for seven years gives auditors a tamper-evident trail. We do not currently hold SOC 2 or ISO 27001 certifications, and we will not claim them on the site until an auditor has signed off.
Last updated: October 1, 2026
The edge agent sits inside your network and reads from PLCs and historians locally. Connections are outbound only: from the agent to the controllers, and from the agent to our cloud over TLS 1.3. No reverse tunnel, no inbound exposure of your OT network. Raw protocol frames are parsed locally; only normalised metrics ship to the cloud.
Haltless is not yet ISO 27001 certified. Our information security management system follows the controls defined in the standard, with documented risk assessments, access reviews, vendor due diligence, and change management. Certification status will appear here only after an external auditor has signed off.
Haltless is not yet SOC 2 Type II certified. We do operate against the Trust Services Criteria for security, availability, and confidentiality, with documented logging, alerting, and incident response procedures reviewed continuously and exercised through tabletop drills. The certification status will appear here only after an external auditor has signed off.
How the platform protects tenant data at rest and proves nothing has been tampered with.
Every audit log row carries a monotonic sequence number and an HMAC-SHA256 hash chained to the previous row. Mutations, deletions, and reordering all produce mismatches the system detects automatically. An append-only database trigger blocks deletes without an explicit retention flag. Your audit trail is cryptographically immutable.
Every tenant-scoped table carries a PostgreSQL row-level security policy that pins queries to the current tenant. Combined with transaction-scoped tenant context middleware and API-layer scoping, a tenant administrator physically cannot reach another tenant’s data. Isolation enforced from query to endpoint.
A signed Data Processing Addendum, lawful-basis tracking, and US data residency are available out of the box. You retain full ownership of Customer Data and can request export or deletion at any time. The full DPA, including the EU Standard Contractual Clauses, UK IDTA, and China Standard Contract, is published on the site.
Traffic between edge agents and our backend is protected with TLS 1.3 and per-tenant key material. Customer Personal Data at rest is encrypted with AES-256, MFA secrets are encrypted with a separate key, and Customer telemetry stays in the United States.
How users prove who they are, with or without your corporate identity provider.
12-character password minimum, 90-day rotation with reuse prevention, login throttling per IP and per user, and TOTP-based MFA with secrets encrypted at rest. Email verification is mandatory before first sign-in.
Tenant-level single sign-on over OpenID Connect with PKCE, against your own corporate identity provider, such as Okta, Microsoft Entra ID or Google Workspace. Users are created on their first sign-in, so access is managed in one place.
Centralized logging, anomaly detection, and continuous vulnerability scanning alert the founder directly, and every incident follows a documented response playbook. Haltless is one person today, so there is no round-the-clock security desk behind those alerts. We would rather say that here than have a security questionnaire find it.
How issued credentials are scoped, refreshed, and revoked at scale.
Access tokens are kept in memory only, never in localStorage. Refresh tokens live in HttpOnly cookies with SameSite=Lax. Sessions are revocable per device, and rotations are routine, not exceptional.
A single database write invalidates every issued token for a user or tenant. Triggered automatically on password change, MFA enrolment, or suspicious activity. No scattered session cleanup required.
DATA SOVEREIGNTY
Customer Data is stored in the United States. Cross-border transfers are covered by the EU Standard Contractual Clauses Module 2, the UK Information Commissioner's IDTA, the China Standard Contract for Cross-border Transfer of Personal Information, or the EU-US Data Privacy Framework, depending on the recipient. The current sub-processor list, with the actual processing region per provider, is set out in Annex III of the Data Processing Addendum.
Read the Data Processing AddendumVulnerability disclosure
Email security@haltless.io in English or Hungarian. It reaches the founder directly. This covers haltless.io and its subdomains, including the client portal and the developer docs, and the Haltless Edge Agent.
What you found, where, and the steps to reproduce it. A proof of concept helps. If you came across personal data, describe it rather than sending it.
We acknowledge your report within three business days (Central Time), keep you posted while we work on it, and tell you when it is fixed.
Don't access, change or delete data that isn't yours, run denial-of-service or load tests, phish or socially engineer anyone, or test physical security. Give us reasonable time to fix an issue before you publish it; we aim for 90 days and will agree a date with you.
If you follow this policy, we treat your research as authorised and won't take legal action against you for it. There is no paid bug bounty.
The same contact details, machine-readable: /.well-known/security.txt
COMMON QUESTIONS
No. The agent is outbound only. It connects out to the Haltless cloud over TLS 1.3, with optional mutual TLS, and there is no inbound path to it and no reverse tunnel. Nothing on the OT network has to accept a connection from outside.
Tenant data is hosted in the United States. Each tenant is isolated at the database level with PostgreSQL row-level security, so isolation is enforced by the database rather than by application code remembering to filter.
They can change a row. They cannot make the change verify. Each row carries a monotonic per-tenant sequence, a hash of the previous row, and an HMAC-SHA256 signature over its canonical payload, signed with a key held by the application and not by the database.
Not yet, and saying otherwise would be the kind of claim this platform exists to make checkable. Haltless is aligned to the SOC 2 Trust Services Criteria; Type II observation is planned for 2027 and no attestation report exists today.
Tell us about your machines and we come back with a tailored per-machine quote, typically within about four hours. No new hardware, no proprietary sensors, no consultants.
We use cookies to remember your choices and keep spam out of our forms. With your permission, we also measure how people use the site.
Your browser sends a Global Privacy Control signal, so every optional category stays off unless you switch it on here. Switching a category on, or choosing Accept All, overrides the signal on this site only.
Remember this choice, and the language you pick until you close your browser. Cloudflare Turnstile keeps spam out of our forms and loads only once you start filling one in. These can't be switched off.
Keep the language you pick for 12 months instead of only until you close your browser.
Google Analytics, which sets cookies, measures which pages people visit and where they came from.
Reserved for campaign measurement. Nothing on this site uses it today: we set no marketing or advertising cookies.
