Open source & experiments.

Eight open-source tools behind our approach, plus source-available jury.

Our tools share one purpose: make good engineering repeatable across projects. Jig gives agents a consistent working environment. Jig-skills puts our engineering practice into focused workflows with clear evidence standards. Epicd coordinates their work. Batter, alongside Runledger and Runlimit, provides the shared foundation for our Rust backends.

/

jig-sh

Rust MCP Receipts Work gates Encrypted vault
github.com/bpcakes/jig-sh

A consistent working environment for coding agents. Jig makes each repository explain how it works: where the code belongs, which commands to use, and what needs to pass before work is finished. It records the results of those checks and keeps shared tooling current as projects evolve.

jig-sh  ·  the working environment
├─ context                  repository guidance and conventions
├─ commands                 a shared way to operate each project
├─ checks                   an explicit definition of done
├─ evidence                 recorded results of the work
└─ updates                  shared tooling that stays current
/

epicd

TypeScript Codex Beads Engineering lead In development
github.com/bpcakes/epicd

An autonomous engineering lead for agentic development. Epicd coordinates coding agents, investigates failures, and carries scoped work through implementation, independent review, and verification. It keeps the history and decisions needed to resume interrupted work. Within Pancake Studio, it is the intended lead for an agent run, with people setting direction and retaining oversight.

epicd  ·  delivery model
├─ plan                     choose how to approach the work
├─ coordinate               assign and guide coding agents
├─ review                   independent checks and repair
├─ verify                   check the result against the scope
└─ resume                   retain decisions across interruptions
/

jig-skills

Codex Evidence standards Rust Swift TypeScript Privacy audit
github.com/bpcakes/jig-skills

Our engineering practice, written for agents. Jig-skills turns the methods we use for planning, code review, refactoring, and privacy checks into focused workflows. Each skill defines what to investigate, what evidence to collect, and how to report the result. Our engineers use that structure to direct agents and judge their work across projects. It is a core part of our approach to reliable, AI-native engineering.

jig-skills  ·  engineering practice
├─ jig-rust                 refactor · architecture · async · security · SQL · tests
├─ jig-ruby                 behavior-preserving Ruby and Rails refactoring
├─ jig-swift                Swift 6 · SwiftUI/UIKit · concurrency-aware cleanup
├─ jig-typescript           simplify · types · React hooks, state, APIs, tests
├─ jig-review               independent Claude, Codex, and Cursor review passes
├─ jig-exec-plans           write · improve · delegate checked-in ExecPlans
└─ jig-privacy-audit        claims · data flow · crypto · leakage · retesting
/

batter

Rust Backend foundation
github.com/bpcakes/batter

The shared foundation for all our Rust backends, designed with coding agents in mind. Batter gives developers and agents a consistent way to work across projects, leaving more room to focus on what makes each product useful.

/

runledger

Rust PostgreSQL SQLx 5 crates
github.com/bpcakes/runledger

A durable PostgreSQL-backed job queue and workflow engine for Rust. Applications supply concrete handlers and a database; Runledger provides a persistent queue, lease-based workers and retries, cron schedules, and workflow DAGs with dependencies, fan-out/fan-in, results, continuation, replay, and external human or API gates. State lives entirely in PostgreSQL, so there is no separate broker to operate. A read-only terminal UI gives operators a live view of queue metrics, jobs, workflows, and definitions.

runledger  ·  workspace
├─ runledger-core            public contracts, traits, types
├─ runledger-postgres        SQLx persistence · queue · DAG
├─ runledger-runtime         supervisor · worker · scheduler · reaper
├─ runledger-tui             read-only queue + workflow operator console
└─ runledger-test-support    ephemeral PostgreSQL · scoped test utilities
/

postgres-test-harness

Rust PostgreSQL 18 Testcontainers Framework-neutral crates.io
github.com/bpcakes/postgres-test-harness

A fast, framework-neutral PostgreSQL integration-test harness for Rust. It starts a PostgreSQL 18 container or connects to an existing server, applies each distinct migration set once, caches the resulting template by fingerprint, and clones a fresh isolated database for every test. Applications keep their normal SQLx, Diesel, or tokio-postgres clients and migration entry points. Concurrent tests get separate databases, while bounded connection and cleanup work keep the suite predictable.

postgres-test-harness  ·  test lifecycle
├─ server                   owned PostgreSQL 18 container or external host
├─ fingerprint              content-addressed schema + migration identity
├─ template                 migrate each distinct schema once
├─ clone                    fresh isolated database per concurrent test
├─ client boundary          SQLx · Diesel · tokio-postgres · custom
├─ prewarm                 optional bounded pool of pristine clones
└─ cleanup                 safe drop · backpressure · failure reporting
/

runlimit

Rust Rate limiting PostgreSQL GCRA 5 crates
github.com/bpcakes/runlimit

A framework-neutral Rust library for keyed rate limiting. Runlimit provides anchored fixed windows in bounded process memory or across PostgreSQL-backed replicas, plus a process-local GCRA backend for continuously replenished quotas. Atomic multi-key checks prevent partial quota consumption, HMAC-derived subject keys keep raw identities out of storage, and shadow mode lets a policy warm up before enforcement. Optional crates add Axum/Tower admission middleware and typed HTTP rate-limit fields.

runlimit  ·  workspace
├─ runlimit-core            policies · HMAC subject keys · decisions
├─ runlimit-memory          bounded fixed-window + GCRA storage
├─ runlimit-postgres        replica-safe SQLx/PostgreSQL backend
├─ runlimit-axum            caller-controlled Axum/Tower middleware
└─ runlimit-http            framework-neutral RateLimit fields
/

syrup-rail

Rust Subscription billing PostgreSQL 18 NMI 4 crates
github.com/bpcakes/syrup-rail

A reusable Rust toolkit for subscription billing. Syrup Rail models enrollment, snapshotted terms, entitlements, cancellation, discounts, automatic renewal, dunning, and terminal non-payment without taking over a host application’s authentication or fulfillment. Its PostgreSQL layer provides the canonical schema and SQLx orchestration, including fail-closed transaction boundaries and replay-stable events. Optional NMI crates add a lifecycle adapter and a bounded, retry-free raw HTTP client.

syrup-rail  ·  workspace
├─ syrup-rail               domain types · lifecycle policy · entitlements
├─ syrup-rail-postgres      PostgreSQL 18 schema · SQLx orchestration
├─ syrup-rail-nmi           NMI gateway · lifecycle-evidence adapter
└─ syrup-rail-nmi-client    bounded, retry-free raw NMI HTTP client
/

jury

Rust Linux Secrets vault Pre-alpha Elastic-2.0
github.com/bpcakes/jury

An experimental portable secrets vault exploring fresh approval for each governed action. The design lets an encrypted vault travel with a Git repository while private identities stay outside it. Governed access binds signed approvals and witness contributions to a specific item revision and action. A Linux CLI works with a self-hosted juryd witness daemon. Pre-alpha and unsuitable for real secrets; it has not had independent security review. Source-available and free to self-host under Elastic License 2.0, which restricts third-party hosted or managed services exposing a substantial set of jury’s features.

jury  ·  experimental access model
├─ portable vault           encrypted artifact · versioned in Git
├─ private identity         local storage outside the repository
├─ approval                 signed decision for an exact action
├─ witness                  contribution to a governed open
└─ receipt                  verifiable signed decision evidence

An internal tool.

Proprietary. Not for sale, not open-sourced.
/

LandingAtlas

Rust Axum TimescaleDB Tera React admin
Proprietary · internal & client use

A multi-site landing-page engine for A/B tests, used in-house and on client engagements. One Rust service routes each request by Host header, renders the matching Tera template, assigns a sticky variant cookie, and writes events to TimescaleDB. A same-origin React admin shows experiments and results; the server runs a chi-square test for homogeneity. Declaring a winner makes its template the site’s runtime default and stops further assignment for that experiment.

landing-atlas  ·  capability map
├─ multi-site routing       Host header → template + asset bundle
├─ variant assignment       weighted, sticky per-visitor cookie
├─ conversion tracking      first-party JS · cookie-validated
├─ statistical analysis     chi-square · p-value · lift over control
├─ winner publication       promote variant to runtime default
├─ admin console            React UI · Basic Auth · same-origin API
└─ preview links            signed URLs survive process restarts