Ozone
Ozone is a hybrid observability and AIOps platform by TechForcz that collects telemetry inside your network, runs anomaly detection and root-cause analysis on it, and turns the result into a single correlated problem with a ticket instead of an alert storm. It is built as two cooperating tiers so collection keeps working even when the cloud is unreachable, and so raw device credentials never leave your premises.
New here? Start with the Quickstart, keep the Glossary handy, and see Licensing & Tiers for what each plan includes.
The two tiers
| Ozone Data Collector | Ozone Orchestrator | |
|---|---|---|
| Domain | collector.techforcz.com (in-network appliance) | ozone.techforcz.com (SaaS) |
| Where it runs | Inside the customer network (OVA appliance) | TechForcz cloud |
| Tenancy | Single-tenant | Multi-tenant |
| Job | Collect, store, correlate, alert, and deliver notifications locally | Manage the fleet, run heavy AI/ML, and serve the portal |
| Data stores | SQLite (state), VictoriaMetrics (metrics, 30d), Redis (cache), over a NATS JetStream bus | Managed PostgreSQL, ClickHouse (90d), VictoriaMetrics (90d), Keycloak |
| Connectivity | Dials out only, no inbound ports | Receives collector traffic; never calls into a customer network |
The collector is autonomous: if the link to the Orchestrator drops, it keeps polling devices, firing local alerts, and serving its local UI. Losing the Orchestrator degrades only fleet visibility, central config push, and upgrades, not collection. The full model is in Platform Architecture.
Core value
- Multi-protocol collection. 63 onboarding methods across 10 device categories (network, wireless, compute, storage, virtualization, container, cloud, observability, security, and load balancer), plus OT protocols like Modbus and BACnet, all normalised into one telemetry envelope.
- AIOps correlation. Anomaly detection (Isolation Forest, Z-score, EWMA, IQR), capacity forecasting (Prophet in the cloud, local linear regression at the edge), and graph-based RCA collapse dozens of symptoms into one root cause.
- LLM triage brain. The cloud
ai-triageservice runs a LangGraph agent over each correlated incident, retrieves similar past incidents from a pgvector knowledge base, and reasons toward a root cause with a confidence gate that auto-closes or escalates. - On-prem delivery. The collector delivers correlated problems directly to ServiceNow, Jira, Slack, Teams, Webex, PagerDuty, or a webhook, so notifications and tickets keep working even when the WAN is down.
Licence tiers
Ozone ships in three tiers: Trial (1 collector, up to 50 devices, 7-day retention, no AI), Professional (5 collectors, up to 250 devices, 30-day retention, AI anomaly detection and capacity forecasting), and Enterprise (unlimited collectors and devices, 90-day retention, plus LLM incident triage, SAML SSO, and HA). The full feature-by-tier matrix is the canonical Licensing & Tiers page.
Start here
| Your role | Go to |
|---|---|
| Architect or new engineer who wants to understand the system | Platform Architecture |
| Security or compliance reviewer | Security & Compliance |
| Deploying a collector on a customer site | Data Collector Deployment |
| Operating the cloud (tenants, alerts, dashboards) | SaaS Workflows |
| On call, something is broken | Troubleshooting |
Brand standard: the product is Ozone; the company is TechForcz (capital T, F, Z). The edge appliance is the Ozone Data Collector and the SaaS control plane is the Ozone Orchestrator.