Release Plans and Pricing

Release offers offer on-demand monthly pricing for development and production application management as shown in the table above. Release uses consumption-based pricing based on how many hours your app is running, the number of components in the application, and bills on an hourly basis. Release offers substantial discounts (upwards of 40%) for annual and multi-year contracts compared to “on-demand.” Contact Sales for more information.

Upgraded support is available for $500 or 10% of your total spend (whichever is higher).  For example, if you spend $10,000 in March, support is $1,000 for March. If you spend $4,000 in April, support is $500 for April. Upgraded support includes production-level SLAs, dedicated Slack channels for your company, and a named customer success manager.

No, there are no upfront costs. You are billed monthly on Net 30 invoicing terms.

A component is defined as any application component that Release has deployed and manages within a namespace/environment.

Examples of components include:

For example let’s say you have:

This would equal 18 components deployed into an environment and managed by Release.

All development environment types are priced the same, regardless of the use case (i.e. development versus staging versus QA). All production environments are priced the same. The only element that will make an environment more expensive than another environment are the number of components contained within the environment.

There is no cost per user. The pricing is based on environment runtime and number of components per environment only. There is no limit to the number of users.

Immediately. Prior to creating an account with Release, you can either set up credit card billing or invoicing (via an order form the sales team will provide). From there, any environment hour used will be billed at the list price rates. 

Yes. However, costs during evaluation and POC will be very minimal. Depending on the extent of the POC, usage is typically limited to a handful of total hours of environment runtime. 

No. Our billing system will collect your credit card information and you are enabled to use the product from there - no contract or signatures are required.

Yes, though when you create an account with Release, you agree to our standard terms of service. We can provide the terms of service in a PDF for your legal team’s review. If they would like a written agreement on the hourly pricing construct inclusive of the price point, we can provide an Order Form outlining the month-to-month terms. Additionally, to lock in a price point and to take advantage of significant discounts, you can proceed with our annual or multi-year contract (instead of monthly on-demand billing).

We have a simple calculator we use to help customers understand the estimated “on-demand” costs. If you can share the following inputs, we will provide you with an estimate: 

Yes. Monthly on-demand pricing is priced at a premium due to the month-to-month flexibility. We provide significant discounts for annual and multi-year agreements. The discounts are based on your total number of environments required and length of Release commitment. Contact Sales for more information about discount programs. 

You will be billed the hourly rate listed above based on the number of components in your application The lowest billing granularity is one hour. 

Governance and cost optimization are our top priorities. The following product features help our customers govern usage and manage costs: 

Auto expiration of environments: By default, any ephemeral environment created will be automatically spun down after x days of usage. You have the ability to modify this setting to any duration you’d like.

Cluster auto scaling: By default, clusters are set to auto-scale as you add and remove environments the Kubernetes cluster will scale accordingly.

Pausing Instant Datasets: Ephemeral environments are meant to be spun up and down and not live forever, which ultimately leads to cost savings. However, sometimes environments are needed for several days or weeks. During the in-between hours when the environment is not in use, you have the ability to pause the underlying database instances.