Security model
Written for the engineer evaluating whether to put a device in a customer's building. No security theatre — just what the system does.
Every device has its own identity
Every device holds its own CA-issued certificate. The private key is generated on the device and never leaves it.
Enrollment is a certificate signing request: the device generates its keypair locally and sends only a CSR. Renewal is automatic. Each identity is scoped to one device in your organization, and every tunnel is mutually authenticated.
Revocation is fast
Revoke a device and its live tunnels drop in seconds — the relay re-checks certificate status continuously.
What we can and cannot see
| We can see | We cannot see |
|---|---|
| Per-interval byte and connection counters (for metrics and quotas) | The contents of passthrough traffic — it is never decrypted |
| Device and route metadata you configure | Your payloads on TLS-passthrough routes |
| An append-only audit trail of state changes | Anything a routing decision does not require |
Passthrough traffic is never decrypted at the relay. We route by TLS SNI without reading a single byte of your payload.
Routes you choose to terminate at the edge are, by definition, decrypted there to apply the access rules you enabled — that is a choice you make per route, not a default.
Tenant isolation
Every resource belongs to an organization. Before every release, an automated suite signs in as a second organization and tries to read, change or delete the first one’s devices, routes, certificates and members; every attempt must fail. What the suite checks.
Account security
Console accounts get role-based access, optional TOTP two-factor, and an append-only audit trail.
Facts
- Where it runs
- Hosted in the EU, run by Applied AI EdgeTech Limited, registered in Ireland (company no. 671821). About us.
- Request logs, traffic counters, connection history
- Request logs and connection history are shown in the console for 30 days. All three are deleted for good after 12 months. Monthly usage totals stay with the account for billing.
- Device public IP addresses
- Deleted 90 days after the device was last seen.
- Audit trail
- Kept for the life of your organization. Deleting the organization de-links it.
- Subprocessors
- Hosting: an EU data centre. Payments: Stripe. Email delivery: a transactional email provider. Each works under a contract that limits what it may do with your data.
- If there is a breach
- We tell affected customers without undue delay, and report it to the Data Protection Commission within 72 hours, as GDPR requires.
- A device revoked while offline
- It stays cut off: its certificate is refused when the device next tries to connect, and it cannot be renewed.
- Source code and exit path
- The agent and the ESP32 library are not open source. You are not locked in: the agent only dials out, so removing it leaves nothing to undo on your network; device certificates are standard X.509; and a device's bundle can be downloaded again at any time.
Live service status: status page.
Questions the review usually raises
Do you decrypt my traffic?
Passthrough traffic is never decrypted at the relay. We route by TLS SNI without reading a single byte of your payload. A route you explicitly set to terminate at the edge is decrypted there so the access rules you enabled can be applied — a per-route choice, never the default.
Where does a device private key live?
Every device holds its own CA-issued certificate. The private key is generated on the device and never leaves it. Enrollment is a certificate signing request: the device generates the keypair locally and sends only the CSR.
How quickly can we cut a device off?
Revoke a device and its live tunnels drop in seconds — the relay re-checks certificate status continuously.
How are customers kept apart?
Every resource belongs to an organization. Before every release, an automated suite signs in as a second organization and tries to read, change or delete the first one’s devices, routes, certificates and members; every attempt must fail.
What do you log about us?
Per-interval byte and connection counters for metrics and quotas, the device and route metadata you configure, and an append-only audit trail of state changes — not the contents of passthrough traffic.
What does it cost to evaluate?
One device with two routes is free forever, with no card required, which is enough to run the whole model end to end before a review. Pricing has the rest, and the PLC and CGNAT pages show it in context.