Portland, Oregon · Developer tools

Everything runs at your place.

Kettlepipe Dev is a pod of six small developer tools — a local-first sync engine, conflict resolution, offline auth, schema migrations, CLI scaffolding and a usage dashboard. Install the SDK once and they run side by side on your own machine.

Install the SDK See the tier board

Enamel kettle steaming on a food cart counter — Six carts, one power line — and all of it on your machine.

Six carts, one pod.

All of it on your machine

Cart 01 · Flagship

The Kettle

Local-first sync engine

Syncs both ways
Keeps working with the wifi off
Your box does the talking

Cart 02

The Fixer

Conflict resolution

Two edits, one answer
Merges before it overwrites
Nothing lost in the middle

Cart 03

The Doorman

Offline auth

Keys stay on the machine
Sign in on the plane
The door opens either way

Cart 04

The Movers

Schema migrations

Tables move house
The app keeps serving
Old and new shapes together

Cart 05

The Starter

CLI scaffolding

New project, one line
Batteries in the box
No config treasure hunt

Cart 06

The Meter

Usage dashboard

See what's ticking
Counted where the data lives
Read it on your own screen

Row of food carts under striped scalloped awnings in a Portland cart pod — The pod on a Saturday: six windows open, everyone working side by side.

The order window

Say it at the counter. It's on in a minute.

One command brings the whole pod down to your machine. The sync engine takes the heavy lifting; the other carts queue up behind it — conflicts, offline auth, migrations, scaffolding and the meter.

Order · two lines, no queue

$ npm i kettlepipe $ npx kettlepipe init

First line installs the SDK. Second line scaffolds the pod on your machine and wires the carts together.

Today's specials

Three short ones — a screen you'll meet on the job, written up like a kitchen ticket and handed over the counter.

Ticket 01Offline auth

The phone keeps working with the signal gone.

A developer steps away from the desk and keeps editing. The keys were made on the machine that owns them, so the door opens without a round trip. When the signal comes back, the work lands where it belongs.

Hands holding a phone at a food cart counter in the evening

Keys stay on the machine · sign-in works offline

Ticket 02Schema migrations

Tables move house while the app keeps serving.

Migrations run in the back, cart by cart, without pulling the shutters down. Old and new shapes sit at the same counter until everything has moved over.

Old shape · new shape · no downtime

Ticket 03Usage dashboard

The meter ticks on your side of the counter.

Syncs, conflicts and migrations, counted locally and drawn on one board you can read at a glance. Counted where the data lives, read on your own screen.

Syncs · conflicts · migrations · all local

The tier board

Chalked up on the A-frame.

Three ways to order. Take one cart if you're shipping small, or take the whole pod and stop thinking about it.

Kettlepipe Dev — today's board

Everything runs locally

One cart

Sync and sign-in, no fuss.

Local-first sync engine
Offline auth

Pick this tier

Half the pod

Sync plus the messy parts.

Local-first sync engine
Conflict resolution
Schema migrations

Pick this tier

The whole pod

Every cart, every line.

Everything in half the pod
CLI scaffolding
Usage dashboard

Pick this tier

Pick your cart at the window — the SDK walks out with you.

Collect your order

Take the SDK home and open the pod.

Two lines at the counter and the carts are yours. Keep your data where it already lives, keep the keys on your machine, and keep working when you're offline.

$ npm i kettlepipe · $ npx kettlepipe init

Install the SDK Back to the tier board

Kettlepipe Dev is a Portland, Oregon developer-tools outfit. The pod runs wherever your laptop does.