WarpStream's BYOC deployment model gives you the security and true data sovereignty benefits of self hosting, but without any of the management hassle.
WarpStream's hybrid Bring Your Own Cloud (BYOC) deployment model provides the ease of use of a fully cloud hosted solution, but the cost profile, security, and data sovereignty of a self-hosted deployment.
BYOC clusters use your own compute, and your own object storage. Your data never leaves your environment.
Zero disks, zero fees, zero ops auto-scaling, and zero IAM access!
.svg)
.svg)
WarpStream supports Schema Validation via external schema registries and services like AWS Glue. It also has its own BYOC-native Schema Registry.
Like all Schema Registries, the WarpStream BYOC Schema Registry ensures data compatibility and compliance by validating schemas during data production and consumption. This helps minimize downstream data issues and enables schemas to evolve without breaking consumers.
In addition, it has unique features that are only possible with WarpStream’s stateless, zero-disk architecture, such as native integration with the WarpStream Agents, data retrieval via object storage with no intermediate disks, easy scaling, usage of zone-aware routing to avoid interzone networking fees, and no need to wait on “leaders” to be elected, as consensus is handled by WarpStream's metadata store, and Agents can read and write.
Learn more about WarpStream BYOC Schema Registry via our docs and announcement blog.
The WarpStream Agents have native support for AWS S3, GCP GCS and Azure Blob Storage built in, so they can run in all three of the major cloud providers, plus others like Oracle Cloud, Cloudflare, DigitalOcean, IBM Cloud, MinIO, Vultr and more. You can deploy in any cloud or region as long as you use an S3-compatible object store.
You can read more about object storage support in our documentation.
BYOC clusters are only charged for uncompressed writes, cluster-minutes, and storage. There are no network ingress or egress charges, and we don't bill for reads at all.
Normally, networking charges associated with running Kafka are accrued based on compressed network throughput. However, WarpStream charges for uncompressed data written because we want to offer predictable pricing, and we believe that your bill should not fluctuate based on which compression algorithm you choose to use in your client. This also aligns incentives so that we are encouraged to reduce your cloud infrastructure costs.
WarpStream has no per-Agent, per node, or per-vCPU charges, and does not charge extra for replication. That's because there is no local data to replicate. WarpStream has no per-partition charges. And unlike Kafka, there is no requirement to increase the number of WarpStream Agents when the number of partitions increases.
All pricing is transparent and you can learn more about it by visiting our pricing page.
Your data never leaves your account. WarpStream only ingests metadata, and WarpStream personnel have zero access to your data or the environment where you deploy the Agents. The metadata transferred to WarpStream cannot be used to access your data, and WarpStream is unable to take actions on your behalf.
To learn more about data isolation and the metadata transferred to WarpStream’s environment, see our documentation, or read our blog post that describes WarpStream’s Zero Access BYOC model in detail.
.svg)
.svg)
.svg)