Your cloud, running locally.

We're pretty happy with Locally, but there are some missing Plugins, features and bugs we'd like to sort out before we start charging, so for now it's in Preview. During Preview, everyone who signs in gets the Team plan for free, so you can try every feature. We'd love to hear what does and doesn't work for you.

After Preview, we intend to launch the plans shown above. They may change before then, but there'll be a generous free Starter plan that even covers commercial use for smaller companies once you've signed in.

No. Without an account, you can use Locally for up to 60 minutes at a time, with a limited set of Plugins.

Once you sign in to a Locally Account, you can use Locally for up to 4 hours at a time on the free Starter plan, or for as long as you like on a paid Standard or Team plan. Either way, you get every Plugin in your plan. You'll also need to sign in to use Locally for work or in CI.

The Getting Started guide takes you through installing Locally (with Homebrew, Scoop or by downloading it), setting it up, and provisioning your first resource.

Locally runs on:

• Linux (arm64 & amd64)
• macOS (Apple Silicon & Intel)
• Windows (arm64 & amd64)

Some services, such as databases, Web Apps and Container Instances, also need Docker or Podman. See Requirements for the full list. If you need Locally on another platform, let us know.

We'll email you at least 30 days before Preview ends, so you've time to choose a plan. As an early adopter, you'll get a discount on a paid plan. If you don't pick one, your Locally Account moves to the free Starter plan. Nothing on your machine is deleted, but you'll lose access to the Standard and Team features and Plugins until you upgrade.

No. You don't need a credit card to use Locally, with or without a Locally Account. You'll only need one if you choose a Standard or Team plan once they launch.

Yes. Sign in to a free Locally Account and you can use Starter for commercial work, as long as your company's annual revenue (turnover) is under $1m (or £1m / €1m if those are your local currency). If you go over that, you'll need a Standard or Team plan within 30 days, once they launch. See the Locally CLI Terms & Conditions for the details.

Yes. We plan to offer a plan for open-source projects after Preview ends.

Yes. We plan to offer an Enterprise plan in the future. If you're interested, get in touch and let us know what you need.

Yes. Locally has a dedicated CI mode, locally ci, which signs in using OIDC. You can set up OIDC against your own Locally Account or against a team, and how many copies can run at once depends on your plan (see the plans above). The Using Locally in CI guide has all the details.

Locally covers a lot of Azure, and Azure never stands still. Keeping up means adding services, supporting new API versions and tracking changes as Microsoft makes them. The paid plans fund that work, so Locally can keep growing and stay accurate.

Locally is ephemeral for now: your resources exist for as long as Locally is running, and they're cleared when it stops. We plan to add saving and restoring your state, and sharing it with your team, in a future version of Locally.

Use Locally Runbooks, available on the Team plan. A runbook can provision shared infrastructure, such as a common network or database, and load schema and seed data into MySQL and PostgreSQL. Runbooks are shared through your Locally Account. They can run automatically when Locally starts, or when someone chooses to deploy one.

A session is one run of locally build, from when you start it until it stops. Sessions last up to 60 minutes without an account and up to 4 hours on Starter. On Standard and Team there's no limit. You can start a new session whenever you like, and there's no daily limit.

When a session reaches its limit, Locally stops, so your resources are cleared just as if you'd stopped it yourself.

Yes. Once it's set up, Locally runs entirely on your machine with no internet connection. It just needs to connect once a month to renew your licence, which happens automatically in the background.

No. Nothing in Locally creates resources in Azure, and everything, including the Dashboard, runs on your machine.

Data plane services such as Storage, Key Vault and Service Bus run as emulators on your machine, so your code, Infrastructure as Code and the Azure SDKs talk to them just as they would to Azure. For some services, such as databases, Locally starts a container with Docker or Podman to get closer to the real thing. Those containers run alongside Locally, never in the cloud.

Yes. Locally doesn't replace Azure, and you'll be deploying there anyway. What it does is give you feedback in seconds rather than minutes, cut what you spend on development and test resources, and catch problems earlier, such as a deployment that breaks one of your policies.