Are they really open source?

Yes. Every standard library module lives in the public ravionhq/modules repo.

Do I need Ravion to use them?

They're plain Terraform, so use them anywhere. With Ravion you also get typed inputs, plans, approvals, deploys, logs, and metrics.

Yes. Add a YAML definition to your Terraform and it shows up in your catalog.

Networking, ECS, EC2, Lambda, static sites, RDS, Aurora, ElastiCache, S3, CloudFront, Route 53, certificates, and more.

The standard library
for AWS.

30+ production-ready, open source Terraform modules for VPCs, ECS, Lambda, RDS, Aurora, CloudFront, and more. Your developers and agents start with the right defaults on day one. Use them as-is, fork them, or ship your own next to them.

Browse the modules

View on GitHub

Trusted by engineering & platform teams at scale

Every agent rewrites the same Terraform.

Good defaults are tribal knowledge

Encryption, backups, log retention, and IAM boundaries get rediscovered on every new service, and agents guess at them.

Forks drift apart

Every copy gets its own fixes, and upgrades turn into migrations.

Agents improvise infrastructure

Ask an agent for a database and it writes one from scratch, with whatever defaults it guessed.

With Ravion

Start from production.
Customize everything.

Every module is versioned, open source, and exposes nearly every AWS option.

Step 1

Pick a module

The standard library ships with every organization, next to the modules your team publishes.

Replaces Terraform Registry, internal wikis

See all modules

Step 2

Configure with typed inputs

Open source Terraform plus a YAML definition gives you a form, a CLI, and an API. Agents get the same typed inputs, so they stay on your paved road. Change defaults, hide inputs, or fork it.

Replaces copy-pasted Terraform, one-off templates

Step 3

Upgrade on your schedule

Modules are versioned. Nothing changes until you upgrade, and every upgrade is a plan you review.

Replaces surprise breaking changes

Keep the Terraform you have.

Any Terraform or OpenTofu module runs in Ravion as it is.

Keep the Terraform behind your Spacelift stacks. Add a module definition to give developers and agents typed inputs, with plans and applies in your AWS account.

SpaceliftRavion

StackTerraform stack (rvn-stack)

Stack variablesModule inputs

Approval policyApproval gate

Move in three steps

Read the migration guide

Point an rvn-stack module at the repo and directory used by your Spacelift stack.
Configure access to the existing state backend and review the first plan before switching applies to Ravion.
Add module definitions for the Terraform you want developers and agents to reuse.

Module questions

Stop rewriting
the same Terraform.

Provision your first module in minutes.

Start free

Book a demo

Free to start / No credit card / Runs in your AWS account