Algorand Sandbox is a free, open source tool that helps Web3 developers build a local Algorand development environment on their own computer. It is aimed at developers who want to test smart contracts and applications without depending on a public network for every experiment. The project brings together Algod, the core node software, and Indexer, the service that lets you query blockchain data, so you can start from a working stack instead of wiring each component by hand.
The program is designed as a fast way to create and configure that environment, and it is organized around containers. Windows users follow a longer path than a typical installer, because the setup runs through Git for Windows, Docker Desktop and WSL2. The code was last updated in August 2026, which means the project is actively maintained. Plan for several steps and a few restarts before your first run.
What Is Algorand Sandbox and Why Developers Use It
Algorand Sandbox is a local toolkit for running an Algorand development network on your own machine. Instead of connecting to a public network, your application talks to a node that you start and stop yourself. That gives you control over timing, account balances and the state of the ledger during tests.
Developers usually reach for a sandbox when a public test network feels too slow or too unpredictable. Public networks change, and waiting for confirmations can make a debugging session drag on. A local environment lets you run the same transaction over and over until the logic is correct.
The value of the tool is in the time it saves. Rather than assembling node software, indexing services and configuration files manually, you start from a prepared setup. The result is a stack you can reuse across projects, which is especially helpful when you move between prototypes and larger test suites.
Who Algorand Sandbox Is For
The most natural audience is developers who write smart contracts or decentralized applications on Algorand. If you are learning the platform, a local environment lets you experiment without worrying about small mistakes costing anything on a live network. Students and hackathon teams often benefit from that freedom.
Quality assurance engineers also have a use for local networks. They can build repeatable test scenarios, reset the environment and check how an application handles edge cases such as failed transactions or unusual account states. Repeatability is the main advantage here.
Team leads who support several developers may find the shared setup useful. When everyone runs the same environment, bugs are easier to reproduce, and onboarding a new engineer becomes a matter of following one documented process instead of troubleshooting a different configuration on every laptop.
How a Local Blockchain Environment Works
A blockchain node is software that stores the ledger, validates transactions and answers requests from applications. Algod plays that role in the Algorand stack. When you run it locally, your application sends transactions to your own machine rather than to a remote server.
Indexer works differently. It reads the ledger and organizes the data so that applications can search for transactions, accounts and assets efficiently. Without an indexer, many read operations would require scanning the chain directly, which is slow for anything beyond simple lookups.
Containers tie these pieces together. Docker packages each component with the dependencies it needs, so the environment behaves the same way across machines. On Windows, the container engine relies on WSL2, which runs a Linux kernel in a lightweight virtual machine. Understanding this layering makes troubleshooting far easier when something fails.
Key features
Local Algod Node
Indexer Alongside Algod
Follower Node Option
Multi-Platform Documentation
Supported coins
The documentation centers on Algorand as the network this environment is built for. Work done here targets the Algorand ecosystem, so the assets and smart contracts you test will be those that run on Algorand. If you need another chain, look for a tool designed for that network instead.
How to install Algorand Sandbox on Windows
- 1
Install Git for Windows
Download the installer from the official site at gitforwindows.org. Run it with the default options unless you have a specific reason to change them. Git is needed to copy the sandbox repository to your machine, so confirm that the installation completed before moving on.
- 2
Enable WSL2 and a Linux Distribution
Install WSL2 following Microsoft's official instructions, then install a Linux distribution such as Ubuntu. Set WSL2 as the default version so Docker can use it. Expect that Windows may need a restart before the new software is recognized correctly.
- 3
Install Docker Desktop
Download Docker Desktop only from the official Docker site at docs.docker.com/get-docker. During setup, make sure the WSL2 backend is enabled and that your Linux distribution is included in the integration settings. Restart the computer if Docker asks you to, and launch the app to confirm it is running.
- 4
Open Windows Terminal with Your Distribution
Open Windows Terminal and start the Linux distribution you installed in the previous step. All remaining commands run inside that environment, not in the standard Windows command prompt. Keeping the terminal open in this context avoids path and permission confusion later.
- 5
Clone the Sandbox Repository
Inside the Linux terminal, clone the project from github.com/algorand/sandbox with Git. Then follow the instructions for Ubuntu and macOS in the repository documentation, since the Windows path builds on the same steps. Read the README before running anything, so you understand what each command starts.
-
Start and Check the Environment
Run the startup command described in the repository README and wait for the containers to finish launching. Confirm that the Algod and Indexer services are running. If a command fails with a pseudo-TTY error, note the message and check the repository issues for the current recommended approach.
System requirements
- Windows 10, latest available version; older versions may not work properly
- WSL 2, which the documentation recommends
- Docker Desktop, latest version, with WSL2 as a prerequisite on Windows
- Git for Windows, latest version, for copying the repository
- A restart after installing Git, WSL2 and Docker so Windows recognizes the new software
How to use Algorand Sandbox
Once the environment is installed, using Algorand Sandbox is mostly about starting it, checking it and keeping your project connected to it. The steps below assume you have completed the installation and are working from the Linux terminal inside Windows Terminal.
- Open Windows Terminal and start your Linux distribution.
- Move into the folder where you cloned the sandbox repository.
- Run the startup command from the README and wait until the containers report that they are ready.
- Check that Algod and Indexer are both running before you connect your application.
- Point your development tools at the local endpoints, then deploy a small test contract to confirm the setup works.
- When you finish, stop the environment so containers do not keep consuming memory and processing power.
Starting with a small contract is a practical habit. If it deploys and returns expected results, you know the node and indexer are working before you debug your larger application.
Pros & cons
- Free and open source, with the code available on GitHub
- Bundles Algod and Indexer so you can start with a complete local stack
- Documented setup for Windows, macOS, Linux and Docker
- Recently updated code, with the last update in August 2026
- Local environment makes repeated testing faster and more predictable
- Windows setup depends on Docker Desktop and WSL2, which adds several installation steps
- Several restarts may be needed before Windows recognizes the new software
- Commands that require a pseudo-TTY can fail with an error, according to the documentation
- Focused on a local development environment rather than a ready-made desktop application
- Less suitable for anyone looking for a graphical interface
Is Algorand Sandbox safe?
Sandbox runs on your own computer and uses Docker to start its components, so treat it like any developer tool. Download the repository only from the official GitHub page at github.com/algorand/sandbox, and get Git and Docker only from their official sites. If a release provides a SHA-256 checksum or signature, check it before you install or run the files. Never enter a seed phrase on a third-party website, and do not move mainnet keys into a local test environment. Before you start, check the latest version on the official GitHub page and keep Docker updated.
- Official source only. Download from github.com/algorand/sandbox. Ignore ads and lookalike domains.
- Check the SHA-256. Compare the installer hash with the value the developer publishes before running it.
- Never share your seed phrase. No developer, support agent or website — including CryptApps — will ever ask for it.
Alternatives
Sandbox sits at a specific point in the Algorand workflow. It is about running the local node and indexer, which is different from the broader development focus of AlgoKit, a CLI for building on Algorand more generally. If you want a single starting point for projects, AlgoKit may fit better. If you want the underlying environment itself, Sandbox is the closer match.
Testing tools such as Graviton and Algojig focus on checking smart contract behavior. They complement a local environment rather than replacing one. Conduit serves a different role, as a data pipeline framework for moving blockchain data, so it fits later stages of a project. Choose the tool that matches the problem you are solving at each step.
Specifications
- Price
- Free
- Type
- Open source
- License
- —
- Latest version
- —
- Last update
- 6 Aug 2026
- Windows support
- Unverified (Windows mentioned in docs)
- Source code
- github.com/algorand/sandbox
Frequently asked questions
Yes, Algorand Sandbox is free and open source. You can download the code from its GitHub repository and run it on your own computer without a license fee. Your only costs are the time spent on setup and whatever resources your computer uses while the local environment runs.
Yes, the project documentation includes Windows instructions. The setup on Windows relies on Git for Windows, Docker Desktop and WSL2, and the documentation recommends using WSL 2. Expect more steps than on a standard application, plus a few restarts while the components are installed.
In practice, yes. The documentation lists WSL2 as a prerequisite for Docker Desktop on Windows, and it recommends WSL 2 for the sandbox itself. Install it before Docker, enable it as the default version, and make sure your Linux distribution is connected to Docker.
Algod is the core Algorand node software, which stores the ledger and processes transactions. Indexer reads that ledger and organizes data so applications can search transactions, accounts and assets quickly. Running both locally gives you a complete testing environment for applications that read and write data.
It is generally safe when you download it from the official GitHub repository and install Git and Docker from their official sites. Check checksums or signatures when a release provides them. Because the sandbox is a development tool, keep real funds and mainnet keys away from your local test setup.
The code was last updated in August 2026, so the project is actively maintained. Active maintenance matters for developer tools because Docker images, Algorand software and Windows components change over time. Review the GitHub repository before you begin, especially if you are reading this page long after its publication date.
The documentation notes that commands requiring a pseudo-TTY can fail with an error in the Windows setup. This is a known limitation rather than a problem with your installation. Check the repository README and issues for the recommended approach, and confirm that Docker and WSL2 are fully up to date.
Verdict
Algorand Sandbox is a practical choice for developers who want a local Algorand environment with Algod and Indexer already in place. It is free, open source and recently updated, which makes it suitable for ongoing development work. Windows users should expect a longer setup built on Git for Windows, Docker Desktop and WSL2, but the process is straightforward once the prerequisites are in place. If you need a complete local network for testing, it is worth trying.