IICY - Infrastructure In Code Ycombinator
A paradigm-shifting approach to infrastructure management where infrastructure is defined alongside service code, eliminating the need for separate infrastructure definitions.
The Problem
Traditional infrastructure management requires:
- Separate infrastructure code (Terraform, CDK, CloudFormation)
- Context switching between service and infrastructure code
- Manual synchronization of infrastructure and service changes
- Complex dependency management between services and infrastructure
The Solution: Infrastructure In Code Ycombinator (IICY)
IICY allows you to define infrastructure directly in your service code using decorators and annotations. A static analyzer extracts these definitions and compiles them into CloudFormation templates.
Key Benefits
- Single Source of Truth: Infrastructure and service code in one place
- Type Safety: Infrastructure definitions are part of the code
- Easier Refactoring: Changes to service code automatically update infrastructure
- Better Developer Experience: No context switching between infrastructure and service code
- Reduced Complexity: No need to maintain separate infrastructure files
How It Works
- Define Infrastructure in Code: Use IICY decorators to define infrastructure alongside your service code
- Static Analysis: The IICY analyzer scans your code to extract infrastructure definitions
- Compilation: Infrastructure definitions are compiled into CloudFormation templates
- Deployment: CloudFormation templates are deployed to AWS
- Service Connection: Service code automatically connects to deployed resources using ARNs and endpoints
Installation
# Create virtual environment
python3 -m venv venv
source venv/bin/activate # On Windows: venv\Scripts\activate
# Install in development mode
pip install -e ".[dev]"
Development
Running Tests
pytest
Author
Blake Smith (blake@dotle.ca)
Release files for iicy 0.2.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| iicy-0.2.3.tar.gz | 51.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| iicy-0.2.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 106.3 kB
Release files / iicy-0.2.3.tar.gz
| Download URL | iicy-0.2.3.tar.gz |
|---|---|
| Size | 51.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bf0646471ce9f7c8b333211c8e8e6b01e3b0db1a01bc56a5b36a1e49631e0c87
|
|
BLAKE2b-256 checksum How to use checksums |
2e7a49e5bdd7474f1d92eabe2bfc22aec005f58db2b5b11b5a542daa19eed31b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 5, 2025.
Transparency logRelease files / iicy-0.2.3-py3-none-any.whl
| Download URL | iicy-0.2.3-py3-none-any.whl |
|---|---|
| Size | 54.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2fd3202eefccbbd8b6c20faf85f9a6109b7481a428bda006ee1f698688ff2f08
|
|
BLAKE2b-256 checksum How to use checksums |
f17f9bb3169d34c8ce17f90ee317a7673dfff762dd49d8928cd31b10a04add91
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 5, 2025.
Transparency log