# 🏰 EVM Cloud

> Deploy, manage, and scale EVM blockchain data infrastructure — Nodes, RPC proxies, indexers, databases, and networking — on any cloud or bare metal

## Docs

- [Architecture](/docs/architecture): How evm-cloud's Terraform modules fit together to deploy a complete EVM indexing stack.
- [Core Concepts](/docs/concepts): evm-cloud is built around three orthogonal dimensions: **where** your infrastructure runs (provider), **how** compute is managed (engine), and **who** deploys the workloads (mode). Understanding these three choices — and how they compose — is the key to using evm-cloud effectively.
- [Cost Estimates](/docs/cost-estimates): Estimated monthly costs for each deployment pattern. All prices are US East (N. Virginia) as of 2025. Actual costs vary by usage, data transfer, and reserved instance pricing.
- [Getting Started](/docs/getting-started): Deploy an EVM blockchain indexer on AWS in under 10 minutes. This guide uses the simplest example: EC2 + Docker Compose + external ClickHouse.
- [EVM Cloud](/docs): Open-source infrastructure platform for EVM blockchain data. Deploy, manage, and scale a complete data stack — RPC proxies, event indexers, databases, networking, and monitoring — on AWS, GCP, or bare metal with a single command.
- [Outputs Reference](/docs/outputs-reference): Terraform outputs from evm-cloud. Access any output with `terraform output -json <name>`.
- [Roadmap](/docs/roadmap): EVM Cloud is evolving from Terraform modules into a full-stack platform for EVM blockchain data infrastructure.
- [Troubleshooting](/docs/troubleshooting): Common issues and solutions, organized by compute engine.
- [Variable Reference](/docs/variable-reference): All configuration variables for evm-cloud, organized by category. Variables marked **sensitive** are redacted in Terraform plan/apply output.
- [Updating Configuration After Deployment](/docs/guides/config-updates): How to change eRPC, rindexer, and ABI configurations after your initial deployment, for each compute engine.
- [External Deployers](/docs/guides/external-deployers): When `workload_mode = "external"` (or when using `k3s`), Terraform provisions infrastructure only and outputs a structured `workload_handoff`. External deployers consume this handoff to deploy workloads independently.
- [Production Checklist](/docs/guides/production-checklist): A step-by-step checklist for hardening your evm-cloud deployment before running in production.
- [Secrets Management](/docs/guides/secrets-management): How evm-cloud handles credentials across compute engines, and how to manage them securely in development and production.
- [Two-Phase Deployment](/docs/guides/two-phase-workflow): k3s and EKS external mode require a two-phase deployment. This guide walks through the full workflow from provisioning to teardown.
- [Bare Metal + ClickHouse (BYODB)](/docs/examples/bare-metal-clickhouse): Deploy evm-cloud on any VPS or dedicated server. No AWS account required. Terraform connects via SSH and deploys Docker Compose services directly on your host. Works with Hetzner, OVH, DigitalOcean, Vultr, or any server with Docker installed.
- [EC2 + Docker Compose + ClickHouse (BYODB)](/docs/examples/ec2-docker-compose-clickhouse): Low-cost AWS deployment. A single EC2 instance running eRPC and rindexer with your own external ClickHouse database. Best for analytics workloads on a budget.
- [EC2 + Docker Compose + Managed PostgreSQL](/docs/examples/ec2-docker-compose-rds): The simplest evm-cloud deployment. A single EC2 instance running eRPC and rindexer with an AWS-managed RDS PostgreSQL database. No external database required.
- [EKS + ClickHouse (BYODB)](/docs/examples/eks-clickhouse): Production-grade Kubernetes deployment on AWS EKS. Runs eRPC and rindexer as Kubernetes pods with your own external ClickHouse database. Best for teams already using Kubernetes.
- [EC2 External Mode (Infrastructure Only)](/docs/examples/external-ec2): Terraform provisions the EC2 instance and networking, but does not deploy workloads. You get a `workload_handoff` output containing SSH connection details and configuration, then deploy eRPC and rindexer using your own CI/CD pipeline, Ansible, or scripts.
- [EKS External Mode (Infrastructure Only)](/docs/examples/external-eks): Terraform provisions an EKS cluster and networking, but does not deploy workloads. Designed for GitOps workflows where ArgoCD, Flux, or a CI/CD pipeline manages Kubernetes deployments separately from infrastructure.
- [Examples](/docs/examples): 7 ready-to-use deployment examples. Each is a complete Terraform configuration you can `terraform apply`.
- [k3s + ClickHouse (BYODB)](/docs/examples/k3s-clickhouse): Lightweight Kubernetes on a single EC2 instance using k3s. Gets you Kubernetes semantics (Helm, kubectl, pods) without the ~$73/mo EKS control plane fee. Uses a two-phase deployment workflow.