Every Genesys KPI.
Every system that needs it.
In real time.
Streamvane turns the Genesys Cloud event stream into the operational metrics your team defines — then delivers them to dashboards, message brokers, data platforms and CRMs from one engine. Managed by us, or embedded in your own cloud on Azure, AWS or GCP.
- < 1s1
- Genesys event to live KPI, end to end
- 1,200+2
- Real-time KPIs ready out of the box
- 70+
- Connector targets across 12 categories
- Your cloud
- Azure, AWS or GCP — or fully managed by us
Built for the teams that live and die by the numbers
We didn't bolt KPIs onto a dashboard. We built the Reactive Engine first.
Streamvane grew out of a production Genesys Cloud platform, not a slide deck. The hard part of operational reporting isn't drawing a chart — it's computing the same metric correctly, continuously, and getting it to every system that needs it without five teams quietly disagreeing about the number.
So that's what we engineered: one event stream in, one KPI definition, fanned out to every destination — on infrastructure you own.
From event to action
Watch a Genesys event become a shared, real-time KPI
Five stages, one continuous flow — no batch windows, no per-team re-implementation.
- 1
Genesys emits the event
Conversations, queue stats, agent states and outbound results stream out of Genesys Cloud the moment they happen.
- 2
Ingress on your cloud
Events land on an event-driven ingress — Azure Service Bus / Event Grid, or the equivalent on AWS or GCP — buffered, ordered and durable inside your boundary.
- 3
The engine computes KPIs
The engine turns raw events into 1,200+ structural KPIs derived from Genesys topics — SLAs, occupancy, abandonment, AHT, outbound results — plus any client-specific metric you define.
- 4
Fan-out to every connector
The same KPI is delivered to Power BI, Kafka, Grafana, Snowflake, Salesforce, REST and more — each one a thin platform package, not a rewrite.
- 5
Teams act in real time
In under a second, supervisors, dashboards and downstream systems react to the same numbers, at the same instant, with a shared definition of truth.
Structural KPIs for a ~1,000-agent deployment
Genesys event to delivered KPI, sub-second
Ways to run it — managed PaaS or embedded in your stack
KPI definition, reused across every destination
- 1End-to-end latency from a Genesys event to a delivered KPI, measured on a production Genesys Cloud deployment over event-driven ingress and a streaming connector. Sub-second on the streaming path; scheduled feeds follow their contracted cadence.
- 2Indicative count of structural KPIs available for a standard deployment of roughly 1,000 agents — spanning agent activity, queues, routing and outbound campaigns. Client-specific KPIs are modelled on top of the same engine.
Why teams choose Streamvane
Three things that change how Genesys reporting works
Reactive Engine
1,200+ KPIs, computed once — correct everywhere
A standard ~1,000-agent deployment ships with 1,200+ structural KPIs that derive logically from Genesys's own topics and structures — agent activity, queues, routing and outbound campaigns — all in real time. Need a metric that's unique to your business? We model client-specific KPIs on the same engine, so every number stays consistent across every destination.
- 1,200+ structural KPIs out of the box, derived from Genesys topics
- Client-specific KPIs modelled to your own definitions
- Deterministic recomputation and replay from the durable event log
- Consistent numbers across Power BI, brokers and warehouses
Connector framework
Deliver the same metric to any system, as a platform package
Every destination is a small, focused platform package that plugs into the same engine. Adding Kafka, Grafana, Snowflake or Salesforce is a connector — not a re-architecture — which is exactly why the catalog keeps growing.
- Messaging brokers, dashboards, data platforms, CRM and cloud events
- New targets ship as Global.Platform.* packages, core stays untouched
- Mix real-time streaming and scheduled feeds from one source of truth
Two ways to run it
Managed by us, or embedded in your own stack
Choose the operating model that fits your governance. Run Streamvane as a managed PaaS — we operate the Genesys integration and bridge computed KPIs into your connectors — or embed the whole architecture, plug-and-play down to components and code, inside your own technology stack. Azure-native by heritage, but equally at home on AWS or GCP.
- Managed PaaS: fastest start, we run the integration and the bridge
- Embedded: deploy the platform inside your own stack on Azure, AWS or GCP
- Your data, your keys — secrets in your vault, data residency under your control
The platform
Everything you need to operationalize Genesys KPIs
A single Reactive Engine, a growing connector catalog, and the guarantees enterprise operations and security teams ask for.
Real-time KPI reactive processing
Sub-second operational metrics from the live Genesys event stream — not nightly batch snapshots.
Multi-connector delivery
Power BI, Kafka, Event Hubs, RabbitMQ, Grafana, Kibana, Snowflake, Salesforce, REST and webhooks.
Your cloud, or managed by us
Embed the platform in your own stack on Azure, AWS or GCP, or let us run it as a managed PaaS. Your data, your keys.
Structural & client-specific KPIs
1,200+ KPIs derive straight from Genesys topics; bespoke metrics are modelled on the same engine and reused everywhere.
Pluggable platform packages
New connectors ship as Global.Platform.* packages without touching the Reactive Engine.
Durable events & replay
An ordered, durable event log lets you recompute and backfill KPIs with confidence.
Secrets in Key Vault
Credentials and connection strings live in your Key Vault — never in a vendor database.
Operational observability
Health, lag and throughput surfaced so operations teams trust the numbers they act on.
Real-time dashboards included
A visualization layer for Power BI, Grafana and Kibana — leaders watch the same sub-second KPIs, no dashboard built from scratch.
Fits your SDLC
Embed in your own languages and pipelines — .NET, Java, Ruby, Go, Rust — shipped via GitLab, Azure DevOps or GitHub Actions.
Scales with your estate
Partitioned ingress and per-connector scaling keep pace with thousands of concurrent agents and constant routing change.
Auditable KPI definitions
Every metric carries a written definition and stored history — a disputed number is traced, never argued.
One engine, many destinations
Explore the connector catalog
Every destination is a thin platform package on the same Reactive Engine. The list keeps growing — because adding one is a connector, not a rewrite.
Stream KPIs into the distributed brokers your platform already runs on.
Reference architecture
Deployed inside your own cloud — end to end
Genesys events are ingested, computed and stored on infrastructure you own and govern — Azure, AWS or GCP — or run it as a managed PaaS. Either way, connectors are the only thing that reaches outward.
↓ events
One KPI definition · computed once · governed by your policies
- Power BI
- Apache Kafka
- Grafana
- Snowflake
- Salesforce
- REST API
What operations teams tell us
One number everyone trusts
We finally have one number for service level that the contact-center floor, the BI team and the execs all trust. That alone ended a recurring monthly argument.
Adding a new destination used to be a project. With the connector model it was a package and a config change — our Kafka feed was live the same week.
Everything runs in our own Azure subscription, so security signed off fast. No Genesys data ever leaves our tenant.
Quotes are illustrative placeholders pending customer approval. Real names, logos and metrics will replace these before launch.
FAQ
Questions, answered properly
What exactly does Streamvane do?
Streamvane ingests the Genesys Cloud event stream, computes it into 1,200+ operational KPIs (service level, occupancy, abandonment, AHT, outbound results and your own custom formulas), and delivers those metrics in real time — in under a second — to whatever systems need them: dashboards, message brokers, data platforms and CRMs. It runs as a managed PaaS or embedded in your own cloud (Azure, AWS or GCP).
Where does my data live? Does anything leave my tenant?
When Streamvane is embedded in your stack, everything runs inside your own cloud subscription — events ingested onto your Service Bus / Event Grid (or the AWS/GCP equivalent), computed by the engine, stored in your database, with secrets in your vault. You own the data and the keys end to end. If you choose the managed PaaS model instead, we operate the integration on your behalf with the data-residency and isolation controls agreed at scoping.
Do we have to run it on Azure?
No. Streamvane is Azure-native by heritage, but the architecture is cloud-portable: it can be embedded in your own stack on Azure, AWS or GCP. There are two operating models — a managed PaaS where we run the Genesys integration and bridge KPIs to your connectors, or a fully embedded deployment, plug-and-play down to components and code, inside the technology stack you already operate.
How many KPIs do you support, and can they be customised?
A standard deployment of roughly 1,000 agents ships with 1,200+ structural KPIs — metrics that derive logically and naturally from Genesys's own topics and structures, covering agent activity, queues, routing and outbound campaigns, all in real time. Beyond those, we model client-specific KPIs to your exact definitions on the same engine, so custom and structural metrics behave identically across every connector.
How are new connectors added?
Each connector is a focused platform package (a Global.Platform.* component) that plugs into the same engine. Because the Reactive Engine stays untouched, adding a destination like Kafka, Grafana, Snowflake or Salesforce is a connector-sized effort rather than a re-architecture — which is why the catalog keeps expanding.
Is this real-time or batch?
Real-time, and genuinely fast: KPIs are computed continuously from the live event stream and reach streaming destinations in under a second — not the multi-second or nightly-batch latency of polling-based exports. Scheduled feeds (e.g. WFM exports) are still supported when a destination contractually needs them.
How is this different from building exports ourselves?
Hand-built exports tend to re-implement the same KPI logic per destination, drift out of sync and break on Genesys API changes. Streamvane centralizes the definition once, computes it from a durable event log, and reuses it across every connector — eliminating the per-destination glue code and the disagreements it causes.
Which Genesys metrics are supported?
Core conversation, queue, routing and agent-state metrics out of the box — service level, ASA, abandonment, occupancy, AHT, outbound results and more — plus custom KPIs defined as configuration on top of the raw event stream.
See your Genesys KPIs flowing everywhere they belong
Book a discovery call and we'll map your metrics, your destinations and a deployment on your own Azure tenant — no data lock-in, no surprises.
Streamvane by Tessovia · Azure · AWS · GCP · Your data, your keys