Stop Copy-Pasting Your CI/CD Pipelines.

Bring native YAML anchors, variables, and cross-file reuse directly to GitHub Actions. Maintain one clean template instead of fighting with bloated, duplicated steps.

Experiment in Progress: We are actively validating market demand with early adopters before finalizing the backend architecture.

What is this?

A drop-in preprocessor for GitHub Actions. It allows you to write DRY (Don't Repeat Yourself) YAML files by unlocking features that the native platform currently restricts.

Who is it for?

Platform Teams and DevOps Architects managing complex, multi-repository GitHub Actions setups who are exhausted by maintaining duplicated pipeline code.

Why should I care?

  • Eliminate Duplication: Stop copy-pasting the same `npm ci` and checkout steps across 50 different jobs.
  • Reduce Security Blindspots: Update a secret or a container image tag in one single template, rather than manually hunting down every instance across your repositories.
  • No Vendor Lock-in: We simply compile your advanced YAML into native GitHub Actions YAML right before the run.

The Spaghetti YAML Problem

Without native anchors, you are forced to repeat job configurations over and over. Reusable workflows help, but they fail when you need deep customization or secure secrets inheritance. Here is the difference our preprocessor makes:

Before (Duplicated & Brittle)

jobs:
  build-linux:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - name: Install deps
        run: npm ci

  build-mac:
    runs-on: macos-latest
    steps:
      - uses: actions/checkout@v3
      - name: Install deps
        run: npm ci

After (DRY & Clean)

.setup_template: &setup
  steps:
    - uses: actions/checkout@v3
    - name: Install deps
      run: npm ci

jobs:
  build-linux:
    runs-on: ubuntu-latest
    <<: *setup

  build-mac:
    runs-on: macos-latest
    <<: *setup

How it works

1

Write Advanced YAML

Author your `.github/workflows` using standard YAML anchors, aliases, and file includes just like you would locally.

2

Automatic Compilation

On trigger, our lightweight integration intercepts the advanced YAML and securely flattens it.

3

Native Execution

GitHub Actions executes the standard, compiled YAML exactly as it normally would. No extra infrastructure required.

Why we're building this.

This project was born out of frustration. After analyzing massive GitHub community threads, we saw hundreds of Platform Engineers begging for basic YAML anchor support—a feature that has been repeatedly ignored by the native platform.

We are building this because we believe your CI/CD pipelines should be a joy to maintain, not a liability of duplicated code. We are measuring demand via this waitlist to ensure this is a problem worth solving before writing the backend logic.

FAQ

Does it have access to my source code?

No. The preprocessing occurs strictly on the workflow YAML definitions, never touching your proprietary application code.

When will it be ready?

We are actively in the market validation phase. If enough teams indicate this is a critical pain point, we will begin the closed beta rollout immediately. Sign up to secure your spot.

Why isn't this a native GitHub feature?

We don't know. The community has asked for it for years, but it remains unaddressed. We decided to solve it today.

Help us shape the syntax.

Join the waitlist today. You'll get early access to the beta and direct input into the architecture before we launch publicly.