See how teams use Topaz to eliminate cloud costs, speed up CI pipelines, and ship Azure-backed applications faster — without a subscription.
From CI pipelines to microservices, here is how Topaz fits into the ways teams already work.
Spin up a full Azure environment inside your CI pipeline — no credentials, no cloud subscription, no per-run charges. Topaz starts as a container alongside your app, provisions resources via the Azure CLI, and your integration tests run against real Azure SDK clients.
Topaz implements the same REST and AMQP protocols as Azure. Swap the endpoint URL and credential, and your BlobServiceClient, SecretClient, ServiceBusClient — everything — works as-is. A NuGet helper handles credential wiring for .NET; the official topaz-sdk package on PyPI provides the same for Python.
// One-time setup — redirect SDK to Topaz
builder.Services.AddAzureClients(clients => {
clients.AddBlobServiceClient(
new Uri("https://topaz.local.dev:8891/..."));
clients.AddSecretClient(
new Uri("https://topaz.local.dev:8898/my-vault"));
clients.UseCredential(
new AzureLocalCredential()); // ← Topaz helper
});
// Application code is unchanged
var blobs = serviceProvider
.GetRequiredService<BlobServiceClient>();
await blobs.CreateBlobContainerAsync("uploads");
Deploy your Infrastructure-as-Code files to Topaz exactly as you would to Azure — az deployment group create, the Terraform azurerm provider, the Azure SDK, or a CI step. Topaz evaluates the template or plan, provisions all described resources, applies RBAC assignments, and lets you verify the resulting state without risking a misconfigured production environment.
Running a microservices architecture locally usually means juggling Azurite, a separate Service Bus emulator, and a fake identity service — or paying for a shared dev Azure subscription. Add a single Topaz service to your docker-compose.yml and get every Azure dependency in one place.
Whatever the workflow, Topaz removes the cloud dependency from your inner development loop.
Model least-privilege role assignments and verify that managed identities can only access the resources they are meant to — all without touching a production tenant.
Sketch a new Azure-backed feature and wire it end-to-end in an afternoon. No provisioning tickets, no shared dev subscriptions, no waiting.
Let new team members explore Azure APIs and SDK patterns in a safe, free, local environment before they ever touch a real subscription.
Work on a plane, in a secure facility, or anywhere without internet access. Topaz runs entirely offline — no Azure connectivity required.
Reproduce subtle SDK or serialization bugs locally with full control over resource state. No need to recreate transient cloud conditions.
Safely refactor how your application interacts with Azure services. Regression-test against Topaz before running against the real cloud.
The built-in MCP server lets GitHub Copilot, Claude, and other AI assistants provision and inspect Topaz resources through natural language. Create resource groups, storage accounts, and key vaults without writing a single CLI command — a capability no other Azure emulator offers.
With Azure SQL, App Service, Key Vault and Blob Storage all running locally, you can test the complete application stack end-to-end — web tier, database, secrets, and file storage — without a cloud subscription. Not possible with single-service emulators like Azurite.
Topaz is free and open source. Get it running in under two minutes.