The platform isn't one app — it's a stack of small, sharp engines. Each does one thing, self-hosted, and they compose. This is the machinery under every Campaign Brain product.
One catalog over every source.
A thin data-federation layer that mirrors datasets from any source — voter files, banking, donations, email — into one registry, normalizes their columns, and gates access with tenant-scoped grants.
Every product reads from one place instead of a tangle of vendor exports; analysts discover and join data that used to live in five incompatible silos.
Plain SQL across the whole platform.
A cross-catalog query layer that runs ordinary SQL — counts, filters, joins — against hundreds of auto-discovered catalogs at once, from voter data to media assets to election results.
Pull a voter count by district, turnout, and demographics in a single query; drive semantic search in chat; materialize an audience without exporting a thing.
Dashboards, composed not coded.
A Bun-native framework for building live data apps — drag KPIs, charts, grids, and maps onto a canvas, wired to real-time streams and saved server-side as JSON.
Field managers watch turf completion, finance directors track the donor pipeline, media buyers read radio coverage — operational views built in minutes, not sprints.
A whole app in one JSON file.
A declarative schema that fully describes a Loom app — its tabs, forms, data sources, and actions — compiled by a generic runtime into a finished, chrome-complete app with zero handwritten boilerplate.
New tools ship as a spec, not a sprint; authors compose them visually and the runtime handles permissions, theming, and tenancy for free.
Text in, sharp graphics out.
A deterministic compiler that turns simple directives into themeable, responsive SVG scenes — one source, rendered correctly across phone, tablet, desktop, print, and TV.
Election reports publish as self-contained files, chat answers come back with charts inline, and every surface looks hand-set at any size.
Any screen, anywhere, live.
A display layer for thin appliances — a Raspberry Pi or a wall TV pulls a Weave-rendered scene and shows it fullscreen, live-updating, with no browser and no client-side logic.
Election-night boards, war-room walls, and fundraiser dashboards that just turn on and stay current — plus live HLS and YouTube streams from the same scene.
The loop that keeps it live.
A runtime for long-lived, stateful services — reconcile loops that wake on a timer or an event, hold their own state, and expose a clean API, so a process can babysit itself.
The live election board that polls for new results, fires a render, and pushes it to every screen — and any other always-on job that has to stay correct on its own.
Every product runs on these seven engines. The catalog is where they show up as tools campaigns actually use.
