FACTORY ZERO

FZ-012 · DEVTOOLS

Keep Shipping

Deploy workflows for engineers, as one typed file per repository.

Public beta VALIDATION FZ stackDeploysOpen source
Visit keepshipping.run Launched: 2026-10-15
Status
Public beta
Pipeline stage
VALIDATION
Sector
DEVTOOLS
Autonomy target
LEVEL 4 · SELF-OPTIMIZING
Built with
3 live · 1 planned

The problem

Your deploy pipeline grows into hundreds of lines of YAML and shell that nobody fully understands.

What it does

Keep Shipping is designed to replace this with one typed workflow file per repo, checked before it runs.

How it works

  1. Build images, plan and apply Terraform or OpenTofu, and deploy, as typed steps instead of scripts
  2. Run the exact same pipeline on your laptop before you push it
  3. Let agents ship too: a policy decides what waits for a person

Early access by invite, in small batches.

Stop spending afternoons on eleven commits to change one pipeline.

TodayCLI v0.1.0 is released for macOS and Linux (MIT); the hosted console is in private use.

Aims

Autonomous operation
Deploys are the automation target. One typed workflow file per repository builds the images, plans and applies the infrastructure and rolls out, and it is checked before anything runs, so a broken pipeline is caught on the laptop instead of in the tenth CI run. The same engine runs locally and in CI, so nobody has to push to find out.
Intelligence
Coding agents can write, check and run the workflow, fenced by a policy in the same file: what they may do alone, what waits for a named person. A decide step asks Jev, a typed decision model, how risky a plan is; it answers with one of the answers you defined and a confidence score, low-risk changes can go through, and destroys always wait for a human. The engine itself is plain code.
Growth
Developer-led. An early-access list first, opened in small batches; typed, versioned blocks that one team writes and forty repos reuse carry it inside a company. Pricing is not set. Growth is repositories shipping through it, counted from the first team that is not a pilot.
The technical detail

A deploy workflow engine. Each repository gets one typed workflow file that builds and signs OCI images, plans and applies Terraform or OpenTofu (apply runs the exact plan a reviewer approved), waits for a human where the file says so, and rolls out to Kubernetes, VMs over SSH or serverless. Every step has typed inputs and outputs, so a tag wired where a digest belongs or a misspelled step fails the check before anything runs, and the same engine runs the file on a laptop and in CI. Steps can be packaged as typed, versioned blocks and reused across repos; a step that needs real code is a TypeScript function with typed inputs. For coding agents, a policy in the file says what they may do alone and what waits for a named person, and a decide step asks Jev (TypeSafe AI) to rate a plan, with destroys always going to a human. The CLI v0.1.0 is released for macOS and Linux under MIT, and the hosted console is in private use; the site at keepshipping.run keeps the early-access list, and the engine, the steps and the runner are still being built.

Related

From the same foundation.

All ventures