wrapper runtime · v1.9
from a script nobody owns
›ctw wrap billing-v1
1exec ./legacy/quote.sh --xml 14.2s exit 7
stderr socket hangup after 12s
retry backoff 4s jitter 0.3 budget 5
2exec ./legacy/quote.sh --xml 11.8s exit 7
retry backoff 9s jitter 0.3 budget 4
3exec ./legacy/quote.sh --xml 9.6s exit 0
schema inferred 14 fields, 2 pinned by contract
✓serve POST /v1/billing.quote openapi 3.1
wrapped in 41.9s · 3 attempts · contract billing-v1@2
to a typed http endpoint
ctw is a wrapper runtime for the parts of your stack that were never designed to be called. Point it at a shell script, a Makefile target, a container build, or a service that only speaks SOAP. It runs the thing, retries it with declared backoff, keeps every attempt on the record, and publishes the result as a typed HTTP endpoint your services can actually depend on.
how the wrap is declared
One file per target. Declare the command, the retry policy, and the contract you promise callers. ctw handles execution, backoff, attempt provenance, schema drift detection, and the OpenAPI document it hands to your clients.
Runs the same on a laptop, in your existing CI job, or as a long-lived service in a private environment.
1target: billing-v1
2exec: ./legacy/quote.sh --xml
3retry:
4 budget: 5
5 backoff: exponential
6 on: [exit != 0, stderr ~ "hangup"]
7serve:
8 route: POST /v1/billing.quote
9 contract: billing-v1@2
10 auth: oidc
11observe:
12 emit: otlp
Push, schedule, webhook, or an HTTP call from another service.
The wrapped command runs in an isolated step with captured streams.
Failure classes you declared get backoff and a fresh attempt. Everything else fails loudly.
The successful result becomes a versioned endpoint with an OpenAPI document.
the part that pays for itself
Flaky targets stop being an on-call problem. ctw retries inside the declared budget, records why each attempt failed, and only pages you when the failure is new.
target attempts recovered paged
billing-v1 412 38 0
inventory-csv 31 9 0
web-api build 188 4 0
pdf-render 97 12 1
flake budget 12% · spent 3.1% · window 24h
integrations · runs inside the ci you already have
ctw is a single binary. It does not want to be your scheduler.
"post": {
"operationId": "billingQuote",
"x-ctw-attempts-max": 5,
"x-ctw-source": "legacy/quote.sh",
"responses": { "200": {…}, "504": {…} }
}
Schemas are inferred on the first green attempt, then pinned. Drift is a build failure, not a 3am incident.
Contract modelbuild executions 8,412 / 25,000
wrapped api calls 1.24M / 5.00M
private envs 2 / 3
overage none
Build executions, wrapped calls, and private environments are counted separately, so a chatty endpoint does not price like a build farm.
How metering workspricing
Metered on build executions, wrapped API calls, and private deployment environments. No seat tax. The binary is free forever on a laptop.
$0 forever
The binary, local wraps, and one hosted endpoint.
$140 per month, then $0.004 / execution
For a build farm you inherited and a handful of wrapped legacy targets.
from $1,900 per month, committed volume
Your VPC, your egress rules, your compliance auditor.
Executions are counted on completion, not per retry. Retries inside your declared budget are free.