> For the complete documentation index, see [llms.txt](https://docs.release.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.release.com/getting-started/create-application.md).

# Create an application

Learn how to create an application in Release

You can create unlimited applications on Release.

{% hint style="info" %}
**Note:** Free accounts are limited to two environments at a time. If you're on a free account and already have two environments, you'll need to delete one before proceeding with this guide. To create more than two environments, [upgrade your account](https://releasehub.com/pricing).
{% endhint %}

To create an application, first log in to your Release account.

On the bottom-right card, click the **create new app** button.

![](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-33db2a409071288e8018aaf672ca82a033eac15e%2Fcreate-app.png?alt=media)

1. **Create a custom application:** If your application doesn't fit into one of the provided templates or if you prefer to start from scratch, you can create a custom application. This option gives you the most flexibility, but requires you to configure your application manually.

   When creating an application in Release, you have two options:
2. **Create from a template:** Release provides a variety of pre-configured templates for common types of applications. These templates include the necessary configuration and code to get started quickly.

   \## Servers and runnables

There are two types of applications you can create in Release:

![](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-31fc77c242205e239fcd07cbaaef0a5dd6921564%2Frunnable-and-server.png?alt=media)

1. **Servers:** Servers are applications that provide services over the network. They are continuously running and waiting for requests to process. Examples include web servers, database servers, and application servers. You can also create multiple environments for a given server application, for example, a development environment and a production environment.
2. **Runnables:** Runnables are applications that perform a specific task, run to completion, and then terminate. Examples include scripts, batch jobs, and fine-tuning AI models. You can only create one environment for a given runnable application.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Learn more:</strong> To learn more about the differences between servers and runnables, read <a href="/getting-started/create-application/servers-vs-runnables.md">Servers vs. Runnables</a>.</p></div>

When creating an application, you'll need to specify the type of application you're creating. This helps Release understand how to handle and manage your application.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.release.com/getting-started/create-application.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
