💡Key concepts

Core Resourcely objects and concepts

Core concepts

Resourcely has three primary concepts: Blueprints, Guardrails, and Resources.

Blueprints

Customizable templates created and managed by central teams, used by developers to configure and deploy infrastructure. With Blueprints, combine expert guidance with an automatically generated, rich UI.

Blueprints use a templating language that creates a form for developers to interact with and generate Terraform. Developers follow a guided experience, and Terraform is generated that meets your expectations.

Blueprints are

Guardrails

Policies built for infrastructure, embedded into your developer workflows. With Guardrails, define rules that are enforced as part of your existing CI pipeline and expose those rules to developers as part of Blueprint forms. Build highly custom workflows, take context into account, and route Terraform that violates your Guardrails for approval.

Guardrails are written using Really, Resourcely's powerful policy-as-code language.

Finally, give developers feedback and context when they are making configuration decisions instead of after by integrating Guardrails with Blueprints.

Resources

Blueprints are published into a service catalog that is discoverable, searchable, and taggable. One or many Blueprints can be added to a shopping cart by developers for use. After developers fill out a Blueprint form, Terraform is generated and a change request is added in your change management system of choice.

Developers can track the status of their PRs through the Resources menu, and even edit resources they have created using Resourcely.

Who does what

Every organization is different. Sometimes, a security team is responsible for writing infrastructure patterns (Blueprints). Other times, a security team wants to only manage rules (Guardrails).

= Sometimes

= Usually

Platform, SRE, InfrastructureSecurity, IAM, Networking, FinOpsDevelopers

Write Blueprints

Write Guardrails

Configure infrastructure with Resources


Last updated