Algorand Sandbox Dev is a Docker-based local environment for developers building on the Algorand network, aimed at people who want a private test setup on their own machine and at engineers who run automated builds. The project is now deprecated and will be archived. Its last code update was on January 2, 2024, and the maintainers point users to the official Algorand images available through AlgoKit LocalNet instead.
The software is free and open source. It was created to speed up local development and continuous integration work, which the project described as suffering from long build times and slow devnet and indexer performance. The documentation mentions Algorand and Komodo and lists Windows, macOS, Linux and Docker as platforms. If you are starting a new project today, read the alternatives section before installing anything.
What Is a Local Algorand Sandbox?
A local sandbox is a private copy of a blockchain network that runs on your own computer or on a build server. Instead of sending test transactions to a public network, developers can deploy contracts, create test accounts and check results in an isolated environment. This keeps experiments cheap, repeatable and separate from real assets.
In the Algorand ecosystem, local networks typically include a devnet, which is a development node, and an indexer, a service that makes past transactions and account data searchable through an API. Both components matter when a test suite queries the chain many times. A slow indexer can make a fast contract test look sluggish, which is why the project focused on those services.
Sandboxes are useful at every stage of a project, but they are most valuable early, when code changes often and public test networks feel too slow for quick checks.
Who Needs a Containerized Test Environment?
Smart contract developers are the most obvious audience. They write code, deploy it locally, and repeat the cycle many times a day. A reproducible environment means that a bug found on one laptop can be reproduced on another machine without manual setup.
DevOps engineers and CI maintainers have a different concern. Automated pipelines need predictable environments that start quickly and tear down cleanly. Running a local network inside a container makes it easier to spin up identical test setups on every commit.
Students and hobbyists can also benefit. A local network lets them experiment with transactions and accounts without worrying about mistakes on a live chain.
Why Build Times and Indexer Speed Matter in Blockchain Testing
Blockchain test suites are often slower than ordinary unit tests because they depend on a running network. Every test may need to create accounts, fund them, submit transactions and wait for confirmation. If the environment takes several minutes to start, the total cost of a test run grows quickly.
Indexer speed affects a different part of the workflow. Tests that check balances, asset holdings or transaction history depend on the indexer returning data promptly. When queries lag, developers may add arbitrary delays to their scripts, which makes tests less reliable.
For this reason, tools aimed at local development are judged mainly by how quickly they start, how consistently they behave and how easily they can be reset between runs.
Key features
Prebuilt Docker image for CI/CD
Targeted devnet and indexer speed
Containers across operating systems
Supported coins
The documentation mentions Algorand and Komodo as supported coins and networks. Developers should treat this list as the starting point and check the project's repository for the current scope.
How to install Algorand Sandbox Dev on Windows
- 1
Install Docker
Install Docker before anything else. On Windows, Docker Desktop includes docker compose, which the project's examples use, so a single installation covers both. Start Docker Desktop and confirm it is running before continuing.
- 2
Download the image from an official source
Download the image only from the official website or the project's GitHub Releases page, or pull it from its official Docker Hub listing. Avoid copies from forums, mirrors or third-party sites. Verify the image digest or checksum where the project publishes one before you run it.
- 3
Start the environment
Open a terminal in the folder that contains the project's compose file and run docker compose up as described in the documentation. Wait until the containers report that they are running, then point your development tools at the local endpoints shown in the configuration.
-
Stop and reset when finished
Use docker compose down to stop the containers when your session ends. Because the environment is disposable, you can recreate it from the same configuration whenever you need a clean start.
System requirements
- Docker, with docker compose included on Windows through Docker Desktop
How to use Algorand Sandbox Dev
This sandbox works best as a local test network for contract deployment and quick checks. Because the project is archived, use it mainly for reference, legacy projects or experiments, and plan migration to a maintained option for new work.
- Start Docker Desktop and confirm that it is running.
- Obtain the image and configuration files from the official source.
- Open a terminal in the project folder and run docker compose up.
- Wait until the containers are ready before sending any test transactions.
- Point your SDK or test runner at the local endpoints listed in the configuration.
- Deploy a small test contract and confirm that it responds as expected.
- Run your test suite and note how long the environment takes to answer queries.
- Stop the environment with docker compose down when the session is complete.
Keep your test accounts and configuration separate from any wallet that holds real funds.
Pros & cons
- Free and open source
- Packaged as a Docker image, which keeps the local setup reproducible
- Designed with CI/CD pipelines in mind
- Documentation covers Windows, macOS, Linux and Docker hosts
- Deprecated, and the repository is being archived
- Last code update was on January 2, 2024, so it no longer receives active development
- Windows support is documented but not formally verified
- Maintainers recommend AlgoKit LocalNet for current work
Is Algorand Sandbox Dev safe?
Algorand Sandbox Dev is deprecated and will be archived, so it is unlikely to receive security fixes. Treat it as a legacy tool and avoid running it on machines that hold valuable keys. Download the image only from the official website, the official GitHub repository or its official Docker Hub listing. Verify the SHA-256 checksum or digest when the project provides one. Never enter a seed phrase on third-party websites, and keep sandbox accounts separate from any wallet that holds real assets. Check the official project page for the latest status before you install.
- Official source only. Download from github.com/MakerXStudio/algorand-sandbox-dev. 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
AlgoKit is a broader command-line tool that the project itself points to as the successor for local networks, through AlgoKit LocalNet. Algojig and Graviton focus on testing contracts rather than hosting a network, so they complement a sandbox instead of replacing it. Conduit handles data pipelines, which places it closer to the indexer side of the stack. Algoml is a language for specifying contracts that compile to TEAL, so it sits earlier in the development process. Choose this sandbox only when you are maintaining an older workflow that already depends on its Docker image.
Specifications
- Price
- Free
- Type
- Open source
- License
- —
- Latest version
- —
- Last update
- 2 Jan 2024
- Windows support
- Unverified (Windows mentioned in docs)
- Source code
- github.com/MakerXStudio/algorand-sandbox-dev
Frequently asked questions
No. The project is deprecated, and the repository will be archived. Its last code update was on January 2, 2024. The maintainers recommend the official Algorand images available through AlgoKit LocalNet for current development.
The documentation mentions Windows as a platform, and the setup runs through Docker Desktop, which includes docker compose. However, Windows support is not formally verified, so test the setup on a non-critical project before relying on it.
Its safety depends on where you get the image. Download it only from the official website, the GitHub repository or the official Docker Hub listing. Verify the checksum or digest when available, and keep sandbox accounts separate from any wallet holding real assets.
Yes, the program is free and open source. There is no licensing fee for the software itself. You still need Docker, which is a separate installation that you obtain from its own official source.
You need Docker installed on your system. On Windows, Docker Desktop includes docker compose, which the project's examples use. After installation, you start the environment from a terminal in the project folder.
The project recommends AlgoKit LocalNet, which provides official Algorand images. AlgoKit itself is a command-line tool for building on Algorand, and Algojig and Graviton are useful for contract testing.
The documentation mentions Algorand and Komodo. Check the repository for the current scope before planning a project around either network, since a deprecated tool may not reflect the latest network changes.
Verdict
Algorand Sandbox Dev is a legacy Docker sandbox for local Algorand development. It is free and was designed to shorten CI/CD builds and speed up devnet and indexer work. Because the project is deprecated and will be archived, it fits mainly developers who already use it and need to keep an older workflow running. New projects should start with AlgoKit LocalNet and the tools listed in the alternatives section.