ADR-002 — Azure multi-tenant deploy

Superseded 2026-05-25. The Azure hosting migration (roadmap item #33) was dropped as a cash-conservation call. Aroovo stays on Hostinger's VPS deployed via GitHub Actions, behind Caddy. This ADR is retained for the historical record but no longer reflects the active architecture.

Original context

ADR-001 Phase 5 (multi-tenant productisation) was originally gated on a hosting move from Hostinger's VPS to Azure Container Apps + Azure Database for PostgreSQL Flexible Server. The rationale at the time: easier per-region scale-out for resellers in different geographies, first-party Entra integration on the bot path, and a clean substrate for the per-Brand shared-bot tenant-claim pattern.

Why it was dropped

Hostinger holds up. The VPS + Caddy + GitHub Actions stack is comfortably under-utilised for the current customer volume. Migration cost would be substantial; near-term benefit is small.
Cash-conservation call. The same engineering calendar week is better spent on the marketing surface (#182), public docs (#189), and the design partner motion (#191).
No buyer signal yet. No customer has asked for a specific Azure-only certification, region, or compliance posture that would force the move.
Per-Brand isolation already holds. ADR-003 made the Brand layer the structural isolation primitive. Adding Azure would have hardened the operational layer but not changed the tenant model.

What stays from this ADR

The Tenant model, the per-tenant scoping work in Phase 5 of ADR-001, and the encrypted-secrets-vault posture are all live. None of those depended on Azure specifically; they were drafted here because this ADR was the original umbrella for the multi-tenant work.

When to revisit

A design-partner buyer asks for an Azure-only deployment as a procurement requirement.
Hostinger's VPS becomes a bottleneck (capacity, region, or SLA).
SOC 2 work (deferred from the roadmap) reopens and the auditor flags the hosting choice.

References

Full markdown: adr-002-azure-multitenant-deploy.md.