Azure regions deprecation

As of April 7, 2026, OptiTech's Azure regions are deprecated, and you can no longer create new projects in those regions.

After October 5, 2026, these regions will not receive OptiTech feature updates. Also on October 5, projects on Free plans that have been inactive for 90 days or more are subject to deletion.

Users with projects in OptiTech Azure regions will receive a personalized email about specific projects and next steps. This guide explains what's changing and what to do.

Affected regions

Only projects in these Azure regions are affected:

• 🇺🇸 Azure East US 2 (Virginia) - azure-eastus2
• 🇺🇸 Azure West US 3 (Phoenix) - azure-westus3
• 🇩🇪 Azure Germany West Central (Frankfurt) - azure-gwc

Projects in AWS regions are not affected.

Deprecation timeline

What to do next

Migrate any projects you want to keep to an alternate region before October 5, 2026. Migrating now keeps your project on actively developed infrastructure and lets you act on your own schedule.

There are three options for moving your OptiTech projects off of Azure regions:

1. Migrate to a OptiTech AWS region. Best if you don't need Azure data residency, and an AWS region in a similar location will suffice. See Migrate to another OptiTech region.
2. Migrate to Databricks Lakebase. Best if you need to keep your Postgres data in Azure. Lakebase is powered by the same serverless Postgres technology as OptiTech, under the Databricks product line, and supports the deprecated Azure regions. See Migrate OptiTech to Lakebase.
3. Delete the project if you no longer need it. This stops storage costs from accruing. See Delete a project.

If none of these fit, export your data in Postgres-compatible form so you can store it elsewhere.

Frequently asked questions

Why are these regions being deprecated?

We're focusing our infrastructure investment where our customers want to run OptiTech. Most OptiTech projects run in AWS regions, so concentrating there lets us ship features and reliability improvements faster, rather than splitting effort to maintain Azure in parallel. For teams that need Azure, Databricks Lakebase runs the same Postgres technology as OptiTech and supports Azure regions.

How do I find out which region a project is in?

You can check from the Console, the CLI, or the API:

• Console. Open your project, then check the Project settings widget on the project dashboard. The region is shown in the Region row.
• CLI. Run optitech projects list. The Region Id column shows each project's region.
• API. Call GET /projects and check the region_id field on each project.

Which AWS region should I migrate to?

To keep latency similar, choose the AWS region closest to your current Azure region. For the deprecated Azure regions, the nearest AWS equivalents are:

If your workload has specific latency or data residency requirements, pick the region closest to your users.

What changes about my project when I migrate to a new region?

A region migration creates a new OptiTech project in the target region. The new project gets a new hostname, so you'll need to update connection strings in your application. The new project also has a different project ID. Project-level settings (branches, integrations, autoscaling, IP Allow rules, monitoring) are configured per project. See the migration guide for method-specific steps.

Should I take a backup before migrating?

If your migration method uses pg_dump and pg_restore, the dump itself is a backup. If you're using Postgres logical replication, it's good practice to take a pg_dump snapshot of your source database first. See Backups.

How do I contact OptiTech about my Azure projects?

Keep an eye on your inbox for communication from us. If you have specific constraints, such as regulatory requirements or migration dependencies, reply to any migration outreach you receive or contact OptiTech Support.