> For the complete documentation index, see [llms.txt](https://help.form.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.form.io/deploy/trial-deployment-quick-start.md).

# Trial Deployment Quick Start

This guide will walk new users through the process of getting a trial environment of Form.io Enterprise deployed locally. It will guide users through the process of

* acquiring a license
* obtaining the tools required
* configuring the local environment
* deploying Form.io Enterprise

## Get A License

First, get the license required to use Enterprise Platform. If a license has already been issued, jump to the [next section](#get-docker).

Users can get a trial license by [scheduling a quick 30 minute call](https://form.io/try-formio-for-free/) or contacting [**support@form.io**](mailto:support@form.io) to request a license.

Once a license key has been provided, save it somewhere it will be easy to paste into the configuration files that will be downloaded later.

## Get Docker

Next, the local machine must have Docker installed. If Docker is already installed and you're familiar with using it, skip to the [next section](#get-docker-compose-files).

Form.io uses [Docker](https://www.docker.com/) Compose to define and run containers that deploy the Enterprise\
platform on a local machine. Users unfamiliar with Docker should refer to the [Get Docker](https://docs.docker.com/get-started/) section of the Docker Help.

Ensure Docker is installed and running before proceeding.

## Get Docker Compose Files

Docker Compose files are `.yaml` files that define a collection of Docker containers. A Compose file will describe each container, the resources allocated to it, and the network that connects them.

Open the [Form.io Deployment Examples](https://github.com/formio/deployment-examples/tree/develop/docker/quickstart) repo on GitHub and download the contents of the Quickstart directory to the local machine. It should contain the following:

* /volumes/caddy
* docker-compose.yml
* .env.example

## Prepare the .env file

Open the .env file in a text editor.

1. Enter the Enterprise license key provided by Form.io in spot marked **`LICENSE_KEY`**.
2. Make note of the default credentials. it is not necessary to change them for this local trial deployment.
3. Rename the file as `.env`

## Spin up the containers with Docker Compose

Open a terminal at the directory that contains the `docker-compose.yml` and `.env` files.\
Run the following command:

```
docker-compose up --detach
```

This starts the Form.io platform containers and the MongoDB database containers locally. The Docker Compose command automatically pulls the necessary values from the .env file.

## Authenticate into the Portal

From a browser, navigate to `http://localhost:3000`

Log in with the admin account. The default credentials are `admin@example.com` / `CHANGEME`. These are set in the `.env` file.

## Form.io Enterprise is Deployed

The Developer Portal should load. The [Portal Base project](broken://pages/xtP0BM0apt2QA3xvl3VQ), used for configuring and administering the Portal should be available by default.

<figure><img src="/files/jr09tTKB7crwoYA0rs40" alt="" width="375"><figcaption></figcaption></figure>

## Where To Go Next

To learn more about a typical Form.io deployment, begin with the [Deployment Overview](/deploy/deployment-overview.md)

To learn more about using the Form.io Platform, check out the [Getting Started](https://help.form.io/) guide or the [Form Building](https://help.form.io/form-building/).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.form.io/deploy/trial-deployment-quick-start.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.