> 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/dev/dev-license.md).

# Developer License

A local deployment license for the Form.io platform used for development and testing purposes.

## What is a Developer License?

The Form.io Developer License enables developers to spin up and down instances of the Form.io platform locally on the developer's machine allowing for local development and testing without affecting the remotely deployed platform configuration.

The local deployments must be connected to a local database. The developer license allows for local deployments of projects, stages, forms, and API/PDF servers.

‌The developer license is priced on a per-seat basis. Customers with a subscription for a remotely deployed configuration containing 3 or more API Server Environments are eligible to order a Developer License.

{% hint style="info" %}
Contact <sales@form.io> for more information on the Developer License
{% endhint %}

## Developer License Script

With a developer license, servers can be locally deployed and connected to a single local MongoDB. Please note you will not be able to use the "replicaSet" option for the connection or connect to any remote databases. All connections must be to a local database.

```
docker network create formio || true && \
mkdir ~/opt/mongodb || true && \
docker run -itd  \
  --name formio-mongo \
  --network formio \
  --volume ~/opt/mongodb:/data/db \
  --restart unless-stopped \
  mongo && \
docker run -d \
  -e "LICENSE_KEY=YOURLICENSE" \
  -e "MONGO=mongodb://localhost:27017/formio" \
  -e "PORTAL_ENABLED=true" \
  -e "ADMIN_EMAIL=admin@example.com" \
  -e "ADMIN_PASS=CHANGEME" \
  -e "DB_SECRET=CHANGEME" \
  -e "JWT_SECRET=CHANGEME" \
  -e "PDF_SERVER=http://pdf-server:4005" \
  --restart unless-stopped \
  --link pdf-server:pdf-server \
  --network formio \
  --name formio-server \
  -p 3000:80 \
  formio/formio-enterprise && \
mkdir ~/seaweedfs/data || true && \
mkdir ~/seaweedfs/config || true && \
docker run -itd \
  -e "AWS_ACCESS_KEY_ID=CHANGEME" \
  -e "AWS_SECRET_ACCESS_KEY=CHANGEME" \
  --network formio \
  --name formio-seaweedfs \
  --restart unless-stopped \
  -p 8333:8333 \
  -v ~/seaweedfs/data:/data \
  server -s3 && \
docker run -itd \
  -e "LICENSE_KEY=YOURLICENSE" \
  -e "MONGO=mongodb://mongo:27017/formio" \
  -e "FORMIO_S3_SERVER=seaweedfs" \
  -e "FORMIO_S3_PORT=8333" \
  -e "FORMIO_S3_BUCKET=formio" \
  -e "FORMIO_S3_KEY=CHANGEME" \
  -e "FORMIO_S3_SECRET=CHANGEME" \
  --network formio \
  --link formio-mongo:mongo \
  --link formio-seaweedfs:seaweedfs\
  --restart unless-stopped \
  --name pdf-server \
  -p 4005:4005 \
  formio/pdf-server;

```


---

# 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://help.form.io/dev/dev-license.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.