Security & Telemetry

Preview

During Public Preview you can use the Team plan for free, and get an early-adopter discount at GA. Sign in

Security & Telemetry

This page answers the questions a security review asks of a tool that runs on a developer's laptop: what it listens on and for whom, what leaves the machine, what it stores, and how to turn each of those off.

What listens, and for whom

Every Locally service binds the loopback interface except two that containers need to reach through the host gateway: the DNS server on 5673 (UDP and TCP), and the managed-identity token endpoint for hosted apps, on a port chosen at launch and defended by a per-app secret header. Nothing else is reachable from another machine. The control plane and HTTP data planes can't be exposed at all; the container, database and messaging ports can be, but only if you set an environment variable to do so. Networking & Proxies has the full map with the bind address of each port.

Everything HTTP is HTTPS, signed by a Certificate Authority created on your machine by locally setup; its private key never leaves the config directory. Database data planes require TLS on the wire, as Azure does: the Postgres and MySQL flexible-server emulators refuse a clear-text login with the same errors Azure returns for require_secure_transport=ON, SQL Server encrypts every login, and Redis's clear-text companion port is off unless the cache was created with enableNonSslPort. A connection string copied from Locally therefore behaves the way the same string would against Azure.

Credentials and tokens

Locally issues real, RS256-signed JWTs from a signing key generated fresh at every launch. They are accepted only by the services on your machine and only for the lifetime of that launch - a token copied out of one session is worthless in the next, and worthless against Azure. With locally build --persist, the signing key is kept with the saved state instead, so a token issued before a restart still works after it. The seeded service principals, users and managed identities are local fixtures: their client secrets and passwords are stored in memory and in your config directory, never sent anywhere. The default identity is deliberately over-privileged (Global Administrator and Owner) so that development is frictionless; use locally run --user, --service-principal or --managed-identity to exercise a less privileged principal, and Minimum Necessary Permissions to find out which role your deployment actually needs.

The Control Plane API can be browsed in a browser without authentication - a convenience for local development that is on by default and can be turned off in Settings → Feature Flags in the Dashboard.

The Control Plane API can also be told to ignore RBAC permissions, so any authenticated principal is granted access before role assignments are configured. Tokens are still validated. This is off by default and can be turned on in Settings → Feature Flags - see Feature Flags.

What leaves the machine

Locally itself contacts four hosts, all over HTTPS on port 443:

Host When What is sent
api.locally.buildCertificate renewal, at least every 32 days; the plugin catalogue; team content sync; locally update and locally update --check; analytics and crash reports if you opted inThe installation certificate (which identifies this install and its plan), the CLI version and platform, and the payloads listed below
account.locally.buildlocally login and locally setup sign-inYour browser signs in there, not the CLI; the CLI receives the resulting installation certificate
get.locally.buildDownloading a new CLI version with locally updateThe version and platform being downloaded
t3.storageapi.devPlugin and CLI downloads, through short-lived signed links handed out by the hosts aboveNothing beyond the signed link

Between certificate renewals Locally works with no network at all. Renewal and sign-in cannot be disabled - the certificate is the licence - but everything below can.

Some features reach further, and only when you use them:

  • Container images. Web Apps, Function Apps, Container Apps, SQL Server, PostgreSQL, MySQL, VM extensions and deployment scripts run in containers. The first time one is needed, Docker or Podman pulls its image from mcr.microsoft.com or Docker Hub (registry-1.docker.io, auth.docker.io, production.cloudflare.docker.com), using the runtime's own proxy settings.
  • Debugging a .NET Web App downloads the debugger from github.com the first time.
  • locally refresh-reference-data runs your Azure CLI against Azure itself, so it reaches management.azure.com and login.microsoftonline.com.
  • locally ci asks your CI provider for an OIDC token.
  • Hosts you point Locally at, such as an API Management backend, a registry you az acr import from, a VM extension's fileUris, or the package feeds a Web App build restores from.

No emulator calls Azure, and Locally sends nothing to a third-party analytics or error-reporting service.

Crash reports and analytics

Both are opt-in. The data-sharing step of locally setup offers three answers - share nothing, share crash reports, or share crash reports and analytics - and you can change your answer at any time by re-running locally setup; it takes effect from the next launch. Neither payload ever contains resource names, resource properties, secrets, request bodies or your account details.

Screenshot of the data-sharing step during Locally setup

Crash report fields

A crash report is written when the Locally process panics, a plugin process dies or hangs, or a container Locally launched fails to become ready. It is stored under crashreports/ in the config directory first, so you can read exactly what would be sent (and delete it) before it is submitted on the next launch.

Field Contents
uuid, occurredAt, schemaVersionA random ID for the report, when it happened, and the report format version
kindprocess-panic, plugin-crash or container-failure
installationIdThe installation UUID, so repeat crashes on one machine can be correlated
applicationVersion, platform, architecturee.g. v2026.09, darwin, arm64
componentWhich process failed - the CLI, a named plugin, or a container
commandThe locally subcommand that was running (for example build), not its arguments or environment
summary, stackTrace, truncatedThe panic message and the Go stack trace, capped at 256 KiB with truncated set when the cap was hit. Container failures carry no stack trace.

Analytics fields

Analytics record what kinds of resources a launch provisioned, so we can prioritise which Resource Types and API versions to work on, and populate Locally Directory. One event is written to disk when Locally shuts down and submitted on the next launch with internet access - or discarded, if you haven't opted in. locally analytics prints what the current launch has recorded:

Screenshot of the result of running 'locally analytics'
Field Contents
installationID, eventDate, applicationVersionWhich install, which day, which CLI version
launchDurationHow long Locally ran, in minutes
totalResourcesProvisionedA count
provisionedResourceTypes[]Per type: resourceType (e.g. Microsoft.Storage/storageAccounts), number, the apiVersions used and the skus chosen. Never a resource name, group, location or property.

Retention

Submitted analytics events and crash reports are stored by the Locally API against your installation. There is no automatic expiry today; to have them removed, get in touch and quote the installation UUID that locally analytics prints. Locally's own on-disk copies live in the config directory and are yours to delete at any time. Website and account analytics are separate and covered by the Privacy Policy.

What is stored on disk

  • Config directory (~/.config/locally; %LocalAppData%\locally on Windows): config.json, the local CA and TLS certificate with their private keys, the installation certificate from your account, installed plugin binaries, synced team content, pending analytics events, crash reports, your snapshots (including the state --persist saves), and the Azure CLI working directory locally run az uses.
  • A temporary directory (locally-storage-* under the OS temp location) holding blob and file-share content while Locally runs; removed at shutdown.
  • The request log is held in memory only, bounded to the last 15 minutes by default, and does record request and response bodies - including any secret you send to an emulator - for the duration of that window. It is never written to disk or sent anywhere.

Nothing you provision is written to disk unless you ask for it: locally snapshot save and locally build --persist save your resources and their data to the snapshots folder in the config directory. Those files hold your resources' credentials, such as Key Vault secrets and keys, and are only encrypted if you save a snapshot with --passphrase.

Reporting a vulnerability

Please report security issues privately rather than in a public issue: the contact and disclosure details are published at /.well-known/security.txt.

Preview

During Public Preview you can use the Team plan for free, and get an early-adopter discount at GA. Sign in

A local cloud for you and your AI agents.

Your Azure infrastructure, running on your machine. Deploy in seconds, break things freely, and ship to Azure when you're ready.