Deploy for a district

Follow this path if you want to deploy Blue Dots for a district, state or domain. It starts with the DPG model, walks the adaptor onboarding journey end to end, then covers installation, deployment, and what district activation looks like on the ground.

1

Introduction

The minimum shared context — what the Blue Dots Economy is and why it exists.

2

Blue Dots as a DPG

Why Blue Dots is built as open Digital Public Goods, and the two DPGs that make up the stack.

3

Adaptor Onboarding

The end-to-end path for an adaptor to stand up Blue Dots for a district or domain.

4

Prerequisites

Tools, runtimes and accounts required to run the Blue Dots DPGs.

5

Local Stack (Docker)

Bring up Postgres, Redis, Keycloak and Mailpit for local development.

6

Deployment

Provision AWS infrastructure and deploy the Blue Dots stack with OpenTofu/Terragrunt and Helm.

7

Activating Blue Dots in a District

The institutional and operational model for how a district government activates Blue Dots in under 90 days.

Go deeper

Infrastructure & Deployment ArchitectureHow Blue Dots is provisioned and deployed — AWS EKS via OpenTofu/Terragrunt, Helm umbrella charts, Kong ingress, and TLS.

ConfigurationHow configuration-as-code works across the Blue Dots DPGs, and where each value lives.

CI/CD & Build PipelineHow code becomes a running deployment — image builds, GHCR, image pinning, and Helm-based delivery.

Prefer browsing? The full documentation map covers every page.