Pricing

3 steps to data warehouse that just works

Choose your product edition
Decide the level of enterprise integration and support that fits the role of your data platform. Choose between three options: Standard, Enterprise, Business critical.
Select your runtime environments
Choose how many runtime environments suit your development lifecycle and practices. For example Development, Testing, Production or any other combinations.
Pick your runtime size
T-shirt sizing model. From Small to XX-Large, based on your data processing concurrency needs. You can scale up and down based on your current data warehouse lifecycle situation.

FAQ

Standard edition includes all core features you need for developing and operating a cloud data warehouse. Enterprise edition adds the option for single sign-on with federated AD, external API connectivity and push notifications. Business critical introduces private link/VPN connectivity, tailored version upgrades and premium support.

Contact us for more details.
Runtime sizing enables scaling of your data processing capacity with a simple and familiar t-shirt sizing model. From small (max 2 concurrent loads) until XX-Large (max 40 concurrent loads). Default sizing is M (5 concurrent loads).
Yes, you can have different concurrency sizing in each of your runtime environments. Typically in production there is a need to have higher concurrency if there are higher service level requirements.
There is no direct pricing effect based on the amount of users in your team. So if your data team grows, your monthly subscription fee is not growing.
There is no automatic pricing effect from growing data volumes. Runtime sizing enables you to adjust the service level of your data platform, when data volume and scope of your platform are growing. But only based on your real business needs.