open-infraAWS's APIs, on infrastructure you own.
open-infra is a cloud you run yourself that speaks AWS. The AWS CLI, the SDKs, Terraform and CloudFormation work against it unchanged — accounts, IAM policy, ARNs and errors included — on your own hardware.
Read from the platform's generated coverage registry.
How it works
Your tools talk to one AWS-shaped front door. Every call is signed with SigV4 and decided by IAM policy — the same evaluator for the console and the API — then served by the platform underneath.
What it serves today
Generated from the same registry the project's CI checks against the code and its live probes — never hand-written, so this page cannot claim more than the platform does.
API operations per service
The services with the most operations served.
CloudFormation coverage
Resource types the CloudFormation front door knows.
Accounts, like AWS accounts
Organizations, member accounts with their own 12-digit ids, and each account's resources kept apart — switch role, cross-account trust and resource policies as AWS does them.
IAM is the only authority
AWS-shaped policies on users, groups and roles, AWS's managed policies by name, permission boundaries, MFA — one evaluator for every API and the console.
Your templates, unmodified
Deploy CloudFormation stacks through the CloudFormation API, with change sets, drift, exports and the instance bootstrap tools, or use Terraform's AWS provider.
Services
Every front door and its state. proven is served and checked by a live probe; gated is built but ships off; planned answers honestly that it is not served.
open-infra is honest about maturity: the stable platform services are distinguished from the experimental ones in the project's documentation, and compatibility is described as AWS-shaped behaviour, never as AWS itself or any certification.
Want more?
Install guide, architecture, the full coverage matrix and the source are on GitHub.
github.com/harn3ss/open-infra →