StreamNative is a leading provider of real-time streaming data solutions, specializing in Apache Pulsar, an open-source distributed messaging and streaming platform. Founded by core developers of Apache Pulsar, StreamNative offers a comprehensive suite of products and services that help organizations harness the power of data streams for scalable, low-latency data processing. StreamNative Cloud, the company flagship product, provides a fully managed Pulsar service, enabling businesses to deploy, monitor, and scale streaming applications across any cloud environment. With a focus on flexibility, reliability, and seamless integration, StreamNative also supports Kafka compatibility through its Kafka On StreamNative (KSN) offering, allowing enterprises to bridge the gap between Pulsar and Kafka ecosystems. StreamNative platform powers diverse use cases, from real-time analytics and machine learning pipelines to log management and event-driven architectures. Notably, StreamNative integrates with various AWS services to enable seamless data streaming and processing in the cloud. For example, StreamNative connectors facilitate data ingestion into Amazon S3 for scalable storage, while integration with Amazon Kinesis and AWS Lambda supports real-time analytics and event-driven applications. Additionally, StreamNative Lakehouse Storage support integrates out of the box with AWS S3, enabling users to offload data in both Apache Iceberg and Delta Lake formats for real-time analytics, advanced querying, and compatibility with modern data lake architectures. StreamNative also supports UniLink, a powerful tool that leverages AWS S3 to efficiently replicate data between clusters, ensuring high availability and disaster recovery. By offering tools like the S3 Sink Connector, Pulsar Functions, and managed Pulsar clusters on AWS, StreamNative enables developers to build scalable, efficient, and future-proof data applications across industries such as finance, retail, and IoT.
Enjoy the low latency, high durability, and long-term data retention provided by Apache Pulsar, along with seamless Kafka compatibility, without the operational overhead, using cost-effective, enterprise-ready clusters.
Support both messaging and streaming use cases in your architecture. Build event-driven applications and gain value from your data in real time with features like Pulsar Functions. A rich client library ecosystem includes support C/C++, Python Java, GO, JavaScript, Rust, and more
Confidently implement data streaming with a managed service backed by the original creators of Apache Pulsar. Clusters are always on the latest stable Pulsar version with enterprise-grade SLAs, on-demand bug fixes, and technical support
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
Pricing is based on the duration and terms of your contract with the vendor, and additional usage. You pay upfront or in installments according to your contract terms with the vendor. This entitles you to a specified quantity of use for the contract duration. Usage-based pricing is in effect for overages or additional usage not covered in the contract. These charges are applied on top of the contract price. If you choose not to renew or replace your contract before the contract end date, access to your entitlements will expire.
Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator to estimate your infrastructure costs.
This listing uses an annual contract with two pricing dimensions. The first bills for consumption of resources like computing, storage, and network. The second is a commitment you make on usage of the managed Apache Pulsar service. You commit to a usage level for the year, then draw down against it as you consume resources. Billing accrues based on actual usage of compute, storage, and network. The commitment dimension sets your prepaid quantity, while the consumption dimension tracks what you use across those resource types.
Top-of-mind questions for buyers
What counts as a resource unit for the consumption dimension?
Consumption covers compute, storage, and network usage. Compute and storage are measured as units of 2 vCPU and 8 GB RAM for stateful and stateless components, billed hourly. Throughput-based usage is measured in Elastic Throughput Units, billed by the highest of ingress, egress, or data-entries each hour.
What happens if my usage goes beyond the committed amount?
The architecture scales automatically to handle throughput past your baseline, and you pay for the extra resources you actually use. There are no hard cutoffs that drop messages. Consumption beyond your commitment is billed under the resource consumption dimension.
How do the commitment and consumption dimensions combine on my bill?
The commitment dimension sets your prepaid usage level for the year. The consumption dimension meters actual compute, storage, and network use, which draws down against your commitment. Usage accrues hourly. Once you pass the committed amount, extra consumption is billed on top.
Tell us how we can improve this page, or report an issue with this product.
Give us feedbackReport a problem with this product or seller
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA).
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.