Release Plans and Pricing

From startups to large enterprises, there’s a Release plan that’s right for your organization. From dev and test to production and distribution, environments as a service improve the speed and quality of your development processes

Release has Environments-as-a-Service offerings that work across the application lifecycle

Pre-Production Environments

1-10 components *
$0.42 /hour per environment
11-50 components *
$0.69 /hour per environment
51+ components *

Production Environments

1-10 components *
$0.69 /hour per environment
11-50 components *
$1.04 /hour per environment
51+ components *

Includes

  • Full-stack Ephemeral Environments including Feature Branch Environments, Preview Environments
  • Cost control features (auto shutdown, timeout, pausing)
  • Custom resource and service footprint support
  • Always-on, Production Ready Staging Environments
  • Remote Development Environments: Full stack, isolated development environment in your cloud account
And More

Includes

  • Rainbow deployments
  • Uptime SLA's
  • Release secondary monitory
  • Dedicated Production Cloud account support
  • Dedicated Production Cluster support
  • Manual deployments
  • Automatic deployments from tracking branch
  • Custom domains
And More
*
A “Component” is defined as components managed by Release into a Kubernetes namespace or deployment job managed by Release. These include deployed Docker containers and jobs (but not replicas), frontend static javascript applications, or deployed infrastructure from an IaC tool (Terraform, Pulumi, etc.). See Pricing FAQ for more about what constitutes a service and additional details. All pricing is in US Dollars

Pre-Production Environments

1-10 components *
$0.42 /hour per environment
11-50 components *
$0.69 /hour per environment
51+ components *

Includes

  • Full-stack Ephemeral Environments including Feature Branch Environments, Preview Environments
  • Cost control features (auto shutdown, timeout, pausing)
  • Custom resource and service footprint support
  • Always-on, Production Ready Staging Environments
  • Remote Development Environments: Full stack, isolated development environment in your cloud account
And MoreAnd more

Production Environments

1-10 components *
$0.69 /hour per environment
11-50 components *
$1.04 /hour per environment
51+ components *

Includes

  • Rainbow deployments
  • Uptime SLA's
  • Release secondary monitory
  • Dedicated Production Cloud account support
  • Dedicated Production Cluster support
  • Manual deployments
  • Automatic deployments from tracking branch
  • Custom domains
And MoreAnd more
*
A “Component” is defined as components managed by Release into a Kubernetes namespace or deployment job managed by Release. These include deployed Docker containers and jobs (but not replicas), frontend static javascript applications, or deployed infrastructure from an IaC tool (Terraform, Pulumi, etc.). See Pricing FAQ for more about what constitutes a service and additional details. All pricing is in US Dollars

Pre-Production Release Features

Pre-Production
Production
Ephemeral Environments/Feature Branch Environments/Preview Environments/Review Apps
Full stack, isolated environment per feature branch
Advance rules on environment lifecycle
Cost control features
Auto shutdown, timeout, pausing
Create from API
Create from Button Click
Create from a PR
Create from a label in a PR
Dynamic hostnames per environment
Custom resource and service footprint support
Staging Environments
Permanent always on, production replica environment
Auto deployments or manual deployments on mainline branch(es)
Custom resource and service footprint support
Rainbow deploys
Remote Development Environments
Full stack, isolated development environment in your cloud account
Write code directly in your cloud env
Terminal into containers
Logging
Bring your own IDE
Port forwarding
SSH access
File syncing

Production Release Features

Pre-Production
Production
Production Environments
Rainbow deployments
Uptime SLA's
Release secondary monitory
Dedicated Production Cloud account support
Dedicated Production Cluster support
Manual deployments
Automatic deployments from tracking brtanch
Custom domains

Pre-Production Release Features

Ephemeral Environments/Feature Branch Environments/Preview Environments/Review Apps
Full stack, isolated environment per feature branch
Pre-Production
Production
Advance rules on environment lifecycle
Pre-Production
Production
Cost control features
Auto shutdown, timeout, pausing
Pre-Production
Production
Create from API
Pre-Production
Production
Create from Button Click
Pre-Production
Production
Create from a PR
Pre-Production
Production
Create from a label in a PR
Pre-Production
Production
Dynamic hostnames per environment
Pre-Production
Production
Custom resource and service footprint support
Pre-Production
Production
Staging Environments
Permanent always on, production replica environment
Pre-Production
Production
Auto deployments or manual deployments on mainline branch(es)
Pre-Production
Production
Custom resource and service footprint support
Pre-Production
Production
Rainbow deploys
Pre-Production
Production
Remote Development Environments
Full stack, isolated development environment in your cloud account
Pre-Production
Production
Write code directly in your cloud env
Pre-Production
Production
Terminal into containers
Pre-Production
Production
Logging
Pre-Production
Production
Bring your own IDE
Pre-Production
Production
Port forwarding
Pre-Production
Production
SSH access
Pre-Production
Production
File syncing
Pre-Production
Production

Production Release Features

Production Environments
Rainbow deployments
Pre-Production
Production
Uptime SLA's
Pre-Production
Production
Release secondary monitory
Pre-Production
Production
Dedicated Production Cloud account support
Pre-Production
Production
Dedicated Production Cluster support
Pre-Production
Production
Manual deployments
Pre-Production
Production
Automatic deployments from tracking brtanch
Pre-Production
Production
Custom domains
Pre-Production
Production

All environments are built on the proven Release platform, including

Core Features

Expand table to see more details.
Expand All
Pre-Production
Production
What can run in an environment?
Containers
Static Javsacript Frontends
Cloud native services created with IaC
Lambdas, CloudFunctions, RDS, CloudSQL, Kenesis, ElasticCache, S3, CloudStorage, WASM, VMs, ECS, EC2 etc...
Monolithic app support
Microservice app support
Environment Definition/Configuration Support
Package.json for static javascript sites
Docker-compose
Helm
Terraform
Custom YAML
Release Environment Templating
Config map
Mount a file not in source control
Per service resource allocation
Cloud support
AWS
GCP
Source control integrations
Github Integration
Gitlab Integration
Bitbucket Integration
Container builds
Release builds your images
Hosted
Release builds your images
Dedicated builders in your cloud account
Bring your own images
Build arguments
Build SSH Keys
Environment variables and secrets
Secrets management
Environment variable management
AWS Parameter Store
Google Secrets Manager
AWS Secrets Manager
Environment Access
Container Logging, Terminal
Direct k8s access
Kubeconfig
ECS Logging, Terminal
Environment auth
Networking
Public ingress
Private ingress
Public CDN
VPN to environments
Bastion Access
User management
SSO
Hosted
RBAC
Deployment strategies
Rolling deploys
Custom environment workflows
Rollbacks
Environment creation task automation via jobs
Environment Management Tools
Release CLI
Environment Handles
GitOps
Data Management
Databases can come up with scrubbed data or database clones with Instant Datasets
Refresh environment to known dataset
Container databases
Connect to SaaS databases
Kubernetes support (if containers running in Release managed EKS or GKE)
Cluster creation
Node group management
Patch node groups
Cluster upgrades
Integrations into third party tools
Slack integration
DataDog
Private registries
Artifactory
DockerHub private registries
LaunchDarkly

Core Features

Expand table to see more details.
Expand All
What can run in an environment?
Containers
Pre-Production
Production
Static Javsacript Frontends
Pre-Production
Production
Cloud native services created with IaC
Lambdas, CloudFunctions, RDS, CloudSQL, Kenesis, ElasticCache, S3, CloudStorage, WASM, VMs, ECS, EC2 etc...
Pre-Production
Production
Monolithic app support
Pre-Production
Production
Microservice app support
Pre-Production
Production
Environment Definition/Configuration Support
Package.json for static javascript sites
Pre-Production
Production
Docker-compose
Pre-Production
Production
Helm
Pre-Production
Production
Terraform
Pre-Production
Production
Custom YAML
Pre-Production
Production
Release Environment Templating
Pre-Production
Production
Config map
Mount a file not in source control
Pre-Production
Production
Per service resource allocation
Pre-Production
Production
Cloud support
AWS
Pre-Production
Production
GCP
Pre-Production
Production
Source control integrations
Github Integration
Pre-Production
Production
Gitlab Integration
Pre-Production
Production
Bitbucket Integration
Pre-Production
Production
Container builds
Release builds your images
Hosted
Pre-Production
Production
Release builds your images
Dedicated builders in your cloud account
Pre-Production
Production
Bring your own images
Pre-Production
Production
Build arguments
Pre-Production
Production
Build SSH Keys
Pre-Production
Production
Environment variables and secrets
Secrets management
Pre-Production
Production
Environment variable management
Pre-Production
Production
AWS Parameter Store
Pre-Production
Production
Google Secrets Manager
Pre-Production
Production
AWS Secrets Manager
Pre-Production
Production
Environment Access
Container Logging, Terminal
Pre-Production
Production
Direct k8s access
Kubeconfig
Pre-Production
Production
ECS Logging, Terminal
Pre-Production
Production
Environment auth
Pre-Production
Production
Networking
Public ingress
Pre-Production
Production
Private ingress
Pre-Production
Production
Public CDN
Pre-Production
Production
VPN to environments
Pre-Production
Production
Bastion Access
Pre-Production
Production
User management
SSO
Hosted
Pre-Production
Production
RBAC
Pre-Production
Production
Deployment strategies
Rolling deploys
Pre-Production
Production
Custom environment workflows
Pre-Production
Production
Rollbacks
Pre-Production
Production
Environment creation task automation via jobs
Pre-Production
Production
Environment Management Tools
Release CLI
Pre-Production
Production
Environment Handles
Pre-Production
Production
GitOps
Pre-Production
Production
Data Management
Databases can come up with scrubbed data or database clones with Instant Datasets
Pre-Production
Production
Refresh environment to known dataset
Pre-Production
Production
Container databases
Pre-Production
Production
Connect to SaaS databases
Pre-Production
Production
Kubernetes support (if containers running in Release managed EKS or GKE)
Cluster creation
Pre-Production
Production
Node group management
Pre-Production
Production
Patch node groups
Pre-Production
Production
Cluster upgrades
Pre-Production
Production
Integrations into third party tools
Slack integration
Pre-Production
Production
DataDog
Pre-Production
Production
Private registries
Pre-Production
Production
Artifactory
Pre-Production
Production
DockerHub private registries
Pre-Production
Production
LaunchDarkly
Pre-Production
Production

Support

Core support

Is included for all Release customers. This includes email support, 1-day incident response SLA, and customer support forum access

Upgraded support

Is available for $500/mo or 10% of your bill. This includes dedicated account management, a 4-hour SLA (Monday-Friday), a dedicated, private Slack channel, and phone support.

Custom Support

Solutions are available to meet the unique needs of your application development team. Our experts can help build custom integrations, onboarding and implementation assistance, team training, and more. Contact sales for more information.

Other Release Offerings

Software Vendor Distribution Services

Many ISVs use Release to automate the distribution and update of their software to their customers. Our VPC-based solution lets you install your software on customer machines and update/manage as needed without disruption. Contact one of our sales specialists to see how we can help you delight your customers and improve your bottom line with Release.

Free Release for Open Source Software Projects

Release is a strong advocate of Open Source Software projects. Release provides free use of our environments as a service offering to qualified OSS projects free of charge. Contact us for more information and to start using Release to automate the creation of development and evaluation environments to improve the delivery of project updates.

Release Pricing FAQ

What is Release’s pricing?

Release offers offer on-demand monthly pricing for pre-production 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.

Are there any other fees? 

Upgraded support is available for $500 or 5% of your total spend (whichever is higher).  For example, if you spend $10000 in March, support is $500 for March. If you spend $6000 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.

Do I pay anything upfront? 

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

What is the definition of a component? 

A component is defined as any application component that Release has deployed and manages within a namespace/environment.
Examples of components include:
  • Docker containers
  • Containers running in a Release namespace/environment
  • Front-end static JavaScript sites
  • Cloud native services deployed by IaC (Terraform, Pulumi, AWS CDK or others. Types of these include: llamdas, ECS containers, RDS databases, etc..)
  • Jobs that run within deployment workflows
  • Cron tasks that run regularly 
  • Release Instant Dataset instances
For example let’s say you have:
  • 5 containers deployed via a Helm chart
  • 1 Static Javascript frontend site
  • 3 containers deployed directly into a K8s cluster defined in your Release Application template
  • 1 Release Instant Dataset (an RDS instance)
  • 3 lamdas created with Terraform 
  • 1 Kenesis instance created with Terraform 
  • 1 ElasticCache instance created with Terraform
  • 2 jobs that setup and configure your Environment (runs database migrations and seeding) 
This would equal 18 components deployed into an environment and managed by Release.

Are all environment types priced the same? 

All pre-production 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.

Is there any limit to the number of users or any charge for additional users? 

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.

When will the usage meter begin? 

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. 

So I have to pay to evaluate Release or do a POC?

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. 

Do I have to sign a contract?

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.

My legal and procurement teams require a written contract to proceed. Can you provide one?

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).

How can I estimate my team’s usage and understand what this might cost me?

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: 
  • Number of developers
  • Number of components in ephemeral environments
  • Number of PRs/dev/month
  • Average time a PR is open (hours)
  • Percentage of PRs that need an env
  • Number of components in dev environments
  • Number of hours devs writing code/week
  • Number of components in staging environments
  • Number of staging environments
  • Hours per week staging environment running
  • Number of components in production environments

Is there an opportunity for discounts?

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. 

What if my environment only runs for 10 minutes?

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. 

What controls do I have to ensure my costs don’t run up unexpectedly?

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.

Release Your Ideas

Start today, or contact us with any questions.