> For the complete documentation index, see [llms.txt](https://docs.dorg.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dorg.pro/install-dorg/install-a-new-dorg/running-the-installation.md).
# Running the Installation
The installer can be downloaded from the [Dorg Agency](https://portal.dorg.pro/) after purchasing a Dorg user. It is available for the following operating systems:
* Windows 11
* MacOS (available soon)
* Linux Ubuntu (available soon)
Download and run the `Dorg-3-x-Installer-1.y.z-x64.exe` installer application.
## Step 1 - Precheck
The installer checks for the required prerequisite software, such as:
* Node.js
* Azure CLI
* Pulumi CLI
If all prerequisites are satisfied, you can proceed to the next step.
## Step 2 - Inputs
Enter the information required to install the application:
* **Azure Subscription ID**
* **Resource Group name** (created during the preparation step)
* **Dorg user email address** (created during the preparation step)
* **Unique code for your Dorg** (example: `-dorg`)
* **License file** downloaded from DORG Agency
* The **Cloud Api Keys**
## Step 3 - Advanced settings
#### High availability
Optional Level 2 — Standard High Availability raises the deployment profile: more replicas per service, stronger database and storage options (including zone-redundant and backup-oriented choices as described in the installer), aimed at higher uptime during your operating window. Leave it off for the default Level 1 base profile.
{% hint style="warning" %}
Enabling High Availability will increase operational costs significantly.
{% endhint %}
#### Azure region
Sets the Azure region used for the stack. The default is Sweden Central; change this when you need another geography—for example if quotas, latency, or regional capacity make another region a better fit. It is better that also the Resource Group is set to the same region.
#### Container Apps environment tier
Chooses the Azure Container Apps managed environment workload profile:
* **Consumption** (shared serverless pool, scale-to-zero friendly, but more exposed to regional capacity limits).
* **D4** or **D8** dedicated general-purpose nodes (reserved capacity, fewer shared-pool surprises)
D4 is recommended when costs are not an issue: it allows more reliability during installation, with very low changes of low capability on Azure region, and provide more reliable performances.
Using Consumption tier is cheaper but still fair for not high-consumption Dorg operations, but may hit temporary Azure Capacity limits during installation, causing delays in installation times.
{% hint style="warning" %}
The D4 and D8 profiles will increase Azure costs significantly, compared to the Consumption profile. Please refer to Azure documentation for more details:
{% endhint %}
#### Azure Speech
Controls how Azure Cognitive Services Speech is provisioned for voice features: F0 (free tier, limited to one per region per subscription), S0 (paid), or Reuse an existing SpeechServices account from another resource group (discovered in-subscription; reused accounts are not destroyed when this dorg stack is torn down). Pick Reuse or S0 when F0 is not available in that subscription/region.
#### Scaling scheduler
Optional start/stop scheduling scales services down during off-hours to save cost. You can enable it and supply [*cron*](https://crontab.cronhub.io/) expressions for when workloads should start and stop (defaults target weekday business hours in Central Europe Standard Time), or disable it for 24/7 operation.
## Step 4 - Azure Validation
The installer verifies:
1. Azure prerequisites
2. The existence of the specified Subscription
3. The existence of the Resource Group
4. Your access permissions
If you are not already authenticated, the installer may prompt you to log in to Azure (az login).
## Step 5 - Application Deploy
The installer deploys all application components into the specified Resource Group.
It also configures three applications in Microsoft Entra ID.
The full deployment process may take up to one hour.
## Step 6 - Application Endpoints, Credentials and DNS record
At the end of the deployment, the installer displays a summary of the main application endpoints, service credentials and the DNS records that must be configured in your DNS (see next section).
It is recommended to copy the full deployment log and retain it for future reference.
---
# 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://docs.dorg.pro/install-dorg/install-a-new-dorg/running-the-installation.md?ask=&goal=
```
`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.