01
16 DHCP RFCs, in full
DHCPv4 and DHCPv6 end to end, Option 82 subscriber traceability, all 255 options parsed and indexed — each clause in the matrix names its evidence.
Learn more →Trust Center
What your security review will find: sixteen DHCP RFCs implemented in full, enforcement that fails open, an appliance that runs with zero outbound connections, and traffic data that never leaves your ClickHouse.
Strengths
What holds up under inspection
Each card links to the page your reviewer will want.
02
Fails open, by design
Enforcement lives in the Linux kernel behind a bypass flag. If inspection stops, DHCP keeps flowing — your leases never depend on our software staying up.
Learn more →03
Runs fully offline
No outbound connections at runtime. Inspected traffic, events, and analysis stay on your host, in your ClickHouse — air-gap ready.
Learn more →04
Licensing that can't take you down
An Ed25519-signed file, verified on the appliance. No licence server, no phone-home, and expiry never rips enforcement out of the kernel.
Learn more →05
A support SLA you can read
Three plans from 5×8 CET next-business-day to custom 24/7, with severity definitions and scope in a binding maintenance ToS — the same data the pricing page renders.
Learn more →Privacy
What the appliance records
The appliance records DHCP transaction metadata only — message type, options, relay info — never Layer-7 payloads. It is stored in your own local ClickHouse, with retention configurable to your policy, and nothing leaves the host unless an operator turns it on. See exactly what leaves the appliance →
This website holds itself to the same posture — no third-party trackers, no tracking cookies; details in /legal/privacy.
Operate
Deploy & operate
What a network owner needs to plan a deployment and run it for the long term, in one place.
Controls
Security controls
Signing in
Local accounts with bcrypt-hashed passwords, optional TOTP MFA with single-use backup codes, and account lockout after repeated failures (threshold and duration configurable).
Per-user IP allow/deny lists scope where each account can sign in from. Identity providers: Google OAuth, Keycloak, or generic OIDC. No LDAP or SAML today.
Roles & access
Three roles — viewer, operator, admin — with every boundary enforced server-side. Only admin reaches user management, the terminal, support, and licensing.
Sessions, tokens & keys
Server-side session records store only token hashes. Idle timeout and per-user concurrent-session caps apply, and sessions are revocable from the GUI.
API keys are revocable too, with issuance and revocation audit-logged.
Accountability
The audit log records every login and failed attempt (with reason), account and user-management changes, session lifecycle, every enforcement action with actor, device, and duration, and every support-session grant.
Remote support shell sessions are screen-recorded and retained 90 days. Audit retention is configurable per installation.
Transport & exposure
The web UI and API are served behind a TLS-terminating reverse proxy (nginx, part of the recommended install), and the appliance binds only to the addresses you configure — localhost by default — on one configurable listening port for UI and API.
The support channel is outbound-only and opt-in. Disk encryption is host-level and customer-controlled.
Compliance
Compliance & certifications
Where each framework stands today. GDPR is live; a framework appears as more than 'on the roadmap' only when an auditor has issued a report we can share.
| Framework | Status | Detail |
|---|---|---|
| GDPR | Compliant today | Documented practices and a DPA you can sign — see /legal/dpa. |
| SOC 2 Type I | On the roadmap | Targeted after the first enterprise-customer cohort. Practices already align with the trust-services criteria; we publish the report once an auditor has issued one. |
| SOC 2 Type II | On the roadmap | A 12-month observation window follows Type I issuance. |
| ISO 27001 | Available on request | Evaluated for qualifying opportunities where an RFP requires it. |
| FIPS 140-2 / 140-3 | Available on request | Offered for federal opportunities; would require a validated crypto-module swap. |
| HIPAA | N/A — out of scope | DHCP metadata does not constitute PHI under HIPAA. |
| PCI-DSS | N/A — out of scope | Our payment processor handles cardholder data; we never see PANs. |
Incident response. Incident handling is aligned with your support SLA tier (see /trust/sla); affected customers are notified within 72 hours of a confirmed incident affecting customer data.
Engage
How to engage
Talk to our team.
Bring your RFP, your DPA, and your security questionnaire — that's what this page is for.