A collection of high‑quality, reflection‑driven components that make it EZ4 developers to build modern applications.
TypeScript
11
62 commits
updated Sep 22, 2026
Most engineering teams strive to build solid foundations and deliver value when building production‑ready cloud applications. EZ4's mission is to provide all the tools needed to achieve this with as little friction as possible. It gives you a single unified model to declare infrastructure, connect services, validate payloads, and deploy everything... without YAML, boilerplate, or scattered configuration.
EZ4 treats your TypeScript code as the source of truth for both infrastructure and runtime.
Each component exposes a contract, a strongly typed interface that describes how the resource is created, configured, and consumed. Contracts are provider‑agnostic, composable, type‑safe, and reflection‑driven. They describe both the infrastructure and the runtime behavior of a component, allowing EZ4 to generate cloud resources and local clients from the same source of truth.
| Contract | Local Provider | AWS Provider |
|---|---|---|
| Gateway | Gateway | API Gateway |
| Database | Database | DynamoDB, AWS Aurora |
| Cache | Cache | Valkey |
| Scheduler | Scheduler | Scheduler |
| Storage | Storage | Bucket |
| Topic | Topic | Topic |
| Queue | Queue | Queue |
| Distribution | N/A | CloudFront |
| N/A | ||
| Validation | N/A | N/A |
| Factory | N/A | N/A |
Read the quick start guide and explore the examples to begin.
MIT License
62 commits
TypeScript
98.8%
A collection of high‑quality, reflection‑driven components that make it EZ4 developers to build modern applications.
TypeScript
11
62 commits
updated Sep 22, 2026
Most engineering teams strive to build solid foundations and deliver value when building production‑ready cloud applications. EZ4's mission is to provide all the tools needed to achieve this with as little friction as possible. It gives you a single unified model to declare infrastructure, connect services, validate payloads, and deploy everything... without YAML, boilerplate, or scattered configuration.
EZ4 treats your TypeScript code as the source of truth for both infrastructure and runtime.
Each component exposes a contract, a strongly typed interface that describes how the resource is created, configured, and consumed. Contracts are provider‑agnostic, composable, type‑safe, and reflection‑driven. They describe both the infrastructure and the runtime behavior of a component, allowing EZ4 to generate cloud resources and local clients from the same source of truth.
| Contract | Local Provider | AWS Provider |
|---|---|---|
| Gateway | Gateway | API Gateway |
| Database | Database | DynamoDB, AWS Aurora |
| Cache | Cache | Valkey |
| Scheduler | Scheduler | Scheduler |
| Storage | Storage | Bucket |
| Topic | Topic | Topic |
| Queue | Queue | Queue |
| Distribution | N/A | CloudFront |
| N/A | ||
| Validation | N/A | N/A |
| Factory | N/A | N/A |
Read the quick start guide and explore the examples to begin.
MIT License
62 commits
TypeScript
98.8%