Practical overview
When it fits
Use Matic CLI when a Polygon development network needs to be created locally, provisioned through the documented cloud workflow, or deployed onto existing VMs. Choose the local Docker setup for a local test network and express-cli when Terraform should manage AWS or GCP infrastructure.
Who it is for
- Developers who need a local Dockerized Polygon devnet for development or testing.
- Teams preparing Polygon devnets on AWS or Google Cloud with Terraform.
- Operators deploying Polygon stacks onto virtual machines whose infrastructure is already configured.
Documented uses
- Set up a local Dockerized devnet and run its deployment and smoke-test scripts.
- Initialize a Terraform devnet workspace for AWS or GCP.
- Deploy Polygon stacks to preconfigured VMs when infrastructure already exists.
- Configure cloud devnet node counts and Dockerized versus per-node VM layout.
Requirements & limits
- The express-cli workflow is documented for v0.3.x devnet stacks only.
- Cloud provisioning requires provider-specific authentication, Terraform, Node.js v18.19.0, configuration files and SSH key material.
- The local Docker workflow requires operating-system-specific host dependencies; Docker is needed for the Docker setup.
- The repository distinguishes cloud provisioning through express-cli from matic-cli deployment to existing VMs.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Set up a local Dockerized Polygon devnet
Create a local devnet, run the documented deployment script and check it with the smoke test.
Before you start
- Clone the matic-cli repository and install its npm dependencies.
- Install the required host software listed in the README, including Node.js v18.19.0 and Docker for a Docker setup.
- Adjust configs/devnet/docker-setup-config.yaml for the local setup.
Steps
From the repository, create and enter a devnet directory.
Run the documented matic-cli setup command with the Docker setup configuration and wait for the “DONE Devnet is ready” log.
Run util-scripts/docker/devnet_setup.sh.
Run util-scripts/docker/smoke_test.sh to verify the deployment.
Expected outcome
A local Dockerized devnet is set up, deployed and checked with the documented smoke test.
Guide limitations
- The README lists additional operating-system-specific dependencies; check its Requirements section before starting.
- The documented express-cli support is limited to v0.3.x stacks.
Prepare an express-cli cloud devnet
Initialize an AWS or GCP Terraform devnet directory after preparing the documented prerequisites.
Before you start
- Install AWS CLI or Google Cloud SDK, Terraform, Node.js v18.19.0 through nvm, and the express-cli and matic-cli npm dependencies.
- Configure authentication for the selected cloud provider.
- Prepare the required SSH key material and repository configuration files, including .env and secret Terraform variables.
Steps
Set up the provider-specific authentication described in the README.
Prepare the configuration files, key material and allowed-IP settings described in the express-cli requirements.
Run ./bin/express-cli.js --init with aws or gcp to initialize a devnet folder.
Expected outcome
A provider-specific devnet directory is initialized with Terraform and local git-ignored files, ready for the subsequent documented cloud workflow.
Guide limitations
- This guide covers initialization only, not starting or operating the cloud devnet.
- The documented express-cli support is limited to v0.3.x stacks.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 17 October 2026
- Original website title
- 0xPolygon/matic-cli · Official homepage title · retained in its source language