Last updated: 2026-10-02.
These Terms and Conditions cover your use of the Locally application - the Locally CLI, the Locally Dashboard, the Plugins, and any emulators, MCP servers and helper components that the CLI installs or runs on your machine (together, "Locally" or "the Locally application"). The Plugins are also covered by our Locally Plugin Terms & Conditions, which add a few points specific to them.
They are in addition to our Website & Locally Account Terms & Conditions and our Privacy Policy, which also apply.
Before you can use Locally, you'll be asked to accept these Terms and Conditions, together with our Website & Locally Account Terms & Conditions and our Privacy Policy, when you first run locally setup, and you accept them by continuing past that screen. If you sign in, your Locally Account also asks you to accept its Terms and Conditions and our Privacy Policy.
If we change these terms, the new version applies once it takes effect, and you accept it by continuing to use Locally afterwards. If you've signed in and a change materially affects you, we'll let you know first (see Changes, below).
We give you a personal, worldwide, non-exclusive, non-transferable, revocable licence to install and run Locally on devices that you control, for as long as you keep to these terms and, if you've signed in, your Locally Account is in good standing.
Use Locally for personal projects, learning and evaluation, and for commercial work while you're signed in to a Locally Account (see Commercial use, below). Run it on Linux, macOS and Windows (on the architectures we publish builds for). Run it inside CI, within the concurrent-instance limit of your plan. Integrate it with the tools we support (Azure CLI, Terraform, OpenTofu, Pulumi, ARM Templates, Bicep, and similar).
Redistribute, resell, sublicense, or host Locally as a service for other people. Modify, reverse-engineer, decompile or disassemble the Locally application except to the extent that English law expressly allows. Use Locally to build or improve a competing product or service - such as another Azure emulator or local-cloud tool - or to copy Locally's features, design or user interface. (Using Locally to develop and test your own software, including tools that run on Azure, is exactly what it's for.) Remove or alter any copyright, trademark or other notices. Share your Locally Account, or the credentials Locally issues to it, with people who don't have their own Locally Account, or otherwise use Locally to circumvent the limits of your plan. Use Locally to build, test or deliver anything illegal, anything that infringes someone else's rights, or anything intended to harm people or systems.
You can use Locally without a Locally Account, within the limits described on our pricing page; signing in lifts some of those limits and lets you use Locally in CI. We follow industry-standard practices for authentication so you don't have to trust us with passwords:
You're responsible for keeping your sign-in credentials secure and for any activity that happens through your Account. The User and Team UUIDs that identify your OIDC trusts aren't secrets - they're just identifiers, and only work in combination with a valid OIDC token from an issuer you've trusted - so they don't need to be treated as credentials.
If you think your Account has been compromised, or that an OIDC trust has been configured to accept tokens from somewhere it shouldn't, please get in touch and remove the affected trust from your Account.
Each Locally Account has a plan (for example Starter, Standard or Team). Your plan determines things like session length, the number of subscriptions you can create, and how many concurrent CI instances you can run. Current plans and limits are described on our pricing page.
We may rate-limit, slow down, or stop sessions that exceed the limits of your plan. While Locally is in Public Preview, plan limits and pricing may change before general availability - we'll give you reasonable notice of any change that materially affects you.
To use Locally for commercial work, you need to be signed in to a Locally Account. On the free Starter plan, commercial use is limited to organisations with an annual revenue (turnover) of less than 1,000,000 US dollars - or 1,000,000 pounds sterling or euros, where that's the currency the organisation reports its annual accounts in. The organisation is the one the work is for, together with any group of companies it belongs to.
If that organisation reaches this limit, you'll need to move to a paid plan within 30 days. Paid plans aren't available yet, so this limit applies once they launch.
Paid plans aren't available yet. Once they are: payment issues happen - cards expire, banks decline, invoices get missed. If we can't take a payment for a paid plan, we'd rather work with you to fix it than cut you off. So here's the order of things:
Once paid plans launch, you'll be able to update your payment details from inside your Locally Account at any time to fix things and switch back to your paid plan.
Locally is designed to run on your machine. The CLI, the Dashboard, the control plane API and the data-plane emulators all run on hardware that you control. Locally does not create real resources in Azure or in any other cloud, and these terms don't change that.
Some emulators (for example database emulation) may start additional containers using Docker or Podman on your machine. You're responsible for installing and running those container runtimes, and for any compute, memory, disk or network resources Locally uses on your system.
To run those containers, Locally may download container images from public registries such as Docker Hub or the Microsoft Container Registry. Those downloads are subject to the registry's own terms.
Locally is for development and testing. It is not a substitute for testing against a real Azure subscription, and it should not be used as a production runtime for live workloads.
Locally is designed to keep working when you're offline. To make that possible, your installation periodically fetches a short-lived installation certificate from the Locally API and then uses that certificate to validate itself locally for the rest of its lifetime - so you don't need a network connection for day-to-day use.
The certificate currently lasts up to 32 days. To stay offline-capable, your installation needs to come online for long enough to renew the certificate at least once inside that window. If a certificate expires before it's renewed, Locally stops, and won't start again until it can reach the Locally API and renew it. Nothing on your machine is deleted.
We intend to keep supporting offline and disconnected use. We may still change how installations are licensed and validated - the certificate's lifetime, or the mechanism itself - for example if our security posture changes. If a change would meaningfully shorten how long you can stay offline, we'll give you reasonable notice before it takes effect.
You can use Locally inside continuous integration and other automation, within the concurrent-instance limit of your plan. Authentication from CI is handled via OIDC trusts that you configure against your User or Team in your Locally Account - your CI provider exchanges its own short-lived identity token for Locally credentials at run time, and those credentials inherit the limits of your plan. We recommend removing OIDC trusts you no longer need from your Account.
We release updates to Locally regularly to add features, fix bugs and improve compatibility with the cloud services we emulate. We try to keep updates backwards-compatible where we can, but some updates may be required to keep using Locally - especially if an older version stops working with the Locally API. If we have to make a breaking change, we'll do our best to flag it in advance.
Locally works alongside third-party tools such as the Azure CLI, Terraform, OpenTofu, Pulumi, Bicep, ARM Templates, Docker and Podman. Those tools are provided by their own vendors under their own licences and terms; we're not responsible for them, and these terms don't change your relationship with their providers.
Locally is an independent product, and isn't offered by, associated with or endorsed by Microsoft or any other company mentioned in our materials. Microsoft, Azure, Microsoft Entra and related marks are trademarks of Microsoft Corporation, and other trademarks belong to their respective owners.
The Locally application bundles open-source software. The full list of components and their licences is available inside the Locally Dashboard. Those licences apply to the components they cover; nothing in these terms is intended to override or limit your rights under them.
Most of what you do with Locally stays on your machine. Some features (for example signing in, validating your plan, fetching updates, renewing your installation certificate and exchanging OIDC tokens for CI credentials) require Locally to communicate with the Locally API. If you turn them on, Locally also sends us usage analytics and crash reports. Exactly what Locally sends, and how long we keep it, is described under "When you use the Locally application" in our Privacy Policy.
You're responsible for any code, configuration, secrets and other data you put into Locally on your own machine.
Because that data stays on your machine, we don't act as a data processor for it on your behalf - we don't see it, store it, or make decisions about it. If your use of Locally involves handling personal data, you remain the controller of that data, and the responsibility for protecting it stays with you.
The exception is content you or your teammates upload to a team, such as Locally Runbooks and Locally Policies. We store that on your team's behalf and sync it to the installations of everyone in the team. Your team decides what goes in it, and remains responsible for any personal data it contains.
We take reasonable care to make sure what we publish is free of viruses and other malicious code: updates to the Locally CLI and Plugin downloads are checked against a checksum before they're installed, and updates to the Locally CLI are also signed. We can't guarantee they'll never contain anything harmful, so keep your own security software and backups up to date.
We're not responsible for code or content that comes from somewhere else - the container images Locally downloads from public registries, and anything you or your team run or upload into Locally, including your own applications, Locally Runbooks and Locally Policies.
You must not use Locally, or your Locally Account, to introduce malicious code into our systems or anyone else's.
Locally is provided "as is". We work hard to make it stable and reliable, but we can't guarantee that it's bug-free, that it will be available without interruption, or that it will exactly reproduce the behaviour of every Azure service it emulates. You should still test important workloads against real Azure before relying on them.
The accuracy of our emulators is on a best-effort basis: the cloud services we emulate can change at any time, and there may be gaps and differences. If you spot something that doesn't behave the way it should, please raise an issue in your Locally Account or let us know, and we'll work to fix it.
To the maximum extent allowed by law, we're not responsible for: business or technical decisions you make based on Locally's behaviour; costs you incur in Azure or any other cloud because a tool wasn't correctly configured to talk to Locally; data loss or corruption on your own machine or in containers Locally starts on your behalf; or any other indirect, incidental or consequential loss. If you're a consumer, this doesn't limit our responsibility for damage to your device or other digital content caused by our failure to use reasonable care and skill.
Locally is currently free for everyone during Public Preview, and we'll continue to offer a free Starter plan after general availability. We've set the limit below to reflect that - on a free plan the cap will be a nominal one pound, and on a paid plan it'll be the fees you've paid us for Locally over the previous twelve months.
Our overall liability to you in connection with Locally is limited to the greater of (a) the fees you have paid us for Locally in the twelve months before the issue arose and (b) one pound sterling (£1). Nothing in these terms limits any liability that can't be limited by law - including liability for fraud, fraudulent misrepresentation, death or personal injury caused by negligence - and your consumer rights under UK law aren't affected by these terms.
If a claim is brought against us because of how you've used Locally - for example because the code or infrastructure you've built with it infringes someone else's rights, or because you've used Locally to do something these terms prohibit - you'll cover any costs, damages and reasonable legal fees we incur as a result, to the extent the issue is down to your use of Locally rather than to Locally itself.
You can stop using Locally at any time. You can also close your Locally Account from inside the Account, which ends access for any installations linked to it. If you own a team, have added Locally Runbooks that a team still uses, or are the contact for an open team issue, you'll need to hand those over to another member or remove them first; if you're the only member of a team, that means deleting the team. If you want to keep using Locally without an account after that, you'll need to sign out (locally logout) and set it up again with locally setup, within the limits described on our pricing page.
We may suspend or end your access to Locally if you materially breach these terms, or if we reasonably believe Locally is being used to harm other people, our systems or third-party systems. Where it's appropriate to do so, we'll let you know first and give you a chance to fix the problem.
When your right to use Locally ends, you must stop using the Locally application. Files, code and other data you've produced on your own machine remain yours.
We may update these terms from time to time - for example when we add new features, change plans, or have to respond to legal or security changes. The "Last updated" date at the top of this page shows when we last changed them. If you've signed in and a change materially affects you, we'll let you know inside your Locally Account or by email before it takes effect. Whether or not you have a Locally Account, if you keep using Locally after a change takes effect, you accept the new version; if you don't want to, you can stop using Locally.
These terms are governed by the law of England and Wales. Any disputes arising out of or in connection with them will be handled by the courts of England and Wales.
Together with our Locally Plugin Terms & Conditions, our Website & Locally Account Terms & Conditions and our Privacy Policy, these terms make up the whole agreement between us about your use of the Locally application. If you've signed a separate agreement with us, for example for an Enterprise plan, that agreement applies too, and takes precedence over these terms where the two differ.
If any part of these terms turns out to be unenforceable, the remaining parts will still apply. We're not responsible for delays or failures caused by events outside our reasonable control (such as natural disasters, strikes, network outages, or failures of upstream providers).
You can't transfer your rights under these terms to anyone else without our written consent. We may transfer ours as part of a sale, reorganisation or restructuring of our business, as long as your rights aren't materially reduced as a result.
Locally is operated by Locally Build Limited, a company registered in England and Wales (company number 16453819), with its registered address at 20 Wenlock Road, London, England, N1 7GU.
Got a question about something that isn't covered here? Feel free to reach out and we'll get back to you.
Your Azure infrastructure, running on your machine. Deploy in seconds, break things freely, and ship to Azure when you're ready.
