SELF-MAINTAINING APIS FOR MANAGED SERVICES

Many managed cloud products are built on open source.

Upstream ships every week. The managed versions run months behind.

Stitch finds the features an open-source project supports but the managed version doesn't, ties each gap to the public customer requests asking for it, and carries each fix the provider picks across every surface, in dependency order.

A recorder pen only ever draws what it is given. The line behind it is the part you can check. FIG. 01

THE PROBLEM

The code takes a day. Shipping it takes months.

When a customer asks a managed service for a setting the open source already supports, the same change has to land on every surface the product ships, in order, with production rollout waits between the steps.

Every upstream release that lands without a managed counterpart widens the distance.FIG. 02

Five steel gauge blocks of increasing height standing in a row on a white surface, each one taller than the last. — A row of standards. Each is a fixed length, and none of them can be shortened to save time.FIG. 03

API The setting has to exist in the public surface before anything can call it.

PRODUCTION ROLLOUT WAIT

CLI A flag that reads from the API, released on the download path.

PRODUCTION ROLLOUT WAIT

IaC An attribute in the Terraform or Pulumi provider, versioned and published to a registry.

PRODUCTION ROLLOUT WAIT

SDKs One package per language, each on its own registry.

PRODUCTION ROLLOUT WAIT

Docs The reference page that tells the customer the setting is there at all.

One product's chain. Another ships a console, a Helm chart, an operator. What stays the same is the order.

Today an engineer tracks that sequence by hand.

WHAT STITCH DOES

Three moves.

Finds the gaps

The features an open-source project supports but the managed version doesn't.

Attaches the demand

Each gap is tied to the public customer requests asking for it, so the provider is choosing against real demand rather than a backlog.

Carries the fix

Each fix the provider picks is carried across every surface, in dependency order.

THE LOOP

Detect, Choose, Implement, Propagate.

Demonstration — the states below advance on a fixed sequence, not against live checks.

Detect Compare what the open-source project supports against what the managed version exposes. not started

Choose Every gap arrives carrying the public customer requests asking for it. The provider picks. not started

Implement The change lands in the API first, because every other surface reads from it. not started

Propagate CLI, IaC providers, SDKs, docs — in dependency order, each one gated on the one before it. not started

Every upstream release opens new gaps; the loop runs again.

CYCLE 01

HOW IT RUNS

A command and a cron job. No server, no database.

Provisional — the command names are not final. The shape is: one command reads, one command runs.

$uvx stitch report --provider <managed-service>

$uvx stitch run --issue <tracker-url>

$# or on a schedule, from a GitHub Actions cron job

Nothing of ours to breach

Stitch is a Python CLI you install with uvx, plus a GitHub Actions cron job. There is no service in the middle holding your credentials.

Run state lives in an issue you already own

A run that spans weeks keeps its state as a YAML block in a GitHub, Jira, or Linear issue on your own tracker. You can read it, and you can stop it.

Checks are small sandboxed scripts

Each one calls package registries, container registries, GitHub, Kubernetes, or a cloud API, and answers a single question about the real world.

An olive-drab indexing plunger photographed from above: a spring-loaded steel pin that has to drop into place before the mechanism it holds can move. — FIG. 04 — A detent. The pin drops, or the next move does not happen.

Coding agents write the changes.

They never write the evidence that their own next step is safe.

Each step starts only after a check against the real world passes.

The package is on the registry.

The deployment is live.

The public schema contains the field.

The human approval landed.

A check answers satisfied, unsatisfied, or unknown. Unknown never unblocks work.

THE FIRST PRODUCT

A read-only gap report, built entirely from public sources.

Every gap, who asked for it, and how many days each surface lags. No code access needed. The paid product adds supervised implementation and propagation inside your own repositories.

Specimen — the shape of one line in the report, not a live reading.
Surface	Evidence the next step waits on	Days behind
API	public schema contains the field	96
CLI	release is on the download path	77
IaC	provider version on the registry	61
SDKs	package is on the registry	44
Docs	human approval landed	pending

Request a gap report digitalizedveer@gmail.com

STITCH IS PRE-LAUNCH. THE GAP REPORT IS READ-ONLY AND BUILT FROM PUBLIC SOURCES ONLY.

WHO

Two engineers. Managed cloud, and flight software.

Veer Singh

Cloud engineer, Google Kubernetes Engine.

Will Zhang

Flight software, Amazon Leo satellites.