[{"data":1,"prerenderedAt":1753},["ShallowReactive",2],{"active-banner":3,"navbar-featured-partner-blog":23,"cloud-terms-and-conditions":304,"navbar-pricing-featured":974},{"id":4,"title":5,"date":6,"dismissible":7,"extension":8,"link":9,"link2":10,"linkText":11,"linkText2":10,"meta":12,"stem":20,"variant":21,"__hash__":22},"banners\u002Fbanners\u002Fkafka-company-2025.md","Native Apache Kafka Service Is Coming Soon to StreamNative Cloud. Join the waitlist and get $1,000 in credits.","2026-04-01",true,"md","\u002Fnative-kafka-service-waitlist",null,"Join Waitlist",{"body":13},{"type":14,"value":15,"toc":16},"minimark",[],{"title":17,"searchDepth":18,"depth":18,"links":19},"",2,[],"banners\u002Fkafka-company-2025","default","IMIJszQOOWTfA_DV33eYUA5jqV7DrX1FWbBTBZfNvWc",{"id":24,"title":25,"authors":26,"body":28,"category":288,"createdAt":10,"date":289,"description":290,"extension":8,"featured":7,"image":291,"isDraft":292,"link":10,"meta":293,"navigation":7,"order":294,"path":295,"readingTime":296,"relatedResources":10,"seo":297,"stem":298,"tags":299,"__hash__":303},"blogs\u002Fblog\u002Fstreamnative-recognized-in-the-forrester-wave-streaming-data-platforms-2025.md","StreamNative Recognized as a Contender in The Forrester Wave™: Streaming Data Platforms, Q4 2025",[27],"David Kjerrumgaard",{"type":14,"value":29,"toc":275},[30,38,46,50,66,72,77,80,86,101,108,114,117,123,126,133,139,142,145,156,162,168,171,174,177,183,190,193,196,203,206,209,223,228,232,236,240,244,248,250,267,269],[31,32,34],"h3",{"id":33},"receives-highest-possible-scores-in-both-the-messaging-and-resource-optimization-criteria",[35,36,37],"em",{},"Receives Highest Possible Scores in BOTH the Messaging and Resource Optimization Criteria",[39,40,42],"h2",{"id":41},"introduction",[43,44,45],"strong",{},"Introduction",[47,48,49],"p",{},"Real-time data has become the backbone of modern innovation. As artificial intelligence (AI) and digital services demand instantaneous insights, organizations are realizing that streaming data is no longer optional – it's essential for delivering timely, context-rich experiences. StreamNative's data streaming platform is built precisely for this reality, ensuring data is immediate, reliable, and ready to power critical applications.",[47,51,52,53,62,63],{},"Today, we're excited to announce that Forrester Research has named StreamNative as a Contender in its evaluation, ",[54,55,57],"a",{"href":56},"\u002Freports\u002Frecognized-in-the-forrester-wave-tm-streaming-data-platforms-q4-2025",[35,58,59],{},[43,60,61],{},"The Forrester Wave™: Streaming Data Platforms, Q4 2025",". This report evaluated 15 top streaming data platform providers, and we're proud to share that ",[43,64,65],{},"StreamNative received the highest scores possible—5 out of 5—in both the Messaging and Resource Optimization criteria.",[47,67,68,69],{},"***Forrester's Take: ***",[35,70,71],{},"\"StreamNative is a good fit for enterprises that want an Apache Pulsar implementation that is also compatible with Kafka APIs.\"",[47,73,74],{},[35,75,76],{},"— The Forrester Wave™: Streaming Data Platforms, Q4 2025",[47,78,79],{},"Being recognized in the Forrester Wave is a proud milestone, and for us, it highlights how far StreamNative has come in enabling enterprises to unlock the power of real-time data. In the sections below, we'll dive into what we believe sets StreamNative apart—from our modern architecture and cloud-native design to our open-source foundation and real-time use cases—and how we see these strengths aligning with Forrester's findings.",[39,81,83],{"id":82},"trusted-by-industry-leaders",[43,84,85],{},"Trusted by Industry Leaders",[47,87,88,89,92,93,96,97,100],{},"Companies across industries are already leveraging StreamNative to drive real-time outcomes. Global enterprises like ",[43,90,91],{},"Cisco"," rely on StreamNative to handle massive IoT telemetry, supporting 245 million+ connected devices. Martech leaders such as ",[43,94,95],{},"Iterable"," process billions of events per day with StreamNative for hyper-personalized customer engagement. And in financial services, ",[43,98,99],{},"FICO"," trusts StreamNative to power its real-time fraud detection and analytics pipelines with a secure, scalable streaming backbone.",[47,102,103,104,107],{},"The Forrester report notes that, “",[35,105,106],{},"Customers appreciate the lower infrastructure costs that result from StreamNative’s cost-efficient, Kafka-compatible architecture. Customers note excellent support responsiveness…","”",[39,109,111],{"id":110},"modern-cloud-native-architecture-built-for-scale",[43,112,113],{},"Modern, Cloud-Native Architecture Built for Scale",[47,115,116],{},"From day one, StreamNative was designed with a modern architecture to meet the demanding scale and flexibility requirements of real-time data. Unlike legacy streaming systems that often rely on tightly coupled storage and compute, StreamNative's platform takes a cloud-native approach: it decouples these layers to enable elastic scalability and efficient resource utilization across any environment. The core is powered by Apache Pulsar—a distributed messaging and streaming engine—enhanced with multi-protocol support (including native Apache Kafka API compatibility) to unify diverse data streams under one roof. This means organizations can consolidate siloed messaging systems and handle both high-volume event streams and traditional message queues on a single platform, without sacrificing performance or reliability.",[47,118,119,120,107],{},"Forrester's evaluation described that “",[35,121,122],{},"StreamNative aims to provide a high-performance, multi-protocol streaming data platform: It uses Apache Pulsar with Kafka API compatibility to deliver cost-efficient, real-time applications for enterprises. It appeals to organizations that want a flexible, low-cost streaming solution, due to its focus on scalability and resource optimization, while its investments in Pulsar’s open-source ecosystem and performance optimization make it the primary platform for enterprises wishing to implement Pulsar.",[47,124,125],{},"Our cloud-first, leaderless architecture (with no single broker bottlenecks) and tiered storage model were built to maximize throughput and cost-efficiency for real-time workloads. By separating compute from storage and leveraging distributed object storage, StreamNative can retain huge volumes of event data indefinitely while keeping compute costs in check—effectively providing a flexible, low-cost streaming solution.",[47,127,128,129,132],{},"This modern design not only delivers high performance, but also ensures fault tolerance and geo-distribution out of the box, so enterprises can trust their streaming data is always available and durable. As Forrester’s evaluation noted, StreamNative ",[35,130,131],{},"\"excels at messaging and resource optimization\" and “Its platform supports use cases like real-time analytics and event-driven architectures with robust scalability.","” Our architecture provides the strong foundation that today's real-time applications demand, from ultra-fast data ingestion to seamless scale-out across hybrid and multi-cloud environments.",[39,134,136],{"id":135},"open-source-foundation-and-pulsar-expertise",[43,137,138],{},"Open Source Foundation and Pulsar Expertise",[47,140,141],{},"StreamNative's DNA is rooted in open source innovation. Our founders are the original creators of Apache Pulsar, and we've built our platform with the same open principles: freedom, flexibility, and community-driven innovation. For developers and data teams, this means adopting StreamNative comes with no proprietary lock-in—instead, you get a platform built on open standards and a thriving ecosystem. We offer broad API compatibility (Pulsar, Kafka, JMS, MQTT, and more) so that teams can work with familiar interfaces and integrate StreamNative into existing systems with ease.",[47,143,144],{},"StreamNative is the primary commercial contributor to the Apache Pulsar project and its surrounding ecosystem. We invest heavily in Pulsar's ongoing improvements our investments in Pulsar's open-source ecosystem and performance optimization bolster StreamNative's value. We also foster a vibrant community through initiatives like the Data Streaming Summit and free training resources.",[47,146,147,148,151,152,155],{},"Forrester's assessment noted that StreamNative’s “",[35,149,150],{},"events-driven agents, extensibility, and performance architecture are solid,","” and we're continuing to build on that foundation. ",[43,153,154],{},"We're actively investing in expanding our tooling for observability, governance, schema management, and developer productivity","—areas we recognize as critical for enterprise adoption and where we're committed to accelerating our roadmap.",[47,157,158,159],{},"Being open also means embracing an open ecosystem of technologies. StreamNative actively integrates with the tools and platforms that matter most to our users. We partner with industry leaders like Snowflake, Databricks, Google, and Ververica to ensure our streaming platform works seamlessly with data warehouses, lakehouse storage, and stream processing frameworks. Forrester’s evaluation observed that StreamNative’s ",[35,160,161],{},"\"investments in Pulsar’s open-source ecosystem and performance optimization make it the primary platform for enterprises wishing to implement Pulsar.\"",[39,163,165],{"id":164},"powering-real-time-use-cases-across-industries",[43,166,167],{},"Powering Real-Time Use Cases Across Industries",[47,169,170],{},"One of the greatest validations of StreamNative's approach is the success our customers are achieving with real-time data. StreamNative's platform is versatile and use-case agnostic—if an application demands high-volume, low-latency data movement, we can power it. This flexibility is why our customer base spans industries from finance and IoT to major automobile manufacturers and online gaming. The common thread is that these organizations need to process and react to data in milliseconds, and StreamNative is delivering the capabilities to make that possible.",[47,172,173],{},"Cisco uses StreamNative to underpin an IoT telemetry system of colossal scale, connecting hundreds of millions of devices and thousands of enterprise clients with real-time data streams. The platform's multi-tenant design and proven reliability allow Cisco to offer its customers a live feed of device data with unwavering confidence. In the financial sector, FICO has built streaming pipelines on StreamNative to detect fraud as transactions happen and to monitor systems in real time. With StreamNative's strong guarantees around message durability and ordering, FICO can catch anomalies or suspicious patterns within seconds. And in digital customer engagement, Iterable relies on StreamNative to process billions of events every day—clicks, views, purchases—so that marketers can trigger personalized campaigns instantly based on user behavior.",[47,175,176],{},"Our customers uniformly deal with mission-critical data streams, where downtime or delays are unacceptable. StreamNative's fault-tolerant, scalable infrastructure has proven equal to the task, handling scenarios like bursting to millions of events per second or seamlessly spanning multiple cloud regions. Forrester's report recognized StreamNative for supporting event-driven architectures with robust scalability—which for us is a reflection of our platform's ability to meet the most demanding enterprise requirements.",[39,178,180],{"id":179},"continuing-to-innovate-ursa-orca-and-the-road-ahead",[43,181,182],{},"Continuing to Innovate: Ursa, Orca, and the Road Ahead",[47,184,185,186,189],{},"While we are thrilled to be recognized in Forrester's Streaming Data Platforms Wave, we view this as just the beginning. StreamNative's vision has always been bold: to ",[43,187,188],{},"provide a unified platform that not only handles today's streaming needs but also anticipates the emerging requirements of tomorrow",".",[47,191,192],{},"One key area of focus is the convergence of streaming data with advanced analytics and AI. As Forrester points out in the report, technology leaders should look for platforms that natively integrate messaging, stream processing, and analytics to provide AI agents with real-time, contextualized information. We couldn't agree more. Our award-winning Ursa Engine and Orca Agent Engine are aimed at extending our platform up the stack—bridging the gap between data streams and data lakes, and between event streams and intelligent processing.",[47,194,195],{},"Our new Ursa Engine introduces a lakehouse-native approach to streaming: it can write events directly to table formats like Iceberg on cloud storage, eliminating entire classes of ETL jobs and making fresh data instantly available for analytics queries. By integrating streaming and lakehouse technologies, we help customers collapse data silos and accelerate their AI\u002FML pipelines.",[47,197,198,199,202],{},"Beyond analytics integration, we are also enhancing StreamNative with more out-of-the-box processing and governance capabilities. In the coming months, we plan to introduce new features for lightweight stream processing and transformation, making it easier to build reactive applications directly on the platform. We're also expanding our ecosystem of connectors and integrations, so that whether your data lands in Snowflake, Databricks, or an AI model, StreamNative will seamlessly feed it. ",[43,200,201],{},"We're investing significantly in enterprise features including security, schema registry, governance, and monitoring tooling","—capabilities that are essential for mission-critical deployments and where we're committed to continued improvement.",[47,204,205],{},"This recognition from Forrester energizes us to keep innovating at full speed. We're sharing this honor with our amazing customers, community, and partners who drive us forward every day. Your feedback and real-world challenges have helped shape StreamNative into what it is today, and together, we will shape the future of streaming data. Thank you for joining us on this journey—we're just getting started, and we can't wait to deliver even more value as we continue to evolve our platform. Onward to real-time everything!",[207,208],"hr",{},[31,210,212],{"id":211},"streamnative-in-the-forrester-wave-evaluation-findings",[43,213,214,215,222],{},"StreamNative in ",[43,216,217],{},[54,218,219],{"href":56},[43,220,221],{},"The Forrester Wave™",": Evaluation Findings",[224,225,227],"h5",{"id":226},"recognized-as-a-contender-among-15-streaming-data-platform-providers","• Recognized as a Contender among 15 streaming data platform providers",[224,229,231],{"id":230},"received-the-highest-scores-possible-50-in-both-the-messaging-and-resource-optimization-criteria","* Received the highest scores possible (5.0) in both the Messaging and Resource Optimization criteria",[224,233,235],{"id":234},"cited-as-the-primary-platform-for-enterprises-wishing-to-implement-pulsar","• Cited as the primary platform for enterprises wishing to implement Pulsar",[224,237,239],{"id":238},"noted-for-excelling-at-messaging-and-resource-optimization","• Noted for excelling at messaging and resource optimization",[224,241,243],{"id":242},"customers-cited-lower-infrastructure-costs-and-excellent-support-responsiveness","• Customers cited lower infrastructure costs and excellent support responsiveness",[224,245,247],{"id":246},"recognized-for-supporting-event-driven-architectures-with-robust-scalability","• Recognized for supporting event-driven architectures with robust scalability",[207,249],{},[251,252,254,255,258,259,189],"h6",{"id":253},"forrester-disclaimer-forrester-does-not-endorse-any-company-product-brand-or-service-included-in-its-research-publications-and-does-not-advise-any-person-to-select-the-products-or-services-of-any-company-or-brand-based-on-the-ratings-included-in-such-publications-information-is-based-on-the-best-available-resources-opinions-reflect-judgment-at-the-time-and-are-subject-to-change-for-more-information-read-about-forresters-objectivity-here","**Forrester Disclaimer: **",[35,256,257],{},"Forrester does not endorse any company, product, brand, or service included in its research publications and does not advise any person to select the products or services of any company or brand based on the ratings included in such publications. Information is based on the best available resources. Opinions reflect judgment at the time and are subject to change",". *For more information, read about Forrester’s objectivity *",[54,260,264],{"href":261,"rel":262},"https:\u002F\u002Fwww.forrester.com\u002Fabout-us\u002Fobjectivity\u002F",[263],"nofollow",[35,265,266],{},"here",[207,268],{},[251,270,272],{"id":271},"apache-apache-pulsar-apache-kafka-apache-flink-and-other-names-are-trademarks-of-the-apache-software-foundation-no-endorsement-by-apache-or-other-third-parties-is-implied",[35,273,274],{},"Apache®, Apache Pulsar®, Apache Kafka®, Apache Flink® and other names are trademarks of The Apache Software Foundation. No endorsement by Apache or other third parties is implied.",{"title":17,"searchDepth":18,"depth":18,"links":276},[277,279,280,281,282,283,284],{"id":33,"depth":278,"text":37},3,{"id":41,"depth":18,"text":45},{"id":82,"depth":18,"text":85},{"id":110,"depth":18,"text":113},{"id":135,"depth":18,"text":138},{"id":164,"depth":18,"text":167},{"id":179,"depth":18,"text":182,"children":285},[286],{"id":211,"depth":278,"text":287},"StreamNative in The Forrester Wave™: Evaluation Findings","Company","2025-12-16","StreamNative is recognized in The Forrester Wave™: Streaming Data Platforms, Q4 2025. Discover why Forrester highlights StreamNative's high-performance messaging, efficient resource use, and cost-effective Kafka API compatibility for real-time innovation.","\u002Fimgs\u002Fblogs\u002F693bd36cf01b217dcb67278f_Streamnative_blog_thumbnail.png",false,{},0,"\u002Fblog\u002Fstreamnative-recognized-in-the-forrester-wave-streaming-data-platforms-2025","10 mins read",{"title":25,"description":290},"blog\u002Fstreamnative-recognized-in-the-forrester-wave-streaming-data-platforms-2025",[300,301,302],"Announcements","Real-Time","Forrester","sOeeJtEO3O-IIfTPJjY1AFOMawZ_rf8FOH8A98NEKgU",{"id":305,"title":306,"beforeContentImage":10,"body":307,"description":966,"extension":8,"heroBg":967,"lastUpdated":968,"meta":969,"navigation":7,"path":970,"seo":971,"stem":972,"__hash__":973},"pages\u002Fcloud-terms-and-conditions.md","StreamNative Software Subscription Agreement",{"type":14,"value":308,"toc":946},[309,315,333,339,342,348,354,364,374,383,392,401,410,423,432,441,451,463,469,472,478,484,491,497,503,506,512,515,522,529,536,539,545,548,554,557,563,573,587,601,624,634,649,659,669,679,685,691,697,703,713,719,725,731,737,744,750,767,773,779,785,791,797,803,817,823,826,832,838,844,850,864,874,880,907,910,916,919,925,931,937,943],[47,310,311,314],{},[43,312,313],{},"Important",": Please read these terms before ordering, configuring and\u002For using the Subscription Service or Supported Software.",[47,316,317,320,321,324,325,328,329,332],{},[43,318,319],{},"This Software Subscription Agreement",", together with its attachments and Orders (the \"",[43,322,323],{},"Agreement","\"), is entered into as of the Effective Date by and between StreamNative and Customer. For purposes of this Agreement, StreamNative and Customer will be referred to individually as a \"",[43,326,327],{},"Party","\" and together as the \"",[43,330,331],{},"Parties","\". In consideration of the mutual covenants and promises set forth herein, the Parties hereby agree as follows:",[39,334,336],{"id":335},"_1-definitions",[43,337,338],{},"1. Definitions",[47,340,341],{},"The following capitalized terms shall have the meanings set forth below:",[47,343,344,347],{},[43,345,346],{},"1.1. \"Customer\""," means any legal entity that enters into the agreement with StreamNative. For Marketplace Orders, Customer is the entity that placed the Marketplace Order.",[47,349,350,353],{},[43,351,352],{},"1.2. \"Effective Date","\" means the date specified in the applicable Order, or the Order date for any Order placed on the Marketplace or directly from StreamNative via its website.",[47,355,356,359,360,363],{},[43,357,358],{},"1.3."," \"",[43,361,362],{},"Licensed Software","\" means the StreamNative software product identified on an Order (other than Open Source Software), including any and all modifications, enhancements, bug fixes, patches and workarounds thereto.",[47,365,366,369,370,373],{},[43,367,368],{},"1.4.","\"",[43,371,372],{},"Marketplace","\" a third-party marketplace on which StreamNative offers subscriptions to the Licensed Software and Support Services.",[47,375,376,369,379,382],{},[43,377,378],{},"1.5.",[43,380,381],{},"Open Source Software","\" means StreamNative or third party software that is licensed, provided or distributed under any open source license, including any license meeting the Open Source Definition (as promulgated by the Open Source Initiative) or the Free Software Definition (as promulgated by the Free Software Foundation), or any substantially similar license.",[47,384,385,359,388,391],{},[43,386,387],{},"1.6.",[43,389,390],{},"Order","\" means an order form for (a) the Licensed Software, Support Services, and\u002For any professional and training services, agreed upon by the parties and referencing this Agreement, or (b) the Licensed Software and\u002For any Support Services selected and activated by Customer via an order placed through StreamNative's website or a Marketplace.",[47,393,394,397,398,189],{},[43,395,396],{},"1.7. \"Service Level Agreement\""," means the cloud uptime service level agreement for Bring Your Own Cloud and StreamNative Hosted deployments as set forth at ",[54,399,400],{"href":400},"\u002Fcloud-uptime-sla",[47,402,403,359,406,409],{},[43,404,405],{},"1.8.",[43,407,408],{},"Software Subscription Fee","\" means the fee for the Licensed Software purchased by Customer as specified on an Order.",[47,411,412,369,415,418,419,422],{},[43,413,414],{},"1.9.",[43,416,417],{},"Statement of Work","\" or \"",[43,420,421],{},"SOW","\" means a mutually executed written document referencing this Agreement that specifies any professional services to be provided by StreamNative to Customer.",[47,424,425,369,428,431],{},[43,426,427],{},"1.10.",[43,429,430],{},"StreamNative\""," means StreamNative, Inc., a Delaware corporation with an address at 440 N Wolfe Rd, Sunnyvale, CA 94085.",[47,433,434,359,437,440],{},[43,435,436],{},"1.11.",[43,438,439],{},"Subscription Term","\" means the applicable initial and any renewal term as set forth in the applicable Order.",[47,442,443,446,447,450],{},[43,444,445],{},"1.12",". \"",[43,448,449],{},"Support Fee","\" means the fee for the Support Services purchased by Customer at the price for the applicable support tier set forth in the Order.",[47,452,453,369,456,459,460],{},[43,454,455],{},"1.13.",[43,457,458],{},"Support Services","\" means the technical support services identified on an Order, as described in StreamNative's Support Policy at ",[54,461,462],{"href":462},"\u002Fsupport-policy",[39,464,466],{"id":465},"_2-software-subscription-and-license",[43,467,468],{},"2. Software Subscription and License",[47,470,471],{},"Subject to Customer's timely payment of all fees due hereunder and compliance with the terms and conditions of this Agreement, StreamNative hereby grants Customer a non-exclusive, non-transferable, non-sublicensable, revocable license to install and use the Licensed Software during the Subscription Term in accordance with any restrictions set forth herein. Customer may not offer the Licensed Software on a service bureau basis, including as a stand-alone product offering to a third party, without StreamNative's prior written consent. The license in this Section 2 will terminate upon the expiration or termination of the Subscription Term.",[47,473,474,477],{},[43,475,476],{},"2.1. Open Source Software",". If applicable, any StreamNative or third-party Open Source Software provided to Customer by StreamNative is distributed or made available under the terms of the open source license agreements referenced in the applicable distribution or the applicable help, notices, about or source files. Copyrights and other proprietary rights to the Open Source Software are held by the copyright holders identified in the applicable distribution or the applicable help, notices, about or source files.",[39,479,481],{"id":480},"_3-third-party-providers-information-security",[43,482,483],{},"3. Third Party Providers; Information Security",[47,485,486,487,490],{},"If Customer elects a StreamNative Hosted deployment on its Order, StreamNative has the sole responsibility for sourcing and securing the cloud environment for the Licensed Software. If Customer elects Bring Your Own Cloud or Private Cloud License on their Order, Customer is responsible for providing all hardware and\u002For cloud infrastructure services (e.g., storage, compute power) necessary for Customer to install and use the Licensed Software. Customer represents and warrants to StreamNative that (a) the information Customer provided about its third-party cloud provider (\"",[43,488,489],{},"Provider","\") and the Provider's environment is complete and accurate, and (b) Customer has the full right and authority to provide StreamNative with sufficient access to Customer's account(s) with Provider as necessary for StreamNative to provide the Licensed Software and Support Services. If Customer or Provider changes Customer's cloud environment, Customer acknowledges that StreamNative may no longer be able to provide the Licensed Software and Support Services in the same fashion, or at all. With respect to Bring your Own Cloud and Private Cloud License deployments, Customer acknowledges that, as between it and StreamNative, it is solely responsible for the security, integrity and availability of the Licensed Software hosted on Customer's or Provider's network, systems and premises, and Customer should ensure that its network, systems and premises are protected by reasonable and appropriate access controls and other security safeguards. StreamNative shall implement and maintain reasonable security measures as required by applicable law to provide the Licensed Software and Support Services, and StreamNative may, from time to time, issue software updates. However, the Licensed Software and Support Services are provided \"as is\" and \"as available,\" when hosted on Customer's or Provider's premises or cloud environment, and StreamNative will not provide any information security support for such deployments.",[47,492,493,496],{},[43,494,495],{},"3.1. Privacy",". Customer is responsible for granting access to users of the Licensed Software and Support Services to its authorized users, preventing unauthorized access, and ensuring that Customer and all of Customer's users under its account(s) comply with privacy and information security laws applicable to the use of the Licensed Software and Support Services. Customer will not (and will not allow any third party to) use the Licensed Software or Support Services to intercept or monitor the communications of other users except as permitted by law, including with the consent of all parties to the communication. Customer has and abides by an appropriate privacy policy, will ensure that Customer has provided or shall provide any necessary notices to users or other data subjects, and will comply with all applicable data protection, privacy, communications, or information security laws relating to the information and communications from users of the Licensed Software and Support Services. Although StreamNative may collect and analyze aggregate and anonymized metrics relating to the use of the Licensed Software and Support Services for purposes of maintenance, support and product improvement, StreamNative does not access or otherwise use the contents of communications supported by the Licensed Software or Support Services. To the extent that StreamNative incidentally processes personal data of Customer's users when providing the Licensed Software or Support Services, the parties acknowledge and agree that Customer is the controller and StreamNative is the processor and service provider with respect to any such data processed pursuant to this Agreement. StreamNative will comply with Customer's instructions for processing personal data, and will not process, maintain or disclose personal data other than to provide the Licensed Software and Support Services pursuant to this Agreement.",[39,498,500],{"id":499},"_4-support-services",[43,501,502],{},"4. Support Services",[47,504,505],{},"Subject to Customer's timely payment of the Support Fee and compliance with the terms and conditions of this Agreement, StreamNative shall provide to Customer the Support Services for the Support Tier set forth in the Order during the Subscription Term. Support Services will expire at the end of the Subscription Term. While the Customer is free to use any Open Source Software under the terms of the applicable open source license after the expiration of the Subscription Term, StreamNative will not provide the Support Services after the end of the Subscription Term.",[39,507,509],{"id":508},"_5-upgrades",[43,510,511],{},"5. Upgrades",[47,513,514],{},"StreamNative will notify Customer when upgrades to the Licensed Software become available. StreamNative and\u002For Customer will install upgrades according to the following procedures based on Customer's deployment model:",[47,516,517,518,521],{},"5.1.1. ",[43,519,520],{},"Hosted Cloud and Hosted Cloud Pro",". StreamNative will automatically install upgrades on a rolling basis.",[47,523,524,525,528],{},"5.1.2.",[43,526,527],{},"Bring Your Own Cloud and BYOC Pro",". StreamNative will install upgrades and perform maintenance during such windows as determined by StreamNative and communicated to Customer in advance.",[47,530,531,532,535],{},"5.1.3. ",[43,533,534],{},"Private Cloud."," StreamNative will provide upgrades to Customer to install and Customer is responsible for installing such upgrades.",[47,537,538],{},"StreamNative shall not be liable for any consequences of Customer's failure to install upgrades as directed by StreamNative.",[39,540,542],{"id":541},"_6-restricted-activities",[43,543,544],{},"6. Restricted Activities",[47,546,547],{},"Customer shall not, and shall not encourage any third party to: (a) modify, adapt, alter, translate, or create derivative works of the Licensed Software; (b) reverse-engineer, decompile, disassemble, or attempt to derive the source code for any Licensed Software; (c) distribute, license, sublicense, lease, rent, loan, or otherwise transfer the Licensed Software to any third party; (d) remove, alter, or obscure in any way the proprietary rights notices (including copyright, patent, and trademark notices and symbols) of StreamNative or its suppliers contained on or within any copies of the Licensed Software; (e) disclose the results of any benchmark tests on the Licensed Software without StreamNative's prior written consent; (f) use the Licensed Software for the purpose of creating any product or service that may compete with the Licensed Software or the Support Services, or any other products, software or services offered by StreamNative; or (g) use the Licensed Software other than as described in the documentation provided therewith, as expressly permitted in this Agreement, or for any unlawful purpose.",[39,549,551],{"id":550},"_7-ownership-of-licensed-software",[43,552,553],{},"7. Ownership of Licensed Software",[47,555,556],{},"StreamNative and its licensors own and retain all right, title, and interest, including all intellectual property rights, in and to the Licensed Software, including any improvements, modifications, and enhancements to it. Except for the rights expressly granted in this Agreement, Customer shall acquire no other rights, express or implied, in or to the Licensed Software, and all rights not expressly provided to Customer hereunder are reserved by StreamNative and its licensors. The Licensed Software provided or made available hereunder is licensed, not sold.",[39,558,560],{"id":559},"_8-fees-and-billing",[43,561,562],{},"8. Fees and Billing",[47,564,565,568,569,572],{},[43,566,567],{},"8.1. Payments and Invoicing."," StreamNative will invoice Customer for the Software Subscription Fee and Support Fees with the billing frequency specified in Customer's Order. The Software Subscription Fee, Support Fee, Excess Usage Fees (as defined below) and any professional services fees are collectively referred to as \"",[43,570,571],{},"Fees","\". Customer is responsible for providing complete and accurate billing and contact information to StreamNative and notifying StreamNative of any changes to such information. Customer will pay to StreamNative all Fees within thirty (30) days of StreamNative's invoices therefore.",[47,574,575,578,579,582,583,586],{},[43,576,577],{},"8.2. Consumption Units",". Software Subscription Fees paid by Customer under this Agreement will be applied as consumption units (\"",[43,580,581],{},"Consumption Units","\") to Customer's account in the StreamNative cloud console (\"",[43,584,585],{},"Customer's Account","\") at a standard rate of $0.10 per Consumption Unit. Consumption Units will be automatically applied toward Customer's consumption of the Licensed Software based on Customer's actual usage of the Licensed Software on each usage dimension on the Order on an hourly basis, and deducted from Customer's Account accordingly.",[47,588,589,592,593,596,597,600],{},[43,590,591],{},"8.3. Support Units."," Support Fees paid by Customer under this Agreement will be applied to Customer's Account as Support Units, at a rate of the Support Percentage on the Customer's Order, ",[35,594,595],{},"multiplied by"," $0.10 (the \"",[43,598,599],{},"Support Unit Price","\"). One Support Unit will be deducted from Customer's account for each Consumption Unit used by Customer.",[47,602,603,606,607,610,611,614,615,619,620,623],{},[43,604,605],{},"8.4. Usage Metrics; Unit Terms."," StreamNative shall maintain records of the Customer's usage of Licensed Software (including for Excess Usage, as defined below) in Customer's Account (the \"",[43,608,609],{},"Usage Metrics","\"). Consumption Units and Support Units (collectively, \"",[43,612,613],{},"Units","\") may be used only by Customer, are non-transferable, and may not be assigned, sold, or transferred to any third party without the prior written consent of the StreamNative. Any discount on Customer's Order will only apply to the amount of cash Fees payable by Customer, and will not impact the price or quantity of any Units applied to Customer's account. Units are non-refundable and may not be redeemed for cash. StreamNative reserves the right to adjust the amount of Units applied to the Customer's account in the event of billing errors, unauthorized usage, or other circumstances warranting such adjustments, as determined by the StreamNative in its sole discretion. Units are allocated to Customer's Account according to the time periods set forth on the Order (typically, on a monthly or annual basis) and will expire and be forfeited if not used within the applicable period unless the Order expressly provides otherwise. Definitions for usage of the Licensed Software are available at ",[54,616,617],{"href":617,"rel":618},"https:\u002F\u002Fdocs.streamnative.io\u002Fdocs\u002Fbilling-overview",[263]," (the \"",[43,621,622],{},"Pricing Guide","\"). In the event of a conflict between the terms of the Pricing Guide and an Order, the terms of the Order shall govern.",[47,625,626,629,630,633],{},[43,627,628],{},"8.5. Included Units; Excess Usage."," Fees for StreamNative's provision of the Licensed Software and Support are determined by the quantity of Units purchased by Customer for the applicable time period on Customer's Order (the \"",[43,631,632],{},"IncludedQuantity\"","), as well as for any excess usage of the Licensed Software and Support Services. Customer is required to pay Fees for the Included Quantity for each applicable time period on the Order, regardless of Customer's actual usage of the Licensed Software. The Total Due Now on Customer's Order is the minimum Fee payable by Customer, and may increase if Customer accumulates any Excess Usage Fees.",[47,635,636,637,640,641,644,645,648],{},"8.5.1. ",[43,638,639],{},"Excess Usage."," If Customer's actual usage of the Licensed Software exceeds the Included Quantity allocated for the applicable time period on the Order (\"",[43,642,643],{},"Excess Usage\"","), additional Fees for any excess Units accumulated by Customer will be due (\"",[43,646,647],{},"Excess Usage Fees","\"). Customer shall pay Excess Usage Fees to StreamNative for the quantity of Units in excess of the Included Units at a rate of $0.10 per excess Consumption Unit, and at the Support Unit Price per excess Support Unit. No discounted rates will be applied to Units accumulated for Excess Usage. StreamNative will invoice Customer monthly in arrears for Excess Usage Fees, and Customer shall pay such Fees within thirty (30) days of its receipt of such invoices.",[47,650,651,654,655,658],{},[43,652,653],{},"8.6. Pay-As-You-Go Billing."," Customers with Pay-As-You-Go billing specified on their Order will be billed Fees for Consumption Units and Support Services monthly in arrears, based upon Customer's actual usage of the Licensed Software and Support Services, as determined by the system monitoring tools employed by StreamNative to track the Usage Metrics (\"",[43,656,657],{},"Pay-As-You-Go","\"). Billing rates for Pay-As-You-Go usage are at the rates set forth in the Pricing Guide (as may be modified from time to time in StreamNative's sole discretion) without any discount applied.",[47,660,661,664,665,668],{},[43,662,663],{},"8.7. Sizing Exercise",". StreamNative may prepare, in collaboration with Customer, a non-binding projection of Customer's anticipated usage of the Licensed Software across the various usage dimensions set forth in the Pricing Guide prior to entering an Order (the \"",[43,666,667],{},"Sizing Exercise","\") in order to estimate the minimum Fees to be payable by Customer . The Sizing Exercise is for informational purposes only, even if attached to an Order, and does not represent a binding commitment of StreamNative or Customer.",[47,670,671,674,675,678],{},[43,672,673],{},"8.8. Pilot Terms."," If Customer's order includes a trial period (the \"",[43,676,677],{},"Pilot Term","\"), the Subscription Term will commence automatically upon expiration of the Pilot Term unless Customer opts out of the Subscription Term by written notice to StreamNative prior to the expiration of the Pilot Term if the performance of the Licensed Software does not meet the success metrics set forth on an Order that includes a Pilot Term.",[47,680,681,684],{},[43,682,683],{},"8.9. Automatic Renewal of Subscription and Opt-Out."," The Subscription Term will automatically renew for additional periods equal to the Subscription Term on the Order, unless: (a) this Agreement is terminated pursuant to Section 9, or (b) either Party opts out of renewal by providing notice to the other Party within the thirty (30) period preceding the expiration of the then current term. Fees for any automatic renewal term will be priced at StreamNative's standard pricing as set forth in the Pricing Guide in effect on the date of such renewal. The provision of and rights to the Licensed Software will automatically renew at the end of the initial term and any renewal term, unless (x) either Party opts out as set forth above, or (y) Customer fails to pay the undisputed Fees required under this Agreement and fails to cure such non-payment within ten (10) days' notice from StreamNative.",[47,686,687,690],{},[43,688,689],{},"8.10. Taxes."," Customer shall pay all taxes, duties and levies of any governmental authority related to the services provided to Customer hereunder, including, but not limited to any sales, use, excise or VAT taxes, except for taxes based on StreamNative's income. If Customer claims exemption from any taxes arising under this Agreement, Customer shall provide StreamNative with documentation required by the taxing authority to support an exemption. All payments by Customer to StreamNative shall be made free and clear of and without reduction for all applicable taxes. If Customer is required to withhold any taxes on the amounts payable to StreamNative hereunder, Customer shall pay StreamNative such additional amounts as are necessary to ensure receipt by StreamNative of the full amount which StreamNative would have received but for the deduction on account of such withholding. All fees are non-refundable except as specifically set forth in this Agreement.",[47,692,693,696],{},[43,694,695],{},"8.11. Late Payments."," Any payment under the terms and conditions of this Agreement made after the date such payment is due and payable shall bear interest as of the day after the date such payment was due and payable and shall continue to accrue such interest until such payment is made at a rate equal to the lesser of either (a) two percent (2%) above the prime rate as reported by the Federal Reserve Bank of New York per month, as of the date such payment was due and payable, or (b) the maximum rate permitted by applicable law. Without prejudice to any other remedy for any breach of this Agreement, StreamNative may suspend Customer's access to the Licensed Software and Support Services and\u002For terminate this Agreement and any Order hereunder, with immediate effect, by giving written notice to Customer if Customer fails to make any payment under this Agreement within thirty (30) days after the date such payment became due and payable.",[39,698,700],{"id":699},"_9-term-and-termination",[43,701,702],{},"9. Term and Termination",[47,704,705,708,709,712],{},[43,706,707],{},"9.1. Term."," The initial term of this Agreement will commence upon the Effective Date and will be coterminous with the initial Order. If any subsequent Orders are executed by the Parties referencing this Agreement, this Agreement will continue or resume in effect with respect to the term of such subsequent Orders or SOWs. The ",[43,710,711],{},"\"Term\""," of this Agreement means the term duration set forth on such initial Order and any subsequent Orders, including renewals and extensions.",[47,714,715,718],{},[43,716,717],{},"9.2. Termination for Cause."," Either Party may terminate this Agreement or an Order upon written notice in the event the other Party materially breaches this Agreement and such breach is not cured within thirty (30) days after written notice of such breach. Either Party may also terminate this Agreement immediately if the other Party (a) terminates or suspends its business; (b) becomes subject to any bankruptcy or insolvency proceeding under federal or state statute; (c) becomes insolvent or subject to direct control by a trustee, receiver, or similar authority; or (d) has wound up or liquidated, voluntarily or otherwise.",[47,720,721,724],{},[43,722,723],{},"9.3. Effect of Termination."," Unless otherwise agreed by the Parties, upon the expiration or termination of this Agreement, all StreamNative's provision of all Support Services and Licensed Software granted hereunder will automatically terminate. All sections of this Agreement which by their nature should survive termination will survive termination, including, without limitation, accrued rights to payment, intellectual property ownership rights, confidentiality obligations, warranty disclaimers, indemnification, and limitations of liability.",[47,726,727,730],{},[43,728,729],{},"9.4. Suspension",". StreamNative may temporarily suspend Customer's access to any portion or all of the Licensed Software or Support Services if StreamNative reasonably determines that (a) Customer's use of the Licensed Software or Support Services disrupts or poses a security risk to any StreamNative system or infrastructure, or to any other customer or vendor of StreamNative; (b) Customer is using the Licensed Software or Support Services for fraudulent or illegal activities; (c) Customer has failed to pay any Fees when due; (d) StreamNative's provision of the Licensed Software or Support Services to Customer is prohibited by applicable law; or (e) Customer has failed to make full and timely payment of any fees owed hereunder. StreamNative shall use commercially reasonable efforts to provide written notice of any such suspension to Customer and to provide updates regarding resumption of access such suspension. StreamNative shall use commercially reasonable efforts to resume providing access to the Licensed Software or Support Services after the event giving rise to the suspension is cured. StreamNative will have no liability for any damage, liabilities, losses (including any loss of data or profits), or any other consequences that Customer may incur as a result of a suspension.",[39,732,734],{"id":733},"_10-feedback",[43,735,736],{},"10. Feedback",[47,738,739,740,743],{},"Customer may submit to StreamNative comments or feedback concerning the functionality and performance of the Licensed Software and Support Services, including, without limitation, identifying potential errors and improvements and suggesting ideas for modifying any of StreamNative's products or services (\"",[43,741,742],{},"Feedback","\"). By submitting Feedback, Customer hereby assigns to StreamNative all right, title, and interest in and to such Feedback.",[39,745,747],{"id":746},"_11-confidentiality",[43,748,749],{},"11. Confidentiality",[47,751,752,446,755,758,759,762,763,766],{},[43,753,754],{},"11.1. Definition",[43,756,757],{},"Confidential Information","\" means any information disclosed by one Party (\"",[43,760,761],{},"Discloser","\") to the other (\"",[43,764,765],{},"Recipient","\") in connection with this Agreement, directly or indirectly, in writing, orally or by inspection of tangible objects, which is designated as \"Confidential,\" \"Proprietary\" or some similar designation, or learned by Recipient under circumstances in which such information would reasonably be understood to be confidential. For avoidance of doubt, any third-party reports about StreamNative (such as its SOC2 audit report) provided by StreamNative to Customer will be considered Confidential Information of StreamNative, regardless of when such materials were disclosed. Confidential Information may include information disclosed in confidence to Discloser by third parties. For the purposes of this Agreement, the Licensed Software, and the results of any performance, functional or other evaluation of the Licensed Software, shall be deemed Confidential Information of StreamNative.",[47,768,769,772],{},[43,770,771],{},"11.2. Exceptions",". The confidentiality obligations in this Section 11 shall not apply with respect to any of the Discloser's Confidential information which Recipient can demonstrate: (a) was in the public domain at the time it was disclosed to Recipient or has become in the public domain through no act or omission of Recipient; (b) was known to Recipient, without restriction, at the time of disclosure as shown by the files of Recipient in existence at the time of disclosure; (c) was disclosed by Recipient with the prior written approval of Discloser; (d) was independently developed by Recipient without any use of Discloser's Confidential Information by employees or other agents of (or contractors hired by) Recipient who had no access to or did not rely on Discloser's Confidential Information; or (e) became known to Recipient, without restriction, from a source other than Discloser without breach of this Agreement by Recipient and otherwise not in violation of Discloser's rights.",[47,774,775,778],{},[43,776,777],{},"11.3. Restrictions on Use and Disclosure",". Recipient agrees not to use Discloser's Confidential Information or disclose, distribute or disseminate Discloser's Confidential Information except in furtherance of the performance of its obligations or enforcement of its rights hereunder or as otherwise expressly agreed by Discloser in writing. Recipient agrees to restrict access to such Confidential Information to those employees or consultants of Recipient who need to know such Confidential Information for performing as contemplated hereunder and have agreed in writing to be bound by a confidentiality obligation no less protective than that contained in this Agreement. Recipient shall exercise the same degree of care to prevent unauthorized use or disclosure of Discloser's Confidential Information to others as it takes to preserve and safeguard its own information of like importance, but in no event less than reasonable care.",[47,780,781,784],{},[43,782,783],{},"11.4. Compelled Disclosure",". If Recipient is compelled by a court or other competent authority or applicable law to disclose Confidential Information of Discloser, it shall give Discloser prompt written notice and shall provide Discloser with reasonable cooperation at Discloser's expense so that Discloser may take steps to oppose such disclosure or obtain a restraining order. Recipient shall not be in breach of its obligations in this Section 11 if it makes any legally compelled disclosure provided that Recipient meets the foregoing notice and cooperation requirements.",[47,786,787,790],{},[43,788,789],{},"11.5. Injunctive Relief",". Recipient acknowledges that breach of the confidentiality obligations would cause irreparable harm to Discloser, the extent of which may be difficult to ascertain. Accordingly, Recipient agrees that Discloser is entitled to immediate injunctive relief in the event of breach of an obligation of confidentiality by Recipient, and that Discloser shall not be required to post a bond or show irreparable harm in order to obtain such injunctive relief.",[47,792,793,796],{},[43,794,795],{},"11.6. Return of Confidential Information",". As between the parties, Confidential Information shall remain the property of the Discloser. At any time, upon Discloser's reasonable request, Recipient shall promptly (and in any event within thirty (30) days) return to Discloser or destroy, at the election of the Discloser, any Confidential Information of the Discloser. In addition, within thirty (30) days after termination of this Agreement, Recipient shall promptly (a) return all tangible materials containing such Confidential Information to Discloser, (b) remove all Confidential Information (and any copies thereof) from any computer systems of the Recipient, its contractors and its distributors, and (c) confirm in writing that all materials containing Confidential Information have been destroyed or returned to Discloser, as applicable, by Recipient. Recipient shall cause its affiliates, agents, contractors, and employees to strictly comply with the foregoing.",[39,798,800],{"id":799},"_12-data-protection",[43,801,802],{},"12. Data Protection",[47,804,805,806,809,810,813,814,189],{},"Each Party shall comply with all applicable data protection and data privacy laws, including without limitation the General Data Protection Regulation (EU) 2016\u002F679 (\"",[43,807,808],{},"GDPR","\"). Customer represents and warrants that, in relation to any personal data that may be disclosed by Customer to StreamNative from time to time in the course of the performance of its obligations under this Agreement, Customer shall obtain and has obtained all necessary consents from the individuals to whom the personal data relate for the disclosure of their personal data to StreamNative. Customer agrees to notify StreamNative prior to making any use of the Licensed Software or Support Services outside of the United States. Customer agrees and acknowledges that if this Agreement or the activities contemplated hereunder involve the \"Processing\" by StreamNative of \"Personal Data\" (as such terms are defined in the GDPR), then StreamNative's Data Processing Addendum (\"",[43,811,812],{},"DPA","\") will be incorporated into this Agreement as set forth at ",[54,815,816],{"href":816},"\u002Fdpa",[39,818,820],{"id":819},"_13-no-warranties",[43,821,822],{},"13. No Warranties",[47,824,825],{},"CUSTOMER EXPRESSLY UNDERSTANDS AND AGREES THAT ALL USE OF THE SUPPORT SERVICES AND LICENSED SOFTWARE IS AT CUSTOMER'S SOLE RISK AND THAT ALL SUPPORT SERVICES AND LICENSED SOFTWARE ARE PROVIDED \"AS IS\" AND \"AS AVAILABLE.\" STREAMNATIVE, ITS SUBSIDIARIES AND AFFILIATES, AND ITS LICENSORS MAKE NO EXPRESS WARRANTIES AND DISCLAIM ALL IMPLIED WARRANTIES REGARDING THE SUPPORT SERVICES OR LICENSED SOFTWARE, INCLUDING IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT, TOGETHER WITH ANY AND ALL WARRANTIES ARISING FROM COURSE OF DEALING OR USAGE IN TRADE. NO ADVICE OR INFORMATION, WHETHER ORAL OR WRITTEN, OBTAINED FROM STREAMNATIVE OR ELSEWHERE SHALL CREATE ANY WARRANTY NOT EXPRESSLY STATED IN THIS AGREEMENT. WITHOUT LIMITING THE GENERALITY OF THE FOREGOING, STREAMNATIVE, ITS SUBSIDIARIES AND AFFILIATES, AND ITS LICENSORS DO NOT REPRESENT OR WARRANT THAT: (A) CUSTOMER'S USE OF THE SUPPORT SERVICES WILL MEET CUSTOMER'S REQUIREMENTS, (B) ANY ERRORS IN THE LICENSED SOFTWARE WILL BE IDENTIFIED OR CORRECTED, OR (C) CUSTOMER'S USE OF THE SUPPORT SERVICES OR LICENSED SOFTWARE WILL BE UNINTERRUPTED, TIMELY OR SECURE.",[39,827,829],{"id":828},"_14-limitation-of-liability",[43,830,831],{},"14. Limitation of Liability",[47,833,834,837],{},[43,835,836],{},"14.1. Exclusion of Damages",". CUSTOMER EXPRESSLY UNDERSTANDS AND AGREES THAT STREAMNATIVE, ITS SUBSIDIARIES AND AFFILIATES, AND ITS LICENSORS SHALL NOT BE LIABLE TO CUSTOMER FOR ANY INDIRECT, INCIDENTAL, SPECIAL CONSEQUENTIAL OR EXEMPLARY DAMAGES INCURRED BY CUSTOMER, HOWEVER CAUSED AND UNDER ANY THEORY OF LIABILITY, INCLUDING, BUT NOT LIMITED TO, ANY LOSS OF PROFIT (WHETHER INCURRED DIRECTLY OR INDIRECTLY), ANY LOSS OF GOODWILL OR BUSINESS REPUTATION, ANY LOSS OF DATA SUFFERED, COST OF PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES, OR OTHER INTANGIBLE LOSS. THE FOREGOING LIMITATIONS ON STREAMNATIVE'S LIABILITY SHALL APPLY WHETHER OR NOT STREAMNATIVE HAS BEEN ADVISED OF OR SHOULD HAVE BEEN AWARE OF THE POSSIBILITY OF ANY SUCH LOSSES ARISING. NOTWITHSTANDING THE FOREGOING, NOTHING HEREIN SHALL EXCLUDE OR LIMIT STREAMNATIVE'S LIABILITY FOR LOSSES WHICH MAY NOT BE LAWFULLY EXCLUDED OR LIMITED BY APPLICABLE LAW.",[47,839,840,843],{},[43,841,842],{},"14.2 Liability Cap",". EXCEPT FOR LOSSES WHICH MAY NOT BE LAWFULLY LIMITED BY APPLICABLE LAW, THE TOTAL LIABILITY OF STREAMNATIVE ARISING OUT OF OR RELATED TO THIS AGREEMENT WILL NOT EXCEED THE AMOUNTS PAID BY OR DUE FROM CUSTOMER UNDER THE APPLICABLE ORDER IN THE TWELVE (12) MONTH PERIOD IMMEDIATELY PRECEDING THE EVENT GIVING RISE TO THE LIABILITY.",[39,845,847],{"id":846},"_15-indemnification",[43,848,849],{},"15. Indemnification",[47,851,852,855,856,859,860,863],{},[43,853,854],{},"15.1. Indemnification by StreamNative."," StreamNative shall indemnify and defend and hold harmless Customer from and against any loss, cost, liability, settlements, judgments, costs and other expenses (including reasonable attorney's fees) arising from third-party claims brought against Customer alleging that the Licensed Software, when used as authorized under this Agreement, infringes a third party's intellectual property right (an \"",[43,857,858],{},"Infringement Claim","\"), provided that Customer gives StreamNative: (a) notification in writing of any such action within sixty (60) days of Customer's receipt thereof; (b) sole control of the defense or settlement of such action (provided any settlement releases Customer from all liability); and (c) all reasonable information and assistance, at StreamNative's expense. Infringement Claims do not include, and StreamNative's obligations in the preceding sentence do not apply to, any claim, suit, or proceeding to the extent that it arises out of, relates to, or alleges: (i) Customer's breach of this Agreement, modification of the Licensed Software after delivery by StreamNative, or violation of any provisions of Section 6 (Restricted Activities); (ii) StreamNative's creation or modification of the Licensed Software in compliance with specifications furnished by Customer; (iii) use of the Licensed Software in combination with hardware, software, or other products or services not provided by StreamNative if the claim would not have arisen but for such combination (\"",[43,861,862],{},"Third Party Products","\"); (iv) any Open Source Software delivered or used with the Licensed Software; (v) any use of the Licensed Software other than as expressly permitted in this Agreement; (vi) Customer's failure to incorporate updates or upgrades to the Licensed Software that would have avoided the alleged infringement; (vii) Customer's use of the Licensed Software after giving or receiving notice to or from StreamNative, respectively, that the Licensed Software infringes on a third party's intellectual property right; or (viii) any claim covered by Customer's indemnification obligations in Section 15.2 (Indemnification by Customer). If StreamNative receives information regarding an infringement claim related to the Licensed Software, StreamNative may in its sole discretion: (x) modify the Licensed Software so that it is no longer infringing; (y) obtain a license for Customer's continued use of the Licensed Software; or (z) terminate the Licensed Software and refund Customer a prorated amount any prepaid but unused fees for the remainder of the Subscription Term. StreamNative's indemnity for intellectual property infringement stated above only applies if Customer uses the Licensed Software in accordance with this Agreement. THIS SECTION 15.1 STATES THE EXCLUSIVE REMEDY OF CUSTOMER AND THE ENTIRE LIABILITY OF STREAMNATIVE WITH RESPECT TO ANY INFRINGEMENT CLAIM.",[47,865,866,869,870,873],{},[43,867,868],{},"15.2. Indemnification by Customer."," Customer shall indemnify, defend, and hold harmless StreamNative, its affiliates, directors, officers, employees, agents, and other representatives of StreamNative (the \"",[43,871,872],{},"StreamNative Indemnitees","\") from and against any loss, cost, liability, settlements, judgments, costs and other expenses (including reasonable attorney's fees) arising from or relating to any third party claims brought against any StreamNative Indemnitee: (a) resulting from Customer's breach of this Agreement; (b) alleging that Customer data or Customer's installation or use of the Licensed Software, whether alone or in combination with any Third Party Product infringes, violates, or misappropriates any third party intellectual property right; (c) relating to any non-StreamNative content or data used by or on behalf of Customer in connection with the Licensed Software; or (d) Customer's negligence, fraud, or intentional misconduct.",[39,875,877],{"id":876},"_16-insurance",[43,878,879],{},"16. Insurance",[47,881,882,883,886,887,890,891,894,895,898,899,902,903,906],{},"StreamNative will maintain at its sole cost and expense the insurance described below for the Term:\n(a) ",[43,884,885],{},"Workers' Compensation",". Workers' compensation or qualified self-insurance in compliance with the requirements of each US state in which services are to be performed by StreamNative employees under this Agreement.\n(b) ",[43,888,889],{},"Employment Practices Liability",". Employment practices liability insurance with a limit of not less than $1 million for bodily injury by accident, $1 million for bodily injury by disease, and $1 million for policy limits.\n(c) ",[43,892,893],{},"Commercial General Liability",". Commercial general liability insurance providing coverage on an occurrence form basis and including coverage for bodily injury, property damage, blanket contractual liability, products liability and completed operations. The insurance must have limits of not less than $1 million each occurrence for bodily injury and property damage and personal and advertising injury, $2 million general aggregate, and $1 million products and completed operations aggregate.\n(d) ",[43,896,897],{},"Auto Liability",". Auto Liability insurance with a limit of liability of not less than $1 million for any one accident or loss for bodily injury and property damage and affording coverage for hired vehicles.\n(e) ",[43,900,901],{},"Professional Liability",". Professional Liability coverage with a limit of liability of not less than $1 million for financial loss due to the errors and omissions of StreamNative and its employees.\n(f) ",[43,904,905],{},"Cyber Security",". Cyber security and privacy liability coverage of at least $1 million for actual or alleged privacy breaches, confidentiality breaches, security breaches.",[47,908,909],{},"Where applicable, umbrella or liability insurance policies may be used to provide the limits required under this Agreement. None of the foregoing requirements as to the type and limits of insurance to be maintained by StreamNative is intended to, and such requirements should not be construed to, limit in any manner StreamNative's obligations under this Agreement.",[39,911,913],{"id":912},"_17-marketplace-terms",[43,914,915],{},"17. Marketplace Terms",[47,917,918],{},"The following terms apply solely to Orders entered through a Marketplace:",[47,920,921,924],{},[43,922,923],{},"17.1. Subscription Start Date."," The Subscription Term start date may be up to several days later than the date of the Order.",[47,926,927,930],{},[43,928,929],{},"17.2. Reporting Times",". Reporting times on Customer's usage may be shifted by several hours to accommodate varying reporting requirements by the applicable Marketplace.",[47,932,933,936],{},[43,934,935],{},"17.3. Renewals",". Any Orders subject to discounts will not automatically renew, regardless of whether Customer has checked a \"renew\" or auto-renewal box on the applicable Marketplace Order.",[39,938,940],{"id":939},"_18-miscellaneous",[43,941,942],{},"18. Miscellaneous",[47,944,945],{},"Customer agrees to comply with all applicable United States and foreign export law, regulations and license restrictions relating to the Licensed Software. This Agreement will be governed by the laws of the State of California without reference to conflict of law principles. Each Party agrees to submit to the exclusive jurisdiction of the courts located within the county of Santa Clara, California to resolve any legal matter arising from this Agreement. Neither Party may assign any of its rights or obligations under this Agreement, whether by operation of law or otherwise, without the prior written consent of the other Party (not to be unreasonably withheld) provided that StreamNative may assign the entirety of its rights and obligations under this Agreement, without consent of the Customer, to its affiliate or in connection with a merger, acquisition, corporate reorganization, or sale of all or substantially all of its assets. StreamNative may use and display Customer's name and logo on its website and marketing materials. This Agreement is the entire agreement between the parties relating to the subject matter hereof, and shall control over any additional or different terms regarding its subject matter in any correspondence, order, confirmation, invoice or similar document, even if accepted in writing by both parties. Waivers and amendments of any provision of this Agreement shall be effective only if signed by both parties. Unless otherwise stated herein, in the event of a conflict between the terms of this Agreement and any Order or SOW hereunder, the terms of this Agreement shall control. The failure of either Party to enforce its rights under this Agreement at any time for any period shall not be construed as a waiver of such rights. If any provision of this Agreement is held invalid or unenforceable, the remainder of this Agreement will continue in full force and effect and the invalid or unenforceable provision shall be reformed to the extent necessary to make it valid and enforceable. The relationship between the Parties is that of independent contractors to each other. Nothing contained herein will in any way constitute any association, partnership, or joint venture between the Parties hereto, nor shall either Party have the power to bind the other Party or incur obligations on the other Party's behalf without the other Party's prior written consent.",{"title":17,"searchDepth":18,"depth":18,"links":947},[948,949,950,951,952,953,954,955,956,957,958,959,960,961,962,963,964,965],{"id":335,"depth":18,"text":338},{"id":465,"depth":18,"text":468},{"id":480,"depth":18,"text":483},{"id":499,"depth":18,"text":502},{"id":508,"depth":18,"text":511},{"id":541,"depth":18,"text":544},{"id":550,"depth":18,"text":553},{"id":559,"depth":18,"text":562},{"id":699,"depth":18,"text":702},{"id":733,"depth":18,"text":736},{"id":746,"depth":18,"text":749},{"id":799,"depth":18,"text":802},{"id":819,"depth":18,"text":822},{"id":828,"depth":18,"text":831},{"id":846,"depth":18,"text":849},{"id":876,"depth":18,"text":879},{"id":912,"depth":18,"text":915},{"id":939,"depth":18,"text":942},"StreamNative is a cloud-based platform for building next-generation data applications using Apache Pulsar. It offers a fully-managed, flexible Pulsar-as-a-Service solution for hybrid, multi-cloud, and on-premise deployments. The company is rapidly expanding and has a diverse team across 14 countries. StreamNative is looking for motivated individuals to join their team and make a significant impact. Opportunities range from entry-level to management positions","\u002Fimgs\u002Fprivacy-policy\u002Fhero-bg.webp","February 17, 2026",{},"\u002Fcloud-terms-and-conditions",{"title":306,"description":966},"cloud-terms-and-conditions","kXFI9GdRBXVrJlnPCDxuW_m1gKB12HaZOblfcF0bfo8",{"id":975,"title":976,"authors":977,"body":982,"category":1740,"createdAt":10,"date":1741,"description":1742,"extension":8,"featured":7,"image":1743,"isDraft":292,"link":10,"meta":1744,"navigation":7,"order":294,"path":1745,"readingTime":1746,"relatedResources":10,"seo":1747,"stem":1748,"tags":1749,"__hash__":1752},"blogs\u002Fblog\u002Fhow-we-run-a-5-gb-s-kafka-workload-for-just-50-per-hour.md","How We Run a 5 GB\u002Fs Kafka Workload for Just $50 per Hour",[978,979,980,981],"Matteo Meril","Neng Lu","Hang Chen","Penghui Li",{"type":14,"value":983,"toc":1710},[984,987,990,993,996,999,1003,1006,1016,1022,1025,1033,1038,1042,1049,1052,1055,1063,1067,1070,1075,1079,1082,1085,1088,1091,1100,1104,1107,1118,1121,1125,1128,1131,1142,1145,1149,1153,1161,1164,1168,1176,1205,1209,1212,1217,1221,1224,1228,1231,1234,1239,1248,1253,1256,1259,1270,1274,1277,1288,1292,1295,1298,1303,1306,1335,1339,1341,1347,1350,1355,1360,1363,1367,1381,1385,1396,1400,1415,1424,1435,1438,1441,1445,1448,1451,1462,1465,1468,1471,1476,1481,1485,1489,1506,1510,1524,1529,1533,1544,1547,1563,1567,1578,1583,1588,1596,1600,1603,1607,1614,1618,1621,1630,1635,1644,1650,1658,1667,1676,1685,1694,1702],[47,985,986],{},"The rise of DeepSeek has shaken the AI infrastructure market, forcing companies to confront the escalating costs of training and deploying AI models. But the real pressure point isn’t just compute—it’s data acquisition and ingestion costs.",[47,988,989],{},"As businesses rethink their AI cost-containment strategies, real-time data streaming is emerging as a critical enabler. The growing adoption of Kafka as a standard protocol has expanded cost-efficient options, allowing companies to optimize streaming analytics while keeping expenses in check.",[47,991,992],{},"Ursa, the data streaming engine powering StreamNative’s managed Kafka service, is built for this new reality. With its leaderless architecture and native lakehouse storage integration, Ursa eliminates costly inter-zone network traffic for data replication and client-to-broker communication while ensuring high availability at minimal operational cost.",[47,994,995],{},"In this blog post, we benchmarked the infrastructure cost and total cost of ownership (TCO) for running a 5GB\u002Fs Kafka workload across different Kafka vendors, including Redpanda, Confluent WarpStream, and AWS MSK. Our benchmark results show that Ursa can sustain 5GB\u002Fs Kafka workloads at just 5% of the cost of traditional streaming engines like Redpanda—making it the ideal solution for high-performance, cost-efficient ingestion and data streaming for data lakehouses and AI workloads.",[47,997,998],{},"Note: We also evaluated vanilla Kafka in our benchmark; however, for simplicity, we have focused our cost comparison on vendor solutions rather than self-managed deployments. That said, it is important to highlight that both Redpanda and vanilla Kafka use a leader-based data replication approach. In a data-intensive, network-bound workload like 5GB\u002Fs streaming, with the same machine type and replication factor, Redpanda and vanilla Kafka produced nearly identical cost profiles.",[39,1000,1002],{"id":1001},"key-benchmark-findings","Key Benchmark Findings",[47,1004,1005],{},"Ursa delivered 5 GB\u002Fs of sustained throughput at an infrastructure cost of just $54 per hour. For comparison:",[1007,1008,1009,1013],"ul",{},[1010,1011,1012],"li",{},"MSK: $303 per hour → 5.6x more expensive compared to Ursa",[1010,1014,1015],{},"Redpanda: $988 per hour → 18x more expensive compared to Ursa",[47,1017,1018],{},[1019,1020],"img",{"alt":17,"src":1021},"\u002Fimgs\u002Fblogs\u002F679c71b67d9046f26edc7977_AD_4nXfvTqyBNUBu2lObdkKAx-5UNkpNP8UYULLZyOcixE6z99VMZUUEsUqWjzexI7vjyNGRNSAUoM9smYvdTP55ctAhIbrs5lmQgcSVMWdaoigbWouCl95DVSQsxooY-qqfGcYqS4g4zA.png",[47,1023,1024],{},"Beyond infrastructure costs, when factoring in both storage pricing, vendor pricing and operational expenses, Ursa’s total cost of ownership (TCO) for a 5GB\u002Fs workload with a 7-day retention period is:",[1007,1026,1027,1030],{},[1010,1028,1029],{},"50% cheaper than Confluent WarpStream",[1010,1031,1032],{},"85% cheaper than MSK and Redpanda",[47,1034,1035],{},[1019,1036],{"alt":17,"src":1037},"\u002Fimgs\u002Fblogs\u002F679c602d77e9c706de5343b8_AD_4nXeDv8rrv_C1CTCCiqYo1zpvlGYbdBk1r0VEqovAPu22iFMQZgh54Hfw9PBMLzM7jDFxKwAFDxbdG0np4XVk_tGsWhEKMloLRcmmea7lvueCx-0cFsyaE3Mya4Mxc1Dox95A6JEc.png",[39,1039,1041],{"id":1040},"ursa-highly-cost-efficient-data-streaming-at-scale","Ursa: Highly Cost-Efficient Data Streaming at Scale",[47,1043,1044,1048],{},[54,1045,1047],{"href":1046},"\u002Fblog\u002Fursa-reimagine-apache-kafka-for-the-cost-conscious-data-streaming","Ursa"," is a next-generation data streaming engine designed to deliver high performance at a fraction of the cost of traditional disk-based solutions. It is fully compatible with Apache Kafka and Apache Pulsar APIs, while leveraging a leaderless, lakehouse-native architecture to maximize scalability, efficiency, and cost savings.",[47,1050,1051],{},"Ursa’s key innovation is separating storage from compute and decoupling metadata\u002Findex operations from data operations by utilizing cloud object storage (e.g., AWS S3) instead of costly inter-zone disk-based replication. It also employs open lakehouse formats (Iceberg and Delta Lake), enabling columnar compression to significantly reduce storage costs while maintaining durability and availability.",[47,1053,1054],{},"In contrast, traditional streaming systems—like Kafka and Redpanda—depend on leader-based architectures, which drive up inter-zone traffic costs due to replication and client communication. Ursa mitigates these costs by:",[1007,1056,1057,1060],{},[1010,1058,1059],{},"Eliminating inter-zone traffic costs via a leaderless architecture.",[1010,1061,1062],{},"Replacing costly inter-zone replication with direct writes to cloud storage using open lakehouse formats.",[39,1064,1066],{"id":1065},"how-ursa-eliminates-inter-zone-traffic","How Ursa Eliminates Inter-Zone Traffic",[47,1068,1069],{},"Ursa minimizes inter-zone traffic by leveraging a leaderless architecture, which eliminates inter-zone communication between clients and brokers, and lakehouse-native storage, which removes the need for inter-zone data replication. This approach ensures high availability and scalability while avoiding unnecessary cross-zone data movement.",[47,1071,1072],{},[1019,1073],{"alt":17,"src":1074},"\u002Fimgs\u002Fblogs\u002F679c602e21b3571bb7117dca_AD_4nXd7Oahc77NjRLNvA9clLt0tsyU6MrIqVibFYv5pW5giTIcCHPr3EA_yTGzfVEUIVO3VXK56qWK8zmBCp5lY0E_4nmlWIPFrHjtHylA5NhwELjn-UB0fLG2h_kbrxrc7Cs_edvveNA.png",[31,1076,1078],{"id":1077},"leaderless-architecture","Leaderless architecture",[47,1080,1081],{},"Traditional streaming engines such as Kafka, Pulsar, or RedPanda rely on a leader-based model, where each partition is assigned to a single leader broker that handles all writes and reads.",[47,1083,1084],{},"Pros of Leader-Based Architectures:\n✔ Maintains message ordering via local sequence IDs\n✔ Delivers low latency and high performance through message caching",[47,1086,1087],{},"Cons of Leader-Based Architectures:\n✖ Throughput bottlenecked by a single broker per partition\n✖ Inter-zone traffic required for high availability in multi-AZ deployments",[47,1089,1090],{},"While Kafka and Pulsar offer partial solutions (e.g., reading from followers, shadow topics) to reduce read-related inter-zone traffic, producers still send data to a single leader.",[47,1092,1093,1094,1099],{},"Ursa removes the concept of topic ownership, allowing any broker in the cluster to handle reads or writes for any partition. The primary challenge—ensuring message ordering—is solved with ",[54,1095,1098],{"href":1096,"rel":1097},"https:\u002F\u002Fgithub.com\u002Fstreamnative\u002Foxia",[263],"Oxia",", a scalable metadata and index service created by StreamNative in 2022.",[31,1101,1103],{"id":1102},"oxia-the-metadata-layer-enabling-leaderless-architecture","Oxia: The Metadata Layer Enabling Leaderless Architecture",[47,1105,1106],{},"Ensuring message ordering in a leaderless architecture is complex, but Ursa solves this with Oxia:",[1007,1108,1109,1112,1115],{},[1010,1110,1111],{},"Handles millions of metadata\u002Findex operations per second",[1010,1113,1114],{},"Generates sequential IDs to maintain strict message ordering",[1010,1116,1117],{},"Optimized for Kubernetes with horizontal scalability",[47,1119,1120],{},"Producers and consumers can connect to any broker within their local AZ, eliminating inter-zone traffic costs while maintaining performance through localized caching.",[31,1122,1124],{"id":1123},"zero-interzone-data-replication","Zero interzone data replication",[47,1126,1127],{},"In most distributed systems, data replication from a leader (primary) to followers (replicas) is crucial for fault tolerance and availability. However, replication across zones can inflate infrastructure expenses substantially.",[47,1129,1130],{},"Ursa avoids these costs by writing data directly to cloud storage (e.g., AWS S3, Google GCS):",[1007,1132,1133,1136,1139],{},[1010,1134,1135],{},"Built-In Resilience: Cloud storage inherently offers high availability and fault tolerance without inter-zone traffic fees.",[1010,1137,1138],{},"Tradeoff: Slightly higher latency (sub-second, with p99 at 500 milliseconds) compared to local disk\u002FEBS (single-digit to sub-100 milliseconds), in exchange for significantly lower costs (up to 10x lower).",[1010,1140,1141],{},"Flexible Modes: Ursa is an addition to the classic BookKeeper-based engine, providing users with the flexibility to optimize for either cost or low latency based on their workload requirements.",[47,1143,1144],{},"By foregoing conventional replication, Ursa slashes inter-zone traffic costs and associated complexities—making it a compelling option for organizations seeking to balance high-performance data streaming with strict budget constraints.",[39,1146,1148],{"id":1147},"how-we-ran-a-5-gbs-test-with-ursa","How We Ran a 5 GB\u002Fs Test with Ursa",[31,1150,1152],{"id":1151},"ursa-cluster-deployment","Ursa Cluster Deployment",[1007,1154,1155,1158],{},[1010,1156,1157],{},"9 brokers across 3 availability zones, each on m6i.8xlarge (Fixed 12.5 Gbps bandwidth, 32 vCPU cores, 128 GB memory).",[1010,1159,1160],{},"Oxia cluster (metadata store) with 3 nodes of m6i.8xlarge, distributed across three availability zones (AZs).",[47,1162,1163],{},"During peak throughput (5 GB\u002Fs), each broker’s network usage was about 10 Gbps.",[31,1165,1167],{"id":1166},"openmessaging-benchmark-workers-configuration","OpenMessaging Benchmark Workers & Configuration",[47,1169,1170,1171,1175],{},"The OpenMessaging Benchmark(OMB) Framework is a suite of tools that make it easy to benchmark distributed messaging systems in the cloud. Please check ",[54,1172,1173],{"href":1173,"rel":1174},"https:\u002F\u002Fopenmessaging.cloud\u002Fdocs\u002Fbenchmarks\u002F",[263]," for details.",[1007,1177,1178,1193,1202],{},[1010,1179,1180,1181,1186,1187,1192],{},"12 OMB workers: 6 for ",[54,1182,1185],{"href":1183,"rel":1184},"https:\u002F\u002Fgist.github.com\u002Fcodelipenghui\u002Fd1094122270775e4f1580947f80c5055",[263],"producers",", 6 for ",[54,1188,1191],{"href":1189,"rel":1190},"https:\u002F\u002Fgist.github.com\u002Fcodelipenghui\u002F06bada89381fb77a7862e1b4c1d8963d",[263],"consumers"," across 3 availability zones, on m6i.8xlarge instances. Each worker is configured with 12 CPU cores and 48 GB memory.",[1010,1194,1195,1196,1201],{},"Sample YAML ",[54,1197,1200],{"href":1198,"rel":1199},"https:\u002F\u002Fgist.github.com\u002Fcodelipenghui\u002F204c1f26c4d44a218ae235bf2de99904",[263],"scripts"," provided for Kafka-compatible configuration and rate limits.",[1010,1203,1204],{},"Achieved consistent 5 GB\u002Fs publish\u002Fsubscribe throughput.",[39,1206,1208],{"id":1207},"ursa-benchmark-tests-results","Ursa Benchmark Tests & Results",[47,1210,1211],{},"The following diagram demonstrates that Ursa can consistently handle 5 GB\u002Fs of traffic, fully saturating the network across all broker nodes.",[47,1213,1214],{},[1019,1215],{"alt":17,"src":1216},"\u002Fimgs\u002Fblogs\u002F679c602d7b261bac1113f7d6_AD_4nXdDPsRc3koXICiFF0bqSmGWbJt_RlUy4FE3ruuWOfbCfpcqZ1dejjqGbkaCJv2hQFL1nirRouBVRW2l5uMWBvY9naMqGB_wHcLI14dBM0f85TXhmdm3UxEv1yGX9Y4hf5FttSkZew.png",[39,1218,1220],{"id":1219},"comparing-infrastructure-cost","Comparing Infrastructure Cost",[47,1222,1223],{},"This benchmark first evaluates infrastructure costs of running a 5 GB\u002Fs streaming workload (1:1 producer-to-consumer ratio) across different data streaming engines, including Ursa, Redpanda, and AWS MSK, with a focus on multi-AZ deployments to ensure a fair comparison.",[31,1225,1227],{"id":1226},"test-setup-key-assumptions","Test Setup & Key Assumptions",[47,1229,1230],{},"All tests use multi-AZ configurations, with clusters and clients distributed across three AWS availability zones (AZs). Cluster size scales proportionally to the number of AZs, and rack-awareness is enabled for all engines to evenly distribute topic partitions and leaders.",[47,1232,1233],{},"To ensure a fair comparison, we selected the same machine type capable of fully utilizing both network and storage bandwidth for Ursa and Redpanda in this 5GB\u002Fs test:",[1007,1235,1236],{},[1010,1237,1238],{},"9 × m6i.8xlarge instances",[47,1240,1241,1242,1247],{},"However, MSK's storage bandwidth limits vary depending on the selected instance type, with the highest allowed limit capped at 1000 MiB\u002Fs per broker, according to",[54,1243,1246],{"href":1244,"rel":1245},"https:\u002F\u002Fdocs.aws.amazon.com\u002Fmsk\u002Flatest\u002Fdeveloperguide\u002Fmsk-provision-throughput-management.html#throughput-bottlenecks",[263]," AWS documentation",". Given this constraint, achieving 5 GB\u002Fs throughput with a replication factor of 3 required the following setup:",[1007,1249,1250],{},[1010,1251,1252],{},"15 × kafka.m7g.8xlarge (32 vCPUs, 128 GB memory, 15 Gbps network, 4000 GiB EBS).",[47,1254,1255],{},"This configuration was necessary to work around MSK's storage bandwidth limitations, ensuring a comparable cost basis to other evaluated streaming engines.",[47,1257,1258],{},"Additional key assumptions include:",[1007,1260,1261,1264,1267],{},[1010,1262,1263],{},"Inter-AZ producer traffic: For leader-based engines, two-thirds of producer-to-broker traffic crosses AZs due to leader distribution.",[1010,1265,1266],{},"Consumer optimizations: Follower fetch is enabled across all tests, eliminating inter-AZ consumer traffic.",[1010,1268,1269],{},"Storage cost exclusions: This benchmark only evaluates streaming costs, assuming no long-term data retention.",[31,1271,1273],{"id":1272},"inter-broker-replication-costs","Inter-Broker Replication Costs",[47,1275,1276],{},"Inter-broker (cross-AZ) replication is a major cost driver for data streaming engines:",[1007,1278,1279,1282,1285],{},[1010,1280,1281],{},"RedPanda: Inter-broker replication is not free, leading to substantial costs when data must be copied across multiple availability zones.",[1010,1283,1284],{},"AWS MSK: Inter-broker replication is free, but MSK instance pricing is significantly higher (e.g., $3.264 per hour for kafka.m7g.8xlarge vs $1.306 per hour for an on-demand m7g.8xlarge). The storage price of MSK is $0.10 per GB-month which is significantly higher than st1, which costs $0.045 per GB-month. Even though replication is free, client-to-broker traffic still incurs inter-AZ charges.",[1010,1286,1287],{},"Ursa: No inter-broker replication costs due to its leaderless architecture, eliminating inter-zone replication costs entirely.",[31,1289,1291],{"id":1290},"zone-affinity-reducing-inter-az-costs","Zone Affinity: Reducing Inter-AZ Costs",[47,1293,1294],{},"We evaluated zone affinity mechanisms to further reduce inter-AZ data transfer costs.",[47,1296,1297],{},"Consumers:",[1007,1299,1300],{},[1010,1301,1302],{},"Follower fetch is enabled across all tests, ensuring consumers fetch data from replicas in their local AZ—eliminating inter-zone consumer traffic except for metadata lookups",[47,1304,1305],{},"Producers:",[1007,1307,1308,1317,1326],{},[1010,1309,1310,1311,1316],{},"Kafka protocol lacks an easy way to enforce producer AZ affinity (though ",[54,1312,1315],{"href":1313,"rel":1314},"https:\u002F\u002Fcwiki.apache.org\u002Fconfluence\u002Fdisplay\u002FKAFKA\u002FKIP-1123:+Rack-aware+partitioning+for+Kafka+Producer",[263],"KIP-1123"," aims to address this). And it only works with the default partitioner (i.e., when no record partition or record key is specified).",[1010,1318,1319,1320,1325],{},"Redpanda recently introduced ",[54,1321,1324],{"href":1322,"rel":1323},"https:\u002F\u002Fdocs.redpanda.com\u002Fredpanda-cloud\u002Fdevelop\u002Fproduce-data\u002Fleader-pinning\u002F",[263],"leader pinning",", but this only benefits setups where producers are confined to a single AZ—not applicable to our multi-AZ benchmark.",[1010,1327,1328,1329,1334],{},"Ursa is the only system in this test with ",[54,1330,1333],{"href":1331,"rel":1332},"https:\u002F\u002Fdocs.streamnative.io\u002Fdocs\u002Fconfig-kafka-client#eliminate-cross-az-networking-traffic",[263],"built-in zone affinity for both producers and consumers",". It achieves this by embedding producer AZ information in client.id, allowing metadata lookups to route clients to local-AZ brokers, eliminating inter-AZ producer traffic.",[31,1336,1338],{"id":1337},"cost-comparison-results","Cost Comparison Results",[47,1340,1005],{},[1007,1342,1343,1345],{},[1010,1344,1012],{},[1010,1346,1015],{},[47,1348,1349],{},"Ursa’s leaderless architecture, zone affinity, and native cloud storage integration deliver unparalleled cost efficiency, making it the most cost-effective choice for high-throughput data streaming workloads.",[47,1351,1352],{},[1019,1353],{"alt":17,"src":1354},"\u002Fimgs\u002Fblogs\u002F679c72208198ca36a352f228_AD_4nXeeZuM8T-xBlD4Vf3j67K618n08qh8wIDLLtiLJG0ssA1Wj1V26u7wIDTX9sqLrtw8mB2c299dwzarGen62CG0Vh7nWstn5qbPGFcBaKJYEepTsLr5fHWv1U8uqbg8Y0UOK6fJ7.png",[47,1356,1357],{},[1019,1358],{"alt":17,"src":1359},"\u002Fimgs\u002Fblogs\u002F679c625978031f40229de484_AD_4nXdLkLLJ30KKr-_A_rN1j8akVwBYacAWIPzWHoOReJF421890kfByZoQQxkLczihVSmiw5Q9J51-V9I2SEKITbwsYnANDDTlAVL5nQ_jfaHNTe9VEWhSoa7DZooCnilDYL6l6msmJg.png",[47,1361,1362],{},"The detailed infrastructure cost calculations for each data streaming engine are listed below:",[31,1364,1366],{"id":1365},"streamnative-ursa","StreamNative - Ursa",[1007,1368,1369,1372,1375,1378],{},[1010,1370,1371],{},"Server EC2 costs: 9 * $1.536\u002Fhr = $14",[1010,1373,1374],{},"Client EC2 costs: 9 * $1.536\u002Fhr =$14",[1010,1376,1377],{},"S3 write requests costs: 1350 r\u002Fs * $0.005\u002F1000r * 3600s = $24",[1010,1379,1380],{},"S3 read requests costs: 1350 r\u002Fs * $0.0004\u002F1000r * 3600s = $2",[31,1382,1384],{"id":1383},"aws-msk","AWS MSK",[1007,1386,1387,1390,1393],{},[1010,1388,1389],{},"Server EC2 costs: 15 * $3.264\u002Fhr = $49",[1010,1391,1392],{},"Client side EC2 costs: 9 * $1.536\u002Fhr =$14",[1010,1394,1395],{},"Interzone traffic - producer to broker: 5GB\u002Fs * ⅔ * $0.02\u002FG(in+out) * 3600 = $240",[31,1397,1399],{"id":1398},"redpanda","RedPanda",[1007,1401,1402,1404,1406,1409,1412],{},[1010,1403,1371],{},[1010,1405,1374],{},[1010,1407,1408],{},"Interzone traffic - producer to broker: 5GB\u002Fs * ⅔ * $0.02\u002FGB(in+out) * 3600 = $240",[1010,1410,1411],{},"Interzone traffic - replication: 10GB\u002Fs * $0.02\u002FGB(in+out) * 3600 = $720",[1010,1413,1414],{},"Interzone traffic - broker to consumer: $0 (fetch from local zone)",[47,1416,1417,1418,1423],{},"Please note that we were unable to test ",[54,1419,1422],{"href":1420,"rel":1421},"https:\u002F\u002Fwww.redpanda.com\u002Fblog\u002Fcloud-topics-streaming-data-object-storage",[263],"Redpanda with Cloud Topics",", as it remains an announced but unreleased feature and is not yet available for evaluation. Based on the limited information available, while Cloud Topics may help optimize inter-zone data replication costs, producers still need to traverse inter-availability zones to connect to the topic partition owners and incur inter-zone traffic costs of up to $240 per hour.",[1007,1425,1426,1432],{},[1010,1427,1428,1431],{},[54,1429,1315],{"href":1313,"rel":1430},[263]," (when implemented) will help mitigate producer-to-broker inter-zone traffic, but it is not yet available. And it only works with the default partitioner (no record partition or key is specified).",[1010,1433,1434],{},"Redpanda’s leader pinning helps only when all producers for the pinned topic are confined to a single AZ. In multi-AZ environments (like our benchmark), inter-zone producer traffic remains unavoidable.",[47,1436,1437],{},"Additionally, Redpanda’s Cloud Topics architecture is not documented publicly. Their blog mentions \"leader placement rules to optimize produce latency and ingress cost,\" but it is unclear whether this represents a shift away from a leader-based architecture or if it uses techniques similar to Ursa’s zone-aware approach.",[47,1439,1440],{},"We may revisit this comparison as more details become available.",[39,1442,1444],{"id":1443},"comparing-total-cost-of-ownership","Comparing Total Cost of Ownership",[47,1446,1447],{},"As highlighted earlier, with a BYOC Ursa setup, you can achieve 5 GB\u002Fs throughput at just 5% of the infrastructure cost of a traditional leader-based data streaming engine, such as Kafka or RedPanda, while managing the infrastructure yourself. This significant cost reduction is enabled by Ursa’s leaderless architecture and lakehouse-native storage design, which eliminate overhead costs such as inter-zone traffic and leader-based data replication. By leveraging a lakehouse-native, leaderless architecture, Ursa reduces resource requirements, enabling you to handle high data throughput efficiently and at a fraction of the cost of RedPanda.",[47,1449,1450],{},"Now, let’s examine the total cost comparison, evaluating Ursa alongside other vendors, including those that have adopted a leaderless architecture (e.g., Confluent WarpStream). This comparison is based on a 5GB\u002Fs workload with a 7-day retention period, factoring in both storage cost and vendor costs Here are the key findings:",[1007,1452,1453,1456,1459],{},[1010,1454,1455],{},"Ursa ($164,353\u002Fmonth) is: 50% cheaper than Confluent WarpStream ($337,068\u002Fmonth)",[1010,1457,1458],{},"85% cheaper than AWS MSK ($1,115,251\u002Fmonth)",[1010,1460,1461],{},"86% cheaper than Redpanda ($1,202,853\u002Fmonth)",[47,1463,1464],{},"In addition to Ursa’s architectural advantages—eliminating most inter-AZ traffic and leveraging lakehouse storage for cost-effective data retention—it also adopts a more fair and cost-efficient pricing model: Elastic Throughput-based pricing. This approach aligns costs with actual usage, avoiding unnecessary overhead.",[47,1466,1467],{},"Unlike WarpStream, which charges for both storage and throughput, Ursa ensures that customers only pay for the throughput they actively use. Ursa’s pricing is based on compressed data sent by clients, meaning the more data compressed on the client side, the lower the cost. In contrast, WarpStream prices are based on uncompressed data, unfairly inflating expenses and failing to incentivize customers to optimize their client applications.",[47,1469,1470],{},"This distinction is crucial, as compressed data reduces both storage and network costs, making Ursa’s pricing model not only more cost-effective but also more transparent and predictable.",[47,1472,1473],{},[1019,1474],{"alt":17,"src":1475},"\u002Fimgs\u002Fblogs\u002F679c602d194800c9206d9d58_AD_4nXcFlf755xgyz7htxhMhBV5fGrsxy642mQNodt61DTok_z1dwkw5A6lkO5hatXVneCaB0anbZPAyvLI3MlIMuQEYLEACHHvQMOr5UfaB37dfzkdqewDEvcT-20VGd_zzvJsuA00zGA.png",[47,1477,1478],{},[1019,1479],{"alt":17,"src":1480},"\u002Fimgs\u002Fblogs\u002F679c62594e9c2e629fae73aa_AD_4nXeU6cOgItnjLsEZCOf13TEvMY_SHWWIxYP2OYUj-B1GUPyWO78OG08K_v03hwYSVcg06f9dqDiGmdwy76vynjmiDGL5bluZ5_XF4nSU_r59oOZdfViXndXt6s11vVOY7qwfZN8v.png",[31,1482,1484],{"id":1483},"cost-breakdown","Cost Breakdown",[1486,1487,1488],"h4",{"id":1365},"StreamNative – Ursa",[1007,1490,1491,1494,1497,1500,1503],{},[1010,1492,1493],{},"EC2 (Server): 9 × $1.536\u002Fhr × 24 hr × 30 days = $9,953.28",[1010,1495,1496],{},"S3 Write Requests: 1,350 r\u002Fs × $0.005\u002F1,000 r × 3,600 s × 24 hr × 30 days = $17,496",[1010,1498,1499],{},"S3 Read Requests: 1,350 r\u002Fs × $0.0004\u002F1,000 r × 3,600 s × 24 hr × 30 days = $1,400",[1010,1501,1502],{},"S3 Storage Costs: 5 GB\u002Fs × $0.021\u002FGB × 3,600 s × 24 hr × 7 days = $63,504",[1010,1504,1505],{},"Vendor Cost: 200 ETU × $0.50\u002Fhr × 24 hr × 30 days = $72,000",[1486,1507,1509],{"id":1508},"warpstream","WarpStream",[1007,1511,1512,1515],{},[1010,1513,1514],{},"Based on WarpStream’s pricing calculator (as of January 29, 2025), we assume a 4:1 client data compression ratio, meaning 20 GB\u002Fs of uncompressed data translates to 5 GB\u002Fs of compressed data.",[1010,1516,1517,1518,1523],{},"It's important to note that WarpStream’s pricing structure has fluctuated frequently throughout January. We observed the cost reported by their calculator changing from $409,644 per month to $337,068 per month. This variability has been previously highlighted in the blog post “",[54,1519,1522],{"href":1520,"rel":1521},"https:\u002F\u002Fbigdata.2minutestreaming.com\u002Fp\u002Fthe-brutal-truth-about-apache-kafka-cost-calculators",[263],"The Brutal Truth About Kafka Cost Calculators","”. To ensure transparency, we have documented the pricing as of January 29, 2025.",[47,1525,1526],{},[1019,1527],{"alt":17,"src":1528},"\u002Fimgs\u002Fblogs\u002F679c602e42713e0028e9af5e_AD_4nXcu5_VWTLu9jRYs6zX1MBAOtLQEo5gyfNSWPcbpnQHXTa8qNCFAXezRR2E8daygzYTTwd4dhJjaLaLM8C6y_3OGbu2NS7pdvEv3a8-ptNKOg7AeKnYqPQCAYvQ5EuxzuI3JYIvY.png",[1486,1530,1532],{"id":1531},"msk","MSK",[1007,1534,1535,1538,1541],{},[1010,1536,1537],{},"EC2 (Server): 15 * $3.264\u002Fhr × 24 hr × 30 days = $35,251",[1010,1539,1540],{},"Interzone Traffic (Client-Server): 5 GB\u002Fs × ⅔ × $0.02\u002FGB (in+out) × 3,600 s × 24 hr × 30 days = $172,800",[1010,1542,1543],{},"Storage: 5 GB\u002Fs × $0.1\u002FGB-month × 3,600 s × 24 hr × 7 days * 3 replicas = $907,200",[1486,1545,1399],{"id":1546},"redpanda-1",[1007,1548,1549,1552,1554,1557,1560],{},[1010,1550,1551],{},"EC2 (Server): 9 × $1.536\u002Fhr × 24 hr × 30 days = $9953",[1010,1553,1540],{},[1010,1555,1556],{},"Interzone Traffic (Replication): 5 GB\u002Fs × 2 × $0.02\u002FGB (in+out) × 3,600 s × 24 hr × 30 days = $518,400",[1010,1558,1559],{},"Storage: 5 GB\u002Fs × $0.045\u002FGB-month(st1) × 3,600 s × 24 hr × 7 days * 3 replicas = $408,240",[1010,1561,1562],{},"Vendor Cost: $93,333 per month (based on limited information. See additional notes below).",[1486,1564,1566],{"id":1565},"additional-notes","Additional Notes",[1007,1568,1569],{},[1010,1570,1571,1572,1577],{},"Redpanda does not publicly disclose its BYOC pricing, making it difficult to accurately assess its total costs. We refer to information from the whitepaper “",[54,1573,1576],{"href":1574,"rel":1575},"https:\u002F\u002Fwww.redpanda.com\u002Fresources\u002Fredpanda-vs-confluent-performance-tco-benchmark-report#form",[263],"Redpanda vs. Confluent: A Performance and TCO Benchmark Report by McKnight Consulting Group.","” for estimation purposes. Based on the Tier-8 pricing model in the whitepaper,  the estimated cost to support a 5GB\u002Fs workload would be $1.12 million per year ($93,333 per month). However, since this calculation is based on an estimation, we will revisit and refine the cost assessment once Redpanda publishes its BYOC pricing.",[47,1579,1580],{},[1019,1581],{"alt":17,"src":1582},"\u002Fimgs\u002Fblogs\u002F679c602dc8a9859eed89a0ef_AD_4nXdbcO8vsNNPy4GtkNLlmNKf22fjxRvzLzH7CtOna1L08sTbvnZx3HhufeFqc1w4K2gEF7lxO2IR5supotxebAiGnA07Qa8Yr3Rd1pVK2LYKK4WurlJGwgdwwucZIFoF-N_2oBjY.png",[47,1584,1585],{},[1019,1586],{"alt":17,"src":1587},"\u002Fimgs\u002Fblogs\u002F679c602d6bc1c2287e012540_AD_4nXfcHZnLfjbjIr3ZAgoQXT9dwP3aQCOQPmGZZJUtpNZSwE6qY6M3yehIaBxCwxEIeu5PVdUPY0zhyjnow26YfgjdYgSG4GnV9ibxu0YWTIpwng6z_F6FUGJMpERMKtpsFESzXSN_Sw.png",[1007,1589,1590,1593],{},[1010,1591,1592],{},"When estimating the storage costs for Kafka and Redpanda, we assume the use of HDD storage at $0.045\u002FGB, based on the premise that both systems can fully utilize disk bandwidth without incurring the higher costs associated with GP2 or GP3 volumes. However, in practice, many users opt for GP2 or GP3, significantly increasing the total storage cost for Kafka and Redpanda.",[1010,1594,1595],{},"Unlike disk-based solutions, S3 storage does not require capacity preallocation—Ursa only incurs costs for the actual data stored. This contrasts with Kafka and Redpanda, where preallocating storage can drive up expenses. As a result, the real-world storage costs for Kafka and Redpanda are often 50% higher than the estimates above.",[39,1597,1599],{"id":1598},"conclusion","Conclusion",[47,1601,1602],{},"Ursa represents a transformative shift in streaming data infrastructure, offering cost efficiency, scalability, and flexibility without compromising durability or reliability. By leveraging a leaderless architecture and eliminating inter-zone data replication, Ursa reduces total cost of ownership by over 90% compared to traditional leader-based streaming engines like Kafka and Redpanda. Its direct integration with cloud storage and scalable metadata & index management via Oxia ensure high availability and simplified infrastructure management.",[31,1604,1606],{"id":1605},"balancing-latency-and-cost","Balancing Latency and Cost",[47,1608,1609,1613],{},[54,1610,1612],{"href":1611},"\u002Fblog\u002Fcap-theorem-for-data-streaming","Ursa trades off slightly higher latency for ultra low cost",", making it an ideal choice for the majority of streaming workloads, especially those that prioritize throughput and cost savings over ultra-low latency. Meanwhile, StreamNative’s BookKeeper-based engine remains the preferred solution for real-time, latency-sensitive applications. By combining these two approaches, StreamNative empowers customers with the flexibility to choose the right engine for their specific needs—whether it's maximizing cost savings or achieving ultra low-latency real-time performance.",[31,1615,1617],{"id":1616},"the-future-of-streaming-infrastructure","The Future of Streaming Infrastructure",[47,1619,1620],{},"In an era where data fuels AI, analytics, and real-time decision-making, managing infrastructure costs is critical to sustaining innovation. Ursa is not just a cost-cutting alternative—it is a forward-thinking, lakehouse-native platform that redefines how modern data streaming infrastructure should be built and operated.",[47,1622,1623,1624,1629],{},"Whether your priority is reducing costs, improving flexibility, or ingesting massive data into lakehouses, Ursa delivers a future-proof solution for the evolving demands of real-time data streaming. ",[54,1625,1628],{"href":1626,"rel":1627},"https:\u002F\u002Fconsole.streamnative.cloud\u002F",[263],"Get started"," with StreamNative Ursa today!",[1631,1632,1634],"h1",{"id":1633},"references","References",[47,1636,1637,1640,1641],{},[1638,1639,1098],"span",{}," ",[54,1642,1643],{"href":1643},"\u002Fblog\u002Fintroducing-oxia-scalable-metadata-and-coordination",[47,1645,1646,1640,1648],{},[1638,1647,1047],{},[54,1649,1046],{"href":1046},[47,1651,1652,1640,1655],{},[1638,1653,1654],{},"StreamNative pricing",[54,1656,617],{"href":617,"rel":1657},[263],[47,1659,1660,1640,1663],{},[1638,1661,1662],{},"WarpStream pricing",[54,1664,1665],{"href":1665,"rel":1666},"https:\u002F\u002Fwww.warpstream.com\u002Fpricing#pricingfaqs",[263],[47,1668,1669,1640,1672],{},[1638,1670,1671],{},"AWS S3 pricing",[54,1673,1674],{"href":1674,"rel":1675},"https:\u002F\u002Faws.amazon.com\u002Fs3\u002Fpricing\u002F",[263],[47,1677,1678,1640,1681],{},[1638,1679,1680],{},"AWS EBS pricing",[54,1682,1683],{"href":1683,"rel":1684},"https:\u002F\u002Faws.amazon.com\u002Febs\u002Fpricing\u002F",[263],[47,1686,1687,1640,1690],{},[1638,1688,1689],{},"AWS MSK pricing",[54,1691,1692],{"href":1692,"rel":1693},"https:\u002F\u002Faws.amazon.com\u002Fmsk\u002Fpricing\u002F",[263],[47,1695,1696,1640,1699],{},[1638,1697,1698],{},"The Brutal Truth about Kafka Cost Calculators",[54,1700,1520],{"href":1520,"rel":1701},[263],[47,1703,1704,1640,1707],{},[1638,1705,1706],{},"Redpanda vs. Confluent: A Performance and TCO Benchmark Report by McKnight Consulting Group",[54,1708,1574],{"href":1574,"rel":1709},[263],{"title":17,"searchDepth":18,"depth":18,"links":1711},[1712,1713,1714,1719,1723,1724,1733,1736],{"id":1001,"depth":18,"text":1002},{"id":1040,"depth":18,"text":1041},{"id":1065,"depth":18,"text":1066,"children":1715},[1716,1717,1718],{"id":1077,"depth":278,"text":1078},{"id":1102,"depth":278,"text":1103},{"id":1123,"depth":278,"text":1124},{"id":1147,"depth":18,"text":1148,"children":1720},[1721,1722],{"id":1151,"depth":278,"text":1152},{"id":1166,"depth":278,"text":1167},{"id":1207,"depth":18,"text":1208},{"id":1219,"depth":18,"text":1220,"children":1725},[1726,1727,1728,1729,1730,1731,1732],{"id":1226,"depth":278,"text":1227},{"id":1272,"depth":278,"text":1273},{"id":1290,"depth":278,"text":1291},{"id":1337,"depth":278,"text":1338},{"id":1365,"depth":278,"text":1366},{"id":1383,"depth":278,"text":1384},{"id":1398,"depth":278,"text":1399},{"id":1443,"depth":18,"text":1444,"children":1734},[1735],{"id":1483,"depth":278,"text":1484},{"id":1598,"depth":18,"text":1599,"children":1737},[1738,1739],{"id":1605,"depth":278,"text":1606},{"id":1616,"depth":278,"text":1617},"StreamNative Cloud","2025-01-31","Discover how Ursa achieves 5GB\u002Fs Kafka workloads at just 5% of the cost of traditional streaming engines like Redpanda and AWS MSK. See our benchmark results comparing infrastructure costs, total cost of ownership (TCO), and performance across leading Kafka vendors.","\u002Fimgs\u002Fblogs\u002F679c6593d25099b1cdcec4ca_image-31.png",{},"\u002Fblog\u002Fhow-we-run-a-5-gb-s-kafka-workload-for-just-50-per-hour","30 min",{"title":976,"description":1742},"blog\u002Fhow-we-run-a-5-gb-s-kafka-workload-for-just-50-per-hour",[1750,1751,301],"TCO","Apache Kafka","A0o_2xdJiLI6rf6xj4RKsxJNo_A6QN2fYzCp6gaLrFw",1775235673800]