01/Studio

Small Team. Serious Software.

We design and build databases, proxies, queues and backend systems, for clients and in the open.

Start a project See the work

02/Work

What We've Built

All projects

Our own projects, all open source under Apache 2.0. Each one has its own site, and its code and releases are on GitHub.

01Database · C

AltSql

A native hybrid of key-value and SQL, from the sensor to the gateway. Both ends share the same records, byte for byte.

altsql.com GitHub

02Database · Go

HyperCrux

SQL, key-value, graph and vector in one native database, kept in a single SQLite file.

hypercrux.com GitHub

03Job queue · Go

Ukue

A job queue in one file, with retries, delayed jobs and dead letters built in.

ukue.com GitHub

04Stream data · Go

Precomputing

Answers kept ready as data arrives. Counts, percentiles and summaries stay current in a SQLite file.

precomputing.com GitHub

05Web server · Go

BareProxy

The operating system for your web traffic: a small Go kernel with sandboxed WebAssembly plugins on top.

bareproxy.com GitHub

06Networking · Go

VPN Works

The VPN, rebuilt as an operating system. Each program gets its own network path, policy and record.

vpnw.com GitHub

07Dev tools · Go

Preconfiguration

Ready machines for coding agents. Describe a project’s setup once, and preconfig writes each agent platform’s setup file and tests it on a clean machine.

preconfiguration.com GitHub

08Browser tools · JavaScript

KeyValueStore

Free tools for the key-value stores you run: Redis, Valkey, DynamoDB and etcd. Nothing you paste leaves your browser.

keyvaluestore.com GitHub

09Schema migrations · Go

ForgeSchema

PostgreSQL migrations with every step and its SQL laid out first, applied in one transaction and verified after.

forgeschema.com GitHub

10Render cache · Go

RenderCache

Fully rendered copies of a JavaScript site’s public pages, kept on your own server and served to crawlers.

rendercache.com GitHub

11Database · Go

RollupDB

An aggregate database. It keeps the statistics you declare for years, in one file, and lets the raw events go.

rollupdb.com GitHub

12Monitoring · Go

RadarModel

Watches the models your app depends on and tells you when one changes underneath it.

radarmodel.com GitHub

13Shared execution · Go

TaskFused

Runs duplicate requests once. Equal requests join one durable operation and share its result, even when a worker crashes.

taskfused.com GitHub

14Record and replay · Go

CodeInstances

Keeps a run of any program as one file, replays it offline, compares runs and shrinks a failure to what causes it.

codeinstances.com GitHub

15Event ordering · Go

Inorderly

Turns events that arrive late, twice or out of order into one sequence that comes out the same every time, byte for byte.

inorderly.com GitHub

16Forkable state · Go

Multivergence

Lets a program fork its state into weighted branches, rule them out as facts arrive, and promote the one that wins.

multivergence.com GitHub

17Workflow kernel · Go

FlowChassis

Runs multi-step jobs inside your own program and picks them up where they stopped after a crash.

flowchassis.com GitHub

18Query optimizer · Go

LQO

Finds the PostgreSQL queries a planner setting makes clearly faster, by trying them on a replica.

lqo.net GitHub

19CI benchmark gate · Go

jvq

Fails a pull request when it makes the benchmarks slower than their budget, and stays quiet within the noise.

jvq.net GitHub

20Seed data reconciler · Go

Bootstrapping

Keeps the reference data an app ships with up to date on every release, without undoing what admins changed.

bootstrapping.org GitHub

21Context reduction engine · Go

Abbreviatory

Turns long test runs, logs, diffs and API responses into short reports that keep every failure, within a byte budget.

abbreviatory.com GitHub

22Explainable key-value store · Go

XKV

A key-value store that records who changed each value, why, and which earlier change caused it.

xkv.org GitHub

23Software repair toolkit · Go

Aftermarket

Fixes HTTP traffic between a client and a service you can’t change, with rules you can read.

aftermarket.dev GitHub

24HTTP timing and file transfer tools · Go

BitSpeed

Shows where an HTTP request spent its time, and moves a file so an interruption never costs the verified part.

bitspeed.org GitHub

25Binary format engine · Go

EByte

Describe a binary format once, then read it, write it back byte for byte and see where a file breaks the description.

ebyte.org GitHub

03/Services

What We Take On

How we work

Most jobs fit one of these. Plenty mix two or three.

Prototypes and MVPs

A working first version you can put in front of users or investors. We find the smallest build that proves the idea, and build that first.

Backend Systems

Services and command-line tools, mostly in Go. Tests and release builds start with the first commit.

Data and Storage

Embedded databases, key-value stores, job queues and precomputed views, sized for anything from a sensor to one honest server.

Network and Edge

Reverse proxies, tunnels, traffic rules and plugin systems, including sandboxed WebAssembly plugins you can write in any language.

Extra Engineering Hands

We join your team for a feature or a migration that has stalled, and work in your repo by your conventions.

Open Source Upkeep

Release pipelines, binaries for each platform, changelogs and docs, so a project keeps shipping without anyone babysitting it.

04/Process

How a Project Runs

The same four steps every time. You see working code early, and you see it often.

Scope

A call, then a short written brief that says what it must do and how we’ll know it works.
Prototype

A small working build early on, so decisions get made on something you can run.
Build

Short cycles, each ending in a version that runs. You see the repository the whole time.
Hand Over

Code, docs, binaries and an automated release pipeline. You own all of it, and we stay reachable.

05/Notes

From the Studio

All notes

Releases and test results from our projects, with links to each project’s own post and its code.

Aftermarket

Have Something to Build?

Tell us what it has to do and what it runs on. We’ll reply with questions first, then a plan and a rough size.

Email the studio Contact page

[email protected]