Understand how Opslytica fits into your infrastructure — from data ingestion to real-time dashboards.
Three logical layers connect your source systems to Opslytica's analytics engine.
Read from your existing logs with zero changes, or send events directly via API. Both paths flow through the same intelligence engine.
Read from Splunk, ELK, Azure Monitor, CloudWatch, Loki, or any log platform. No source system changes.
Read from SQL Server Change Data Capture, PostgreSQL replication, or status history tables.
Direct HTTP calls to our API. Full control, works with any language.
Type-safe clients for .NET, Java, and Python with auto-batching and retry.
Customer-deployed proxy for PHI de-identification, schema mapping, and buffered forwarding.
Follow an event from source system to encrypted storage.
Source system generates an operational event (e.g., case opened, SLA clock started, ticket updated).
Event Gateway (optional) de-identifies PHI using configurable rules before the event leaves your network.
Event transmitted via HTTPS / TLS 1.3 to the Opslytica API. Only outbound connections required.
API validates schema, enforces rate limits, and queues the event for asynchronous processing.
Event stored encrypted at rest (AES-256) in your chosen data region. Encryption keys rotate automatically.
Run the Event Gateway wherever your infrastructure lives.
docker pull opslytica/event-gateway
Single container deployment. Ideal for dev, staging, or lightweight production workloads.
Official Helm chart with horizontal auto-scaling, health probes, and configurable resource limits.
Native Windows service installer. Ideal for on-premises healthcare IT environments without container infrastructure.
Azure and AWS one-click deploy from your cloud marketplace. Automatic updates and managed scaling.
Built for regulated industries with strict data handling requirements.
PHI never leaves your environment. Only de-identified operational metrics reach Opslytica.
Independently audited security controls for data handling, access, and availability.
You control where the Gateway runs. Choose your cloud region or keep data on-premises.
Minimal network configuration needed. No inbound access required.
Explore the API reference or talk to our engineering team about your deployment scenario.