- an Azure Database for PostgreSQL flexible server holds the data;
- one Web App runs two containers: the interface (
apowerb-ui) as the main container, which receives the traffic, and the API (apowerb) as a sidecar next to it.
localhost and proxies every /api call.
The API therefore has no public address, which keeps the same layout as the
Docker Compose stack.
Every step below was run end to end on 8 October 2026 on a new Azure free
account, in the France Central region, with the portal in English and Azure CLI
2.91.0: sign-up, sign-in, an agent created, then read back from the database.
Start with free credits
New Azure customers can open an Azure free account:- $200 of credit to use on Azure services within 30 days. The French page shows the same amount in US dollars, not in euros.
- To sign up you need a phone number, a non-prepaid credit or debit card, and a Microsoft or GitHub account. Azure places a temporary $1 authorization on the card.
- After 30 days, Azure asks whether you want to move to pay-as-you-go pricing. If you don’t, your account and services are disabled.
- App Service also has a Free (F1) tier: up to 10 web or API apps with 1 GB of storage and 1 hour of compute per day. It is a shared tier with no scale-out. This guide was tested on Basic B1, not on F1.
- Full-time university students can use Azure for Students instead: $100 of credit for 12 months, no credit card required.
What it costs
Estimates shown by the portal on 8 October 2026, in France Central:Before you start
Choose the names and prepare two secrets. Keep them in a password manager, not in a file you commit.ENCRYPT_KEY encrypts the credentials of the integrations you connect later.
Back it up: if it is lost or changed, those credentials can no longer be read.
1. Register the resource providers
On the new subscription used for this guide, the two resource providers needed here were not registered. Register them once, from Azure Cloud Shell or a terminal whereaz login has run:
Registered.
2. Create the PostgreSQL server
In the portal search bar, typepostgresql flexible and open
Azure Database for PostgreSQL Flexible Server under Marketplace.
Basics: project and server
- Resource group: click Create new and type
rg-apowerb. - Server name: your unique name, for example
pg-apowerb-7f3a. - Region: the region you will also use for the Web App.
- PostgreSQL version: 16, the version the apowerb stack is tested with. The form offers 18 by default.

Create a new resource group from the PostgreSQL form.
Basics: size and cost
- Workload type: Dev/Test.
- Zonal resiliency (under High Availability): Disabled.
- Compute + storage: click Configure server, keep Burstable, choose Standard_B1ms and keep 32 GiB of storage, then Save.

Burstable tier and the Standard_B1ms size: the estimate drops to about 17.56 USD/month.

The summary to check before going further.
Basics: authentication
- Authentication method: PostgreSQL authentication only.
- Administrator login:
apowerbadmin. - Password and Confirm password: the password you prepared.
Networking
- Keep Public access (allowed IP addresses).
- Tick Allow public access from any Azure service within Azure to this server. This is what lets the Web App reach the database.
- Do not add the
0.0.0.0 - 255.255.255.255rule: it opens the database to the whole internet.

The one box to tick on the Networking tab.
Create
3. Create the th2agent database
The server comes with a postgres database only. apowerb expects a database of
its own.
In the portal, open the server once its status is Ready, then
Settings › Databases › + Add. Type th2agent in Name, keep the
default character set and collation, and click Save. The database appears
in the list a few seconds later.
Or in Cloud Shell:
th2agent.
az postgres flexible-server create --database-name th2agent is refused by
Azure CLI 2.91: the option now only applies to elastic clusters. Create the
database with the separate command above.4. Create the Web App
In the portal, Create a resource › Web App.Basics
Container: the interface
:0.1.35 you get
latest, and the interface and the API are only guaranteed to work
together at the pinned pair. The form proposes port 80: replace it with
3000, or App Service probes a port where nothing listens.
The interface as the main container, on port 3000.
Monitor + secure
Create
apowerb/apowerb-ui:0.1.35 on port 3000, then Create.Note the default domain
apowerb-7f3a-abc123def456ghij.francecentral-01.azurewebsites.net: the
address is not simply <name>.azurewebsites.net. You need the exact
value in the next step.5. Set the environment variables
In the Web App, Settings › Environment variables › App settings. App settings are shared by every container of the app, the sidecar included.DB_PASSWORD and ENCRYPT_KEY.

The Add/Edit panel masks the value as you type it.
WEBSITES_ENABLE_APP_SERVICE_STORAGE on its own; leave it.
6. Add the API as a sidecar
In the Web App, Deployment › Deployment Center › Containers › + Add › Custom container.
The API as a sidecar: Docker Hub image, port 8000, and access to the app settings.
main (Main) and
apowerb (Sidecar). The first start takes a few minutes: the API image is
about 250 MB, and it creates its tables on first boot.
7. Check the deployment
A page that answers200 only proves that the interface is up. Check the API
through the interface, then the real path.
502on/api/agents: the API is not reachable yet. It is either still starting (wait two or three minutes, especially after a settings change) or it failed to start: check the variables of step 5.404on/api/healthis normal: the API health route is not published through the interface.
- Create Account with an e-mail and a password. You are signed in and land on the dashboard, which shows no agent yet.
- Click Create starter agent. apowerb opens Agent Factory, and a
starter_agent_…is listed: the API is writing to the database. - Reload the page. The agent must still be listed.
Clean up
Everything lives in one resource group. To stop all charges, delete it:rg-apowerb › Delete resource group.
The database, its data and the accounts created in the app are deleted with it.
Troubleshooting
Not covered by this page
- A language model. Agents can be created, but not run, until you set
DEFAULT_LLM_MODEL,DEFAULT_LLM_API_KEYand, if needed,DEFAULT_LLM_API_BASE. - Workflows. They rely on the
th2etlservice, which this setup does not deploy. - Uploaded files. No volume is mounted on
/app/data: files stored there are lost when the containers restart. Agents themselves are stored in PostgreSQL and survive. - Logs and traces (
th2pulse, OpenTelemetry collector), a custom domain, and the Free (F1) tier were not tested.
