Solution 01

Developer Templates & CI/CD

Standardize the platform work. Keep developers focused on business logic.

The platform tax

Every new service repeats the same platform work — build, container image, pipeline, infrastructure — and every team solves it a little differently. The cost lands later, when one fix has to be reapplied by hand across repositories that no longer look alike.

Templates that keep shipping

  1. 01

    Templates own the platform layer

    Build, container, pipeline, and infrastructure patterns live in reusable templates instead of in the last repository someone copied.

  2. 02

    Composition, not a starter kit

    OpenPlate assembles a project from several parameterized templates, so independent concerns stay independent.

  3. 03

    Ownership stays explicit

    Generated projects record which files the template still owns, so updates ship without overwriting application code.

  4. 04

    The same action everywhere

    OpenCICD runs a project’s own actions in containers, so a step behaves the same on a laptop as in CI.

Inspect it yourself

OpenPlate

Apache-2.0

Generates a project from composed templates and keeps it updatable afterwards. Implementation, documentation, and history are public.

github.com/Comcast/OpenPlate

OpenCICD

Apache-2.0

Turns a project’s own action configuration into container commands. Public and inspectable.

github.com/Comcast/OpenCICD

Built on these tools

Career record

Reusable Docker, .NET, AWS SAM, GitHub Actions, and Terraform templates built against both projects and used by delivery teams.

All solutions

Contact

Submission is not yet available.