How it works
From infrastructure idea to deployment.
OpxKit gives you the code, decisions and documentation. You stay in control of your account and pipeline.
Six steps
- 01
Choose a kit
Pick a foundation that matches your target architecture and cloud.
- 02
Review the architecture
Read the architecture notes and decisions before you change anything.
- 03
Configure variables
Set region, environment, naming and project-specific inputs via tfvars.
- 04
Deploy
Run plan and apply in your own account using your own pipeline or CLI.
- 05
Customize
Extend modules for your application. The code is yours to change.
- 06
Maintain and update
Follow versioned release notes and upgrade guidance as kits evolve.
What makes an OpxKit different?
- Tested infrastructure
- Deploy and destroy flows are run before a version is released.
- Documentation
- Setup, configuration, deployment and troubleshooting guides ship with every kit.
- Security
- Security-focused defaults and static scanning are part of verification.
- Versioning
- Provider and module versions are pinned, with documented compatibility.
- Reusability
- Modular structure and example configs make kits reusable across environments.
Build less infrastructure from scratch.
Start with a verified foundation and focus your engineering effort on what makes your application unique.