Quinzee Cloud

Quinzee components and runtime

Understand what Quinzee runs, where it runs, and how your application connects.

Local application development

Quinzee Cloud runs a defined subset of Azure-compatible services on your own Linux infrastructure. Applications connect through supported Microsoft SDKs, REST APIs, ARM and Bicep.

It is intended for developers who need a local environment they can inspect and control. The commercial Linux distribution is in development; a public installer is not available yet.

The moving parts

The cloud service handles resource management and service APIs. QHQ is the native management interface. Local DNS resolves supported Azure-style service names, while development certificates provide verified HTTPS.

  • Control plane: create and configure resources through Azure Resource Manager.
  • Data plane: use resources through service-specific SDKs or REST.
  • Native engines: PostgreSQL, MySQL and Valkey run in managed local containers.
  • Functions: a separate helper runs registered .NET application images.

Know the boundaries

Local compatibility does not reproduce Azure billing, regional resilience, capacity or full RBAC. Validate authorization, scale and failure behavior against your real deployment target. Use synthetic development data; the emulator does not encrypt stored secret values at rest.