Introduction

OPSd is a scenario-driven infrastructure bootstrap tool.

It helps teams start from a validated product scenario, edit a manifest that describes the intended shape, and render standard OpenTofu that stays under the team’s control.

What OPSd is for

OPSd is designed for teams that want:

• a faster start than hand-building infrastructure from scratch
• a more honest model than hosted lock-in platforms
• a controlled path from scenario selection to rendered OpenTofu

What OPSd is not

OPSd is not:

• a replacement for OpenTofu
• a black-box runtime
• a hosted control plane that owns your infrastructure

OPSd helps generate and evolve the stack, but the rendered code remains yours.

Start from a scenario

Instead of a blank repository, you begin from a supported blueprint and variant such as:

• backend API + database
• backend API + database + cache
• object storage
• static assets + CDN

Use the manifest as the editable source of truth

The manifest is where supported product-level changes happen. It is meant to be human-readable and stable enough to review before rendering.

Render standard OpenTofu

OPSd renders standard OpenTofu stacks that you can inspect, keep, and continue operating.

Keep a clear exit path

The client keeps:

• the manifest
• the lock file
• the rendered OpenTofu

That means leaving OPSd does not require rewriting the environment from zero.

If you need a provider-by-provider view of supported blueprint use cases and variants, continue with Blueprint Catalog.

Who OPSd is for

OPSd is a good fit for:

• small teams that need a reliable starting point
• consultants or fractional platform engineers who want a repeatable delivery model
• teams that want help getting to a first environment without giving up ownership

Continue with the Installation guide or jump straight to the Quickstart.