Quickstart
Last updated
Was this helpful?
Last updated
Was this helpful?
Here's a step-by-step guide to adopting Release in your organization. Start with the Release Cloud Sandbox
Create a Release account.
Play around with the Release Sandbox
Choose a Starter Repo or Custom Application
Release Enterprise Quick Start
Integrate your cloud provider.
Link a domain.
Create a cluster.
Connect your source control provider.
Create your application.
Visit and sign up using your email address or a single sign-on provider.
Take a look at our documentation if you need more information about this step.
When you first signup for Release you are in the Release Cloud and using a Sandbox account which includes 5 free hours of environment time. This is to help you get a feel for the features in Release.
There are two ways to try Release. If you just want to see how Release works, start with one of our Starter Repos. The Starter Repos have been setup ahead of time to work out of the box with Release. You just fork the repo and follow the guided setup. This generally takes a few minutes and is the easiest way to get familiar with Release. You can also start with a Custom Application. When you go down this path, you bring code from your own code repositories (Github, Bitbucket or Gitlab). If you just want to see the features in Release, start with a Starter Repo. If you want to bring up your own applications start with Custom Application. We recommend starting with a Starter Repo. You can always bring your own code at anytime once you are familiar with Release.
Once your 5 free hours has expired you can upgrade to our paid Release Cloud plan which runs on our infrastructure in the Release Cloud or upgrade to Enterprise which allows you to run your environments in your cloud account.
If you're on the Release Enterprise paid plan, integrate Release with your cloud provider.
In Account Settings, navigate to Clusters, and press Create new cloud provider integration. Currently, we support AWS and GCP.
When prompted to log in to your cloud provider, you should use an account with enough privileges to create and destroy clusters, manage permissions, manage DNS settings, and other provider-specific functionality that Release will need to function.
Take a look at the following docs for more help with integrating your cloud provider:
If you don't already have a domain, you should register one through your cloud provider (for example, Route53 if you're using AWS).
To link your domain to Release, go to Settings -> Domains -> Create new domain.
Enter your domain and take note of the nameservers that Release will display. If you're using a third-party domain provider, configure your domain to point to these name servers.
Finally, verify your domain by pressing the Verify button.
Once you have a linked and verified domain, you can create your first cluster. Navigate to Settings -> Clusters and choose Create new cluster under your cloud provider.
Release will pull code from your source control provider (such as GitHub, GitLab, or Bitbucket) to deploy your application.
To get started, click on your profile picture in Release, then on Manage Profile.
You can connect GitHub, Bitbucket, or GitLab.
If you're connecting GitHub, you'll be given the option to grant Release access to all of your repositories or only specific repositories.
Once you've created the connection, you'll be able to view your repositories when creating a new app from Release and select the one that you want to deploy using Release.
Select an example application and fork it to your integrated source control account. Then press Create new app from your Release dashboard and choose the repository you forked.
Now you can configure and monitor your applications through your Release dashboard. If necessary, you can still access your AWS account and Kubernetes cluster directly, but for most use cases, you can enjoy our simplified controls and sensible defaults.
To get the most out of Release, you should:
You can also use a domain registered through a third-party provider such as GoDaddy (follow our guide), but it's easier if you use your cloud provider directly.
For more help with this, see .
You may have integrated a source provider account when you signed up for Release using SSO, but you can further to give Release access to the correct repositories and edit other settings, like whether Release automatically comments on your pull requests.
To test that everything works, you can deploy one of our .
Prepare your applications for use with Release. See .
Understand the that lets you configure most aspects of Release.
Read our to understand the details of how Release works.
