Deployment
SaaS, on-prem, or hybrid — collectors stay with the network.
Optima Pulse separates control plane from data plane. SNMP, ICMP, syslog, traps, and flow collection run on site-bound edge collectors. The API, stores, and UI can run in Pulse Cloud or in your environment.
SaaS
Cloud control plane
Operators use Pulse Cloud while site-bound collectors gather telemetry from distributed networks.
On-prem
Private instance
Run the full control plane in your environment — API, stores, workers, and collectors — with offline-capable packaging.
Hybrid
Connected operations
Keep sensitive collection at the edge, apply residency controls, and operate from a central Pulse command center.
What you are actually deploying
Edge collectors
Site-bound poll and ingest. Poll targets come from the control plane; telemetry posts back over authenticated collector channels.
Control plane
Go API, Postgres, workers, NATS, VictoriaMetrics, ClickHouse, and the React console — SaaS or private instance.
Identity
OIDC/SSO via Keycloak or local authentication. RBAC and tenant isolation stay server-side either way.
Data residency
Residency routing and store placement for teams that must keep telemetry in a region or on-prem.
MSSP scale
One control plane, many tenants. Portfolio views for platform admins; customer views stay isolated.
Operations
Audit, readiness, on-prem packages, and deployment views exist in-product so install is not a separate undocumented ritual.
Next step