Three ways to get an OpenScan.AI explorer stack running for your chain.
All methods deploy the same components — indexer, database, API, and frontend — and all require a synced EVM node with JSON-RPC (see Chain Node Layer).
Methods
Build from Source (CLI)
Clone the repositories and build the services yourself. Full control over versions and configuration — recommended for production and contributors.
Containerized Deployment
Run the pre-built container images with Docker Compose. The fastest path to a working explorer on a single server.
All-in-One Image
A single container bundling every service for evaluation and development. Not recommended for production — see the all-in-one deployment page in this section.
Choosing
| Method | Best for | Effort |
|---|---|---|
| Source build | Production, customization | Higher |
| Container images | Most self-hosters | Medium |
| All-in-one | Local testing, demos | Low |
After Building
- Explorer Verification — confirm everything works.
- Monitoring — keep it healthy.
- Network Upgrades — keep it current.