SET UP

How to set up a Runtime

To create a Runtime, you will need to create an Application, an Environment and a Runtime. If you have not created an Application and Environment, please see the guide “How to set up an Application“ and “How to set up an Environment” for more information.  

To create a Runtime, click on the menu on the upper left side, select “Pipelines” and click on the tab “Runtime.”


You may see an empty page if you have not created any Runtimes yet. Click on “Create.”


You see a list of Applications you created. Select the Application you would like to deploy.


By selecting an Application, the details of the Application appear including the repository, traffic type, Environment variables and scaling strategies. Make sure that your setup is correct. If you need to make any changes, you will need to go back to the menu “Pipelines” and select “Applicaiton” and update the application’s configuration. If the Application looks good, click on “Next” button at the bottom of the page. 


We are in the second step of creating a Runtime. Let’s select a branch. The branches are synched with the repo you have selected from your integration. Then, select a protocol for the health check of the Application. Currently, we offer TCP.  Then select an Environment where you would like to deploy the Application. If you want to create a new Environment here, you can click on “Set up an Environment” and type in the name of the Environment. You can use lowercase, numbers and dash, but spaces and special symbols are not allowed. Click on next.


The last step is to add custom tasks to your Pipelines. This is a collection of tasks that are executed before and after the deployment of the Application. This step is optional. If you don’t want to use custom pipelines you can opt out and just click on “Create” to create a Runtime.


If you would like to add tasks, click on “Custom Pipeline.” If you would like to run a task before deployment, add the task to “Before Deploy.” If the task needs to be executed after the deployment, add the task to “After Deploy.” These tasks get executed in the order you entered in this form. Once you add all the tasks, click on “Create.” It might take up to a few minutes for the Application to be deployed.


While the Runtime is created, you can see the logs on the right side of the page and the Runtime’s status is “Pending.”

When you create a Runtime, the platform automatically generates a CloudFlare Origin Certificate Authority (Origin CA) as well as a URL.

Once a Rumtime is created successfully, you can see the icon changes to “Running.”


Using the tabs, you are able to see Details, Metrics, Logs and Pipelines of the Runtime.

Incubated by

Members of

Hatchet Ventures 22 Cohort 1

Hatchet Ventures