{"resourceId":"vast-on-cloud-event-broker-tco-vs-confluent-20261030","versions":[{"version":"external-8bcc2bc35252766d2d61f165da5535b1d996345e084bced7194103c878bf2c1f","resource":{"id":"vast-on-cloud-event-broker-tco-vs-confluent-20261030","title":"VAST models VAST on Cloud Event Broker at $238,387 a month versus $1.1 million for Confluent Cloud Enterprise at 4 GB/s, and concedes long retention can cost more","organization":"VAST Data","sector":"AI data infrastructure vendor (cloud event streaming); applicable to state/local agency telemetry and higher-ed data platforms","geography":"Global (AWS and Microsoft Azure deployments described); no SLED customer named","publishedAt":"2026-10-30 (page metadata 19:20 UTC; modified 2026-10-31 02:04 UTC; on-page byline shows Nov 3, 2026)","publicationDate":"2026-10-30","eventDate":null,"sourceName":"VAST Data blog (Jason Gaudreau, Senior Product Marketing Manager)","sourceLabel":"Vendor TCO analysis (blog)","sourceUrl":"https://www.vastdata.com/blog/rethinking-event-streaming-tco-with-vast-on-cloud","evidenceClass":"vendor-claim","outcomeClass":"emerging","topics":["infrastructure","governance-procurement","operating-model"],"finding":"VAST's own TCO model prices a Kafka-compatible VAST Event Broker running on VAST on Cloud virtual EBoxes against Confluent Cloud Enterprise list pricing (October 2026) for a 4 GB/s, 2:1 fanout, five-day-retention workload: $238,387 versus $1,106,530 per month ($23.78 versus $110.38 per TB ingested). The gap is attributed to Confluent's per-GB ingress/egress and post-replication storage fees versus erasure coding with 2.7% to 20% parity overhead. VAST concedes long retention on flash EBoxes can cost more than archive-tier cloud offerings and says value is greatest for 1 to 14 days. Full-AZ recovery takes 3 to 15 minutes, with data lazy-loaded from object storage.","sledRelevance":"Limited and indirect. No government or education customer is named. State and local agencies and universities that stream high-volume telemetry (traffic and transit sensors, public-safety video metadata, security logs, research instruments) could use the model as a template for their own comparisons. Most SLED streaming workloads are far below 4 GB/s, where the modeled gap is smaller and fixed provisioned costs matter more.","evidence":"Vendor-authored cost model, not a measured deployment. It uses one workload profile and list pricing (low end of the regional range); the Confluent figure is described as a floor because three Enterprise clusters are pooled. No performance, latency or reliability measurements are reported, and no customer bill is shown. A Hanging Context summary published 2026-11-01 00:58 UTC repeats the figures and labels them self-reported.","architectureImplications":"Replaces broker log replication with VAST DataBase tables protected by erasure coding and Cloud-HA (block and object persistence) on AWS and Azure; topics become queryable through Trino, Presto and Spark without ETL. VAST's 5.4 knowledge-base page states VAST on Cloud clusters do not support expansion or OS upgrade, which sits uneasily with the blog's 'add more EBox VMs' scaling claim and needs confirmation for the virtual-EBox model.","governanceImplications":"Interpretation: agencies comparing streaming platforms should build their own TCO with their actual throughput, retention, fanout and contract pricing rather than adopt a vendor's single scenario. The comparison uses commercial list prices, not negotiated public-sector or cooperative-contract pricing.","securityPrivacyImplications":"The blog does not address government-cloud authorization. Confluent's government offering is FedRAMP 20x Moderate on AWS GovCloud only and supports Dedicated clusters, so the commercial Enterprise-tier baseline may not be the comparator a state agency with FedRAMP or StateRAMP-type requirements would actually buy. No VAST on Cloud government-region or authorization evidence surfaced.","caveats":"Vendor claim. Single modeled scenario; no independent reproduction; publication date ambiguous (metadata Oct 30, byline Nov 3). Event Broker performance claims have previously been criticized for missing methodology (see StorageMath item). Treat savings as a hypothesis to test, not an expected outcome.","streamIds":["vast-data"],"roles":{"sales":"This is a vendor cost model, not a customer result, so use it to open a TCO conversation rather than to promise savings. It fits state or university teams already paying usage-based streaming fees for high-volume telemetry with several consumers. Discovery should establish real throughput, retention and fanout, and whether government-cloud authorization is required. Do not quote the $238,387 versus $1.1 million comparison as typical; most SLED workloads are smaller and use negotiated pricing.","engineering":"The design question is whether replacing Kafka log replication with erasure-coded VAST DataBase tables holds up for the customer's workload. Engineers should validate Kafka-client compatibility, consumer-group behaviour, ordering, tail latency and recovery (the blog cites 3 to 15 minutes for AZ loss), and confirm whether VAST on Cloud clusters can be expanded and upgraded, since VAST's own KB lists that as a limitation. Government-region availability must be confirmed before any architecture is proposed.","delivery":"Any adoption would be a migration of producers, consumers and downstream analytics from an existing broker, so delivery planning should cover dual-running, offset handling, schema and connector replacement, and rollback. Ownership shifts from a managed streaming service to a team operating VAST clusters in the cloud. Acceptance should be defined against the agency's own cost and latency baseline, with retention kept inside the 1-to-14-day window where VAST says the model favours it."},"roleDetails":{"sales":{"customerProblem":"Usage-based streaming fees grow with throughput, retention and the number of consumers reading the same telemetry stream.","stakeholders":["Agency or university data platform owner","State or campus CIO/CTO finance staff","Security operations teams consuming log streams","Procurement and cooperative-contract officers"],"discoveryQuestions":["What sustained ingest rate, retention and consumer fanout do current streams have?","Is FedRAMP, StateRAMP or a government cloud region required?","What do you pay today under negotiated, not list, pricing?","Which analytics tools read the streams after landing?"],"valueHypothesis":"For high-throughput, multi-consumer, short-retention streams, provisioned capacity without per-GB read fees may lower cost; this is VAST's modeled hypothesis, unverified for any SLED workload.","potentialEngagement":"A bounded TCO workshop comparing the customer's own streaming bills and workload profile against a VAST on Cloud estimate, with no savings commitment.","unsupportedClaims":["Guaranteed 4-5x savings","Any SLED or government deployment of VAST Event Broker","Performance or reliability parity with Kafka","Government-cloud authorization of VAST on Cloud"]},"engineering":{"fit":"Relevant only to high-volume, multi-consumer event streams with short retention that also need SQL access to landed events.","architectureIntegration":"Kafka-protocol producers and consumers connect to VAST Event Broker VIPs on virtual EBoxes; topics land as VAST DataBase tables queried by Trino, Presto or Spark; Cloud-HA persists to block and object storage on AWS or Azure.","prerequisites":["Measured workload profile (ingest, fanout, retention, message size)","Confirmation of supported cloud regions, including any government regions","Inventory of Kafka features, connectors and schema registry in use"],"constraints":["VAST KB states VAST on Cloud clusters do not support expansion or OS upgrade","Long retention on flash can exceed archive-tier cloud costs","No government-cloud authorization evidence found","Comparator priced at commercial list rates, not government offerings"],"security":"Security controls for the broker endpoint, identity integration and encryption are not described in the blog; agencies must verify them and any required authorization before handling sensitive or CJIS-type data.","proofOfValue":["Run the agency's own throughput and fanout profile and record p99 latency","Test AZ-loss recovery time against the 3-15 minute claim","Confirm cluster expansion and upgrade path on the virtual-EBox model","Rebuild TCO with negotiated pricing for both options"]},"delivery":{"work":"Stand up a VAST on Cloud pilot cluster, mirror one production topic, and compare cost, latency and recovery against the incumbent broker.","dependencies":["Cloud account and region approvals","Kafka client and connector compatibility","Security review and authorization decision","Analytics engine connectors (Trino/Spark)"],"ownership":"Agency or campus data platform team, with cloud operations owning VAST cluster lifecycle.","skillsAdoption":"Staff need VAST cluster operations and VAST DataBase skills alongside existing Kafka knowledge; plan training before cutover.","governanceCheckpoints":["Security and authorization review before production data","Cost review against negotiated baseline after pilot","Retention policy approval (keep within modeled window)"],"acceptanceCriteria":["Proposed: pilot monthly cost per TB ingested below incumbent at measured workload","Proposed: p99 end-to-end latency within agreed SLO","Proposed: zero message loss and preserved ordering in failover test"],"risks":["Savings disappear at low throughput or long retention","Expansion/upgrade limits on cloud clusters","Lock-in to a single storage vendor's broker implementation"]}},"retrievedAt":"2026-11-02T08:34:42-06:00","enrichedAt":"2026-11-02T08:36:58-06:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Shifts skills from managed-service consumption to operating VAST clusters; smaller agencies may lack staff to run them.","procurementImplications":"Commercial list pricing in the model is not public-sector pricing; buyers should request vendor quotes under existing cooperative or state contracts and compare total cost including staff time.","operatingModelImplications":"Moves from a fully managed streaming service to a provisioned, customer-operated platform; fixed capacity must be sized and paid for regardless of actual load.","sourceVerification":{"openedUrl":"https://www.vastdata.com/blog/rethinking-event-streaming-tco-with-vast-on-cloud","referenceExcerpt":"VAST on Cloud provides the most value when deployed for retention windows from 1 to 14 days.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}