One firewall, every machine you’re responsible for.
Ferrite Pro is built for one operator-grade machine. Enterprise is the same engine, aimed at a fleet: centralized visibility, policy that follows the endpoint, and forwarding into the tools your team already watches.
Built and shipping today
These aren’t roadmap promises — they’re real code, already in the product:
- SIEM & webhook forwarding. CEF over UDP/TCP, Splunk HEC, and Elastic ECS, with real per-destination delivery counters — point Ferrite’s detections at the SOC tooling you already run.
- The full Pro engine, everywhere it’s installed. Deep packet inspection, DNS-bypass detection, forensics, and system-level enforcement — the same tested core, not a stripped-down fleet edition.
- Threat & anomaly correlation. The behavior-correlator detectors and MITRE-mapped findings that ship in Pro, available per endpoint today.
On the roadmap, not yet built
Stated plainly, because implying otherwise would waste your evaluation time:
- Fleet-wide policy management. Today, policy is configured per machine. A central console to push and audit policy across every endpoint is designed but not shipped.
- SSO / SCIM provisioning. Not built yet — if this is a hard requirement for your team right now, say so; it changes how we prioritize.
- Per-seat licensing at scale. Pricing today is negotiated directly, not self-serve — see below.
How this actually works right now
Enterprise isn’t a self-serve checkout — it’s a conversation, honestly because the fleet-management layer isn’t finished and we’d rather scope a real pilot than sell you a console that doesn’t exist yet. Tell us your team size and what you’re trying to solve, and we’ll tell you plainly whether Ferrite fits today, fits after the roadmap items above land, or doesn’t fit at all.
Tell us about your team
Already running Ferrite Pro solo and thinking about your team? The same form works — mention it in the message.