The platform
The Genesys Cloud real-time KPI platform
Streamvane is a modular real-time Genesys Cloud KPI platform: ingress, Reactive Engine, metrics store and connectors for Power BI, Kafka, Snowflake and Salesforce.
Platform philosophy
Separate concerns — turn integrations into a framework
Most contact-center integration programs fail for the same reason: every new destination re-implements ingestion, re-derives the same KPIs, and quietly drifts out of sync with the others. Streamvane breaks that pattern by separating concerns — ingest once, compute each KPI a single time, store it as your system of record, then deliver it to as many systems as you need. The payoff is one agreed definition of every metric, reused everywhere instead of rebuilt every time.
Ingest once
Genesys Cloud analytics and notification events — plus selective REST polling where the stream is incomplete — are landed once on durable, ordered ingress. No destination ever talks to Genesys directly again.
Compute once
The Reactive Engine turns raw events into agreed KPI semantics — service level, occupancy, AHT, abandonment, outbound results and your own formulas — each defined a single time and versioned.
Store
Computed KPIs persist to a client-owned operational store that becomes your system of record — queryable for APIs and feeds, and reconcilable against Genesys baselines.
Deliver many times
The same computed KPI fans out to every connector your architecture needs — dashboards, brokers, warehouses and CRMs — with no per-destination glue code to maintain.
Product modules
A Reactive Engine at the core
The competitive moat versus generic iPaaS and one-off scripts is encoded Genesys contact-center semantics — so you stop rebuilding metric logic every time routing changes.
Ingress Layer
Reliable intake of Genesys Cloud operational data into Azure.
- Service Bus subscription to Genesys analytics / notification events
- Validation, deduplication and watermarking at ingress
- Optional Genesys REST polling for metrics off the event stream
- Secrets and connection strings in Azure Key Vault
Reactive Engine
Transform raw Genesys events into operational KPI activities your business recognizes.
- Topic-aware processors mapped to Genesys DetailType semantics
- Activity handlers and buffers for high-volume streams
- EventsWeaver correlation for multi-event KPI windows
- Configurable schedulers per KPI family + consolidation
Metrics Store
Durable, queryable operational time-series owned by the customer.
- metrics-store containers partitioned by metric family
- Historical operational queries for APIs and feeds
- Housekeeping and TTL patterns for long programs
- Foundation for reconciliation against Genesys baselines
KPI catalog
1,200+ KPIs — structural by default, bespoke when you need it
A standard deployment of roughly 1,000 agents arrives with 1,200+ real-time KPIs already modelled. They split into two families — both computed on the same engine, both delivered in under a second.
Structural KPIs
Metrics that derive logically and naturally from Genesys's own topics and structures — available in real time for a standard ~1,000-agent deployment.
- Agent activity, adherence and state transitions
- Queue, routing and service-level interval metrics
- Outbound campaign and dialing outcomes
- Conversation, AHT, occupancy and abandonment families
Client-specific KPIs
Bespoke metrics unique to your business, modelled on the same Reactive Engine so they behave identically to structural KPIs across every connector.
- Custom formulas blending multiple Genesys topics
- Business-defined thresholds, weightings and windows
- New KPI families added without touching the core
- Versioned definitions, reviewable and reconciled
Structural KPIs are not a fixed report pack — because they derive from Genesys topics, they extend naturally as your routing and campaigns evolve. Client-specific KPIs add the metrics that are unique to your operation, with no compromise on latency or consistency.
Connectors are egress products on the same core
Beyond the implemented egress paths, Streamvane documents 70+ connector targets in twelve categories. New connectors ship as Global.Platform.{Name} packages — the same architecture as RabbitMQ and the Power BI dispatcher.
Packages
Five ways to buy the same engine
Each package layers connectors onto one shared Reactive Engine. Start narrow, expand without re-architecting — the KPI definitions you prove once travel with you.
Core Package
The foundationIdeal for
Platform teams building internal apps
Microsoft Package
Ideal for
Microsoft / Azure / BI-centric IT
Feeds Package
OperationalIdeal for
WFM and legacy integration leads
Enterprise Package
At scaleIdeal for
Large contact centers, BPO, telco
Partner Package
Co-deliveryIdeal for
Genesys implementation partners
Not sure which fits?
Pricing is discovery-based — no public self-serve SKU at launch. We scope to your KPI families, connectors and environments.
Compare packages & pricingReal-time dashboards
Dashboards, not just data feeds
Beyond the connectors, Streamvane ships a real-time visualization layer so supervisors and executives watch the same sub-second KPIs — in the tools they already use, with no dashboard built from scratch.
Power BI
Streaming datasets push live KPIs into the Microsoft dashboards leaders already open every morning.
Grafana
Real-time operational and NOC-style boards over a Prometheus-compatible metrics endpoint.
Kibana
KPI documents indexed into Elasticsearch for search-driven exploration and Kibana visualizations.
Bring your own
Tableau, Looker, Qlik or a bespoke front-end — all reading the same computed KPIs over REST.
Every dashboard reads the same computed KPIs as every other connector — so the wallboard, the BI report and the downstream system never disagree.
Integration depth
Engineered into your software development lifecycle
When you embed Streamvane, it lives inside your engineering reality — your languages, your services, your pipelines — not a black box bolted on the side.
Languages & runtimes
We integrate in the languages your teams already maintain — with client libraries and services that drop into your codebase, not a foreign black box.
Backend & services
KPIs are exposed to your existing backend systems and service mesh through APIs, events and SDKs your applications consume natively.
DevOps & delivery
Streamvane ships through your own pipelines as infrastructure-as-code, versioned and promoted like any service you operate — whatever CI/CD you run.
Deployment models
Run it where your governance demands
Two ways to consume Streamvane — a managed PaaS we operate as a bridge to your connectors, or the architecture embedded plug-and-play inside your own stack. Either way it stays cloud-portable across Azure, AWS and GCP.
Managed PaaS bridge
Fastest startWe operate the Genesys integration and reactive processing as a service, and bridge computed KPIs into your connectors. Fastest time-to-value, no platform to run.
Embedded in your stack
Full controlDeploy the whole architecture — plug-and-play down to components and code — natively inside the technology stack you already operate on Azure, AWS or GCP.
Client-owned cloud
RecommendedRun every resource in your own subscription on Azure (native), AWS or GCP — the strongest data-ownership and residency story.
Implemented in platform
Safe to claim today
- Service Bus ingress, Reactive Engine, the metrics store
- Power BI streaming service
- REST read APIs with authentication patterns
- Scheduled HTTP operational feeds
- RabbitMQ / FIL bridge
Framework-ready
Platform-package extension — scoped delivery
- Kafka, Azure Event Hubs, Azure Event Grid
- Grafana, Kibana, Tableau, Microsoft Fabric
- Snowflake, Synapse, Databricks
- Salesforce, ServiceNow, Microsoft Teams
- Webhooks, SFTP/Blob batch, Prometheus/OpenTelemetry
FAQ
Common questions
Can we buy only one connector?
Yes. Pilots typically start with one KPI family and one connector, then expand connector by connector on the same core — no re-platforming as you grow.
Managed PaaS or embedded in our own stack — how do we choose?
Start with the managed PaaS when you want the fastest time-to-value and prefer us to operate the Genesys integration and bridge KPIs to your connectors. Choose the embedded model when governance, data residency or platform strategy means the architecture should live inside your own stack — it deploys plug-and-play down to components and code on Azure, AWS or GCP.
Do we have to run on Azure?
No. Streamvane is Azure-native by heritage, but the architecture is cloud-portable and runs equally on AWS or GCP. Ingress, reactive processing and storage map to the managed equivalents on whichever cloud you operate.
How fast is 'real time', really?
On the event-driven streaming path, a Genesys event becomes a delivered KPI in under a second end to end — not the multi-second or nightly-batch lag of polling-based exports. Scheduled feeds (e.g. WFM exports) still follow their contracted cadence where a destination requires it.
How many KPIs do we get, and can we add our own?
A standard ~1,000-agent deployment ships with 1,200+ structural KPIs derived from Genesys topics. Beyond those, we model client-specific KPIs to your exact definitions on the same engine, so bespoke and structural metrics behave identically across every connector.
Do we need the metrics store if we only want Power BI?
It depends on the architecture. Many programs keep the operational store as the system of record even when Power BI is the first consumer — because feeds, APIs and reconciliation almost always follow. When embedded, that store lives in your own cloud.
Does it fit our engineering and DevOps practices?
Yes. When embedded, Streamvane ships through your own pipelines as infrastructure-as-code and integrates in the languages your teams maintain — .NET, Java, Ruby, Go, Rust — whether you run GitLab CI, Azure DevOps, GitHub Actions, Jenkins or Bitbucket.
Is source code included?
The engagement model defines IP and licensing, and differs between the managed PaaS and embedded deployments. We scope it explicitly at discovery.
Does this replace Genesys reporting or journey management?
No — it complements them. Genesys native views and journey analytics are excellent inside the platform; Streamvane carries those same operational KPIs outward, intact and in real time, to the WFM, BI, warehouse and client-reporting systems that live outside Genesys. We make the platform's truth usable everywhere, not redundant.
Which contact-center use cases does it cover?
Anywhere a Genesys KPI has to leave the platform: WFM and intraday actuals, self-service and automation metrics (containment, deflection, first-contact resolution), workforce-engagement families (adherence, occupancy, shrinkage), per-client BPO reporting, Microsoft and Power BI analytics, and post-migration reporting parity. The same engine and definitions serve all of them.
Start with one KPI family. Expand on proven core.
Book a discovery workshop and we'll scope ingress, reactive processing and your first connector.
Streamvane by Tessovia · Azure · AWS · GCP · Your data, your keys