Taking business
into orbit.
From Rust Belt, to Kalahari, to the Cosmos — we pioneer digital and physical tools that help people work and learn.
Babb is an industrial software company and open-source foundry. We build for the working world: individuals, small teams, shop floors, farms, field crews, and operators whose work cannot pause for fragile software. We build on fundamentals — in software, hardware, and the perennial disciplines of communication and commerce — because we are building for a very long time.
Operator autonomy. Individual development. Tools that last because they are built on things that do not change.
We build on the mathematical and structural foundations of communication and commerce — not on the assumptions of the moment. Our protocols encode invariants that have governed trade since Sumerian clay tablets. Our interfaces speak a language older than the internet. We optimize for the long arc.
Every Babb tool is built so the person using it understands it, owns it, and can walk away with their work intact. Open standards, not lock-in. Offline-first, not always-connected. Local-first data, because your records belong to you — not to a platform.
The most lasting contribution a tool can make is improving the capability of its user. Across the Babb suite, capturing and recalling ideas, information, and artifacts from working and playing is woven into every surface — an independent layer that travels with you, under your full control. Our tools go far beyond conventional help: annotated examples, context-rich guidance, and intelligent prompting that builds real understanding over time.
The practices behind Babb's tools are not new. The coordination problems we are solving were first solved in clay and reed. Select a moment.
Uruk, Mesopotamia — the first industrial coordination records
Around 3300 BCE in the city of Uruk, administrators began pressing reed styluses into soft clay to record what arrived, what was issued, and to whom. The earliest known tablet — a beer ration record from around 3300 BCE — shows human heads eating from bowls beside conical vessels, with numerical marks: how much beer, for how many workers. These were not literary documents. They were operational records for a managed workforce. Temple complexes in Lagash deployed over 6,000 laborers in textile workshops, fisheries, grain cultivation, and irrigation maintenance. Each worker's ration was standardized and logged: adults received 30–40 sila of barley per month; children received 20. Scribes recorded daily wage rates, delivery weights, labor assignments, and commodity flows across city-states whose productive capacity depended entirely on the legibility of these records. The transition from clay tokens to written tablets was itself driven by scale: as city populations reached the tens of thousands, three-dimensional tokens stored in envelopes became unworkable. Pressing the token's impression into the clay surface — then discarding the token — was the world's first data compression. Two-dimensional marks replaced physical objects because operations had grown too large for any other method. The logic Babb applies to lean binary records, standardized formats, and offline-first data capture is this same logic — applied five millennia later.
Venice, 1494 — the method that balanced the books of empire
Luca Pacioli's Summa de Arithmetica did not invent double-entry bookkeeping — Venetian merchants had practiced it for two centuries. What Pacioli did was formalize and publish the method at the exact moment the printing press could carry it across Europe. The core insight: every transaction has two sides, and those sides must balance. Debit and credit are not moral categories — they are structural positions in a record that cannot lie without revealing the lie. The method enabled the merchant republics of northern Italy to coordinate trade at scales previously impossible: goods moving between agents in distant cities, multiple currencies, time-delayed settlement, complex partnerships. The ledger became the operating system of early modern commerce. BitLedger, Babb's compact binary transmission protocol, encodes this same invariant at the wire level — not as a rule to check after the fact, but as a structural property of the encoding. A record that does not balance cannot be encoded. Five hundred and thirty years later, the mathematics is identical.
Paris, 1870 — five bits, thirty-two signals, the beginning of binary commerce
Émile Baudot's telegraph code reduced the alphabet to five binary positions — each a combination of electrical marks and spaces. Five bits. Thirty-two possible signals. Every subsequent binary communication standard (Murray code, ASCII, ISO 6429, Unicode control characters) preserved this space, because the constraint is mathematical: five bits is the minimum to encode the Roman alphabet plus basic controls. The telegraph collapsed distance for commerce. A merchant in London could coordinate a purchase in Mumbai in minutes rather than months. Commodity markets, insurance, and modern banking were restructured around telegraphic speed. Baudot's code was also a compression decision: the tradeoff between expressiveness and bandwidth — how much information travels through a constrained channel per unit of cost — is the same engineering problem BitPads addresses today for satellite links, KaiOS devices, and low-bandwidth field operations across sub-Saharan Africa. One hundred and fifty-five years later, three upper bits of Baudot's original C0 control character space remain structurally available — unclaimed by every standard since. The BitPads Enhancement Grammar reclaims them.
Bell Labs, 1969 — the interface that outlasted every successor
Unix was designed under extraordinary constraint: a PDP-7 with 8KB of memory, a small team, no budget. The answers those constraints produced — small composable tools, text as the universal interface, files as the organizing principle, explicit commands rather than hidden state — turned out to be so structurally correct that every serious computing environment since has either adopted them or been forced to explain why not. The terminal is not an anachronism. It is the interface that survived every generation of "simpler" successors, because it models the computer as it actually is: a machine that receives explicit instructions and returns deterministic output. Workwarrior is built on this foundation — not as a nostalgic choice, but because the terminal's composability, scriptability, and transparency make it the correct substrate for tools intended to last. The work ahead is to make that foundation genuinely accessible: to lower the entry cost, to carry the same rigor onto mobile devices and dedicated work screens, and to let the discipline of the terminal inform how software behaves everywhere else.
Rust Belt to Kalahari to Cosmos — the moment Babb was built for
We are in a period of simultaneous reindustrialization and expanding connectivity, where traditional hard work — farming, fabrication, transport, field service, local trade — remains foundational while new infrastructure extends into spaces and regions that previous generations of software ignored entirely. Babb is building for continuity across all of it: old and new infrastructure, local and global markets, terrestrial and off-world operations. The tools we build are rooted in practices that are five thousand years old and designed to operate in environments that did not exist five years ago. The constraint that makes a Sumerian tablet readable today is the same constraint we apply to every protocol: records should be self-describing, minimal, and structurally honest. Every tool should compound the capability of its user. Every standard should be free to implement, maintained openly, and durable enough to outlast the organization that created it. Babb's time has come — not because the problems are new, but because the moment that demands permanent, capable, accessible tools for every operator on every continent has arrived.
Workwarrior
Productivity is personal. Workwarrior unifies the four daily disciplines of real work — tasks, time, notes, and exchanges — into a terminal environment that is composable, scriptable, and entirely yours. It connects best-in-class CLI tools (Taskwarrior, Timewarrior, JRNL, hledger) through a coherent profile system that holds your work context intact across sessions, devices, and collaborators.
Workwarrior represents the building blocks we are putting in place to simplify and strengthen personal and team work from the ground up. The terminal is where we establish the foundations — the data models, the discipline, the composability. From there, the same logic extends onto mobile devices, dedicated work screens, and consumer hardware. The rigor of the terminal travels. The intimidation factor does not.
The learning layer is built in: Workwarrior goes beyond help documentation to provide context-rich guidance, annotated examples, and structured prompting that helps users genuinely understand and improve how they work — not just execute commands.
Workpads
A job-record system built around one durable unit: the single work document. Instead of forcing small teams into heavy software stacks, Workpads keeps the center of gravity where it belongs — on a clear record of what happened, what should happen next, and why.
Workpads is organized around PADS: Processes, Actions, Details, Story. Minimal enough to model real jobs on the lowest-cost mobile devices; structured enough to produce records that integrate with CLI tools and web surfaces without format translation. Job records encode as compact textable strings that self-load on the receiver's end without a data connection — coordination that continues when networks don't.
The phone that costs twenty dollars is already in the hands of 400 million people.
No serious business software exists for it. We are changing that.
KaiOS runs on feature phones without touchscreens, navigated by D-pad, with limited JavaScript runtimes and no PWA support. Networks are intermittent. Data costs money. These are not problems to apologize for — they are the design parameters of a first-class deployment target. Babb embraces every constraint as a forcing function for tools that are genuinely lean, genuinely durable, and genuinely accessible.
Workpads for KaiOS turns these devices into daily employee work tools. Job records are created, shared, and received using standard SMS — no data plan required. A Workpads link travels as a text message and self-loads on the receiver's end. Business coordination continues when networks do not. Our approach positions KaiOS devices as capable enterprise tools that can make entire tool suites redundant for workforces that previously had nothing built for them.
Workpads for KaiOS — coming soon · Follow updates →While Workwarrior and Workpads address personal and team-scale work, Babb's development extends into industrial operations. Clarkware is an on-the-floor manufacturing environment for technicians, supervisors, and integrated services — designed to accelerate production capacity and supply chain coordination in environments where fragile software has no place. It demonstrates Babb's thesis applied at operational scale: the same commitment to legible records, operator autonomy, and durable formats, brought to the factory floor and field operation. Clarkware is in focused development and will be introduced as the industrial layer of the Babb stack as it matures.
Also in the ecosystem: ClarkChat — persistent, type-aware conversation for operations, learning, and automation.
for
Orbit
"From the Midwest to the Kalahari to the Cosmos, Babb exists to help people and businesses lead and endure. The durable tools and technologies that can reliably operate far away are the same ones that faithfully serve Earth's remotest regions. This is our shared oath — to take the common spirit of business up into orbit and beyond."
Read the full Oath →- Apr 25, 2026 BitLedger Protocol v0.1.0 — Initial Release
- Apr 25, 2026 BitPads Protocol v0.1.0 — Initial Release
- Apr 25, 2026 Workwarrior v0.1.0 — Initial Release
- Apr 25, 2026 Workpads v0.1.0 — Initial Release
- Apr 25, 2026 BASICS Standard v0.1.0 — Initial Release
- Jul 16, 2025 What is Workwarrior?
- Mar 14, 2025 Logging Business Events
- Mar 14, 2025 Building for Remote Regions
- Mar 13, 2025 What is Workpads?
- Mar 13, 2025 What is the Times Project?
- Mar 10, 2025 Welcome to Babb!
- Mar 10, 2025 Business Pioneers
Follow the build.
Dispatches are manually posted notes from the Babb team — project progress, field reports, and thinking posted when there is something worth saying. No algorithm. No content schedule.