Snap CD

Compose and Orchestrate with Terraform, OpenTofu and Pulumi

Visit website

SubscriptionOpen SourceDevOpsCode13 impressionslaunches Oct 131 comment

>log in to comment

Karl Schriek[maker]· 1d ago
We built Snap CD to replace monolithic Terraform states with modular, event‑driven deployments. It orchestrates Terraform across isolated runners, offers fine‑grained permissions, and lets you trigger runs on commits, output changes, or config edits. Let us know what you think!

Break infrastructure into small, focused modules — each with its own state file, lifecycle, and blast radius. Outputs from any module automatically become inputs to others, so the dependency graph is derived from your configuration itself: no terraform_remote_state glue, no wrapper scripts, no hard-coded CI chains. Changes propagate automatically. A new commit or version tag, a changed upstream output, or an edited module definition each triggers a deployment — a true GitOps orchestrator that keeps everything in sync. Add approval thresholds wherever you want plans to run automatically but applies to wait for human sign-off.

Open Source DevOps Code Workflow automation

Version‑controlled configurations with code review
Full Terraform Provider for managing all resources as code
Hierarchical role‑based access control (Stacks, Namespaces, Modules)
Cross‑state dependency management and drift detection
AI agents with scoped permissions for safe automation

Snap CD orchestrates modular Terraform/OpenTofu deployments with GitOps, runner isolation and AI-driven approval.

for: DevOps teams that manage Terraform/OpenTofu infrastructure and need modular, event-driven deployments.
pricing: freemium

works withTerraformOpenTofuAWSAzure Service BusAzure Key VaultSSO

Key features

6 features of Snap CD

Modular Deployments — Each module has its own state file, lifecycle and blast radius, with automatic input/output wiring.
Event-driven CD — Triggers on commits, version tags, upstream output changes or module edits, with optional approval gates.
Runner Isolation — Runners run in your own infrastructure, keeping cloud credentials out of the control plane.
Fine-grained Permission System — RBAC at organization, stack, namespace and module levels, plus runner and integration scopes.
Non-invasive Orchestration — Runs standard terraform CLI commands; no wrapper CLI or proprietary plan format required.
AI Agents with Guardrails — Event-driven AI missions governed by the same RBAC, with audit trails and approval gates.

Use cases

Deploy a multi-service application where networking, compute and database live in separate Terraform state files.
Automatically apply infrastructure changes when a new Git tag is pushed, with human approval for production.
Run Terraform plans on isolated runners in Azure or AWS to keep dev and prod credentials separate.

Snap CD pricing

from snapcd.io ↗

Community$0Unlimited users · 10 Modules · Core features · Community Support
Lite$60/monthUnlimited users · 20 Modules · Premium features · Community Support
Snap CD Cloud$300/month10 Users included · 100 Modules included · Premium features · Hosted, patched and backed up
Enterprise$300/monthUnlimited users · 100–1 000 Modules · Premium features · Priority support and AI Agents

Snap CD vs alternatives

all alternatives →

	Snap CD	Terraform	Pulumi	n8n	Railway
Best for	Modular GitOps for Terraform	Terraform infrastructure as code	Multi-language IaC	Workflow automation	App & DB deployment platform
Pricing	Freemium	Free	Free	Subscription	Subscription
DevHunt upvotes	1	0	0	0	0
Launched	Oct 2026	—	—	—	—

Snap CD vs Terraform: Snap CD adds modular state files and runner isolation on top of Terraform’s core IaC engine.
Snap CD vs Pulumi: Snap CD focuses on GitOps orchestration and AI-driven approvals, whereas Pulumi provides multi-language IaC without built-in CD.
Snap CD vs n8n: n8n offers generic workflow automation; Snap CD is specialized for Terraform deployment pipelines with state management.
Snap CD vs Railway: Railway deploys apps and databases, but Snap CD orchestrates Terraform modules with fine-grained RBAC and AI agents.

Snap CD FAQ

What's the difference between Cloud and Self-Hosted?+

Cloud is hosted by Snap CD and ready to use immediately; Self-Hosted uses a license key you install on your own server, but both provide the same functionality.

What counts as a 'module'?+

A module is a single Terraform or OpenTofu root module with its own state file; resources inside the module are unlimited.

How do I get a free Community+ key?+

Sign up on snapcd.io, go to Self-hosted licenses and click ‘Get free Community+ key’; one active key per organization can be regenerated anytime.

What happens when my license expires?+

The server falls back to Community defaults (10 modules, baseline features) without hard lockout; renew or replace the key to restore full tier.

How does metered billing work?+

For Cloud only, you pay a base fee plus usage-based charges for additional modules and users, calculated by the time each exists during the billing period.

Summarized by DevHunt from snapcd.io · Oct 8, 2026. Details may change; check the official site.