Tome · what your platform would run on
Tome is the platform we build on. The hard parts are already built.
Logins, permissions, payments and courses already run in production, so your budget goes to the part only your business does.
Most operations run on rented parts: a spreadsheet that became the system, a plugin for members, an app for payments, another for courses. Each one solved a problem the day you added it. None of them is yours, and none of them knows about the others.
We learned what that costs around 2021. A client’s community, built on the industry-standard stack the vendors recommend, met a quarter-million visitors on launch day, fifteen to twenty thousand of them logging in at once. It went down in an instant.
You inherit every failure point in software you don’t control.
The vendors whose parts buckled wouldn’t touch it, and it was our build. So we stopped assembling other people’s parts, built our own foundation and called it Tome.
One foundation under the whole operation.
Tome is one foundation for the parts every operation needs: who your people are, what they’re allowed to see, what they’ve paid and what they’ve learned. The Commerce, CRM & Marketing, Learning, Directory and Community engines sit on top, all sharing one record.
It does what the rented parts couldn’t. Permissions follow your org chart. Money moves between accounts with every change on the ledger and nothing left half-finished. Courses enforce their own prerequisites. Each of those was a wall we kept hitting on WordPress before we built it.
Because everything shares one identity model and one audit trail, a new capability already knows who your people are, what they’re allowed to do and what needs recording.








Take identity, the foundation the rest stands on. A member’s identity is kept separate from their login, so a lost or changed login never takes their history with it. Permissions follow the org chart. Sessions, two-factor sign-in and passkeys come built in, and every access decision is recorded, so you can always see who could do what, and when.
That’s the pattern across Tome: a shared foundation and pieces that meet cleanly. Every project we build on it is still custom.
The proof is what it already runs.
Wabbit came first. Then we proved how much Tome could carry. Four very different operations run on it in production today, sharing nothing except the foundation underneath.
An online organization of 150–200 active members, run on one platform.
Eight years old, and it used to run on five to ten rented tools costing about $1,500 a month. On Tome it runs the full order of battle with delegated command, a training academy with prerequisites and certifications, governance where a ban or a senior promotion needs a quorum of signatures, and a live Discord integration.
700+ on the roster · 85+ collections · 50+ access rulesOur own business, and a live city directory.
wabbit.com, the site you’re reading, runs on Tome, along with the Living Library and the course platform behind Wabbit EDU. So does BudFinderKC, a live cannabis-dispensary directory in Kansas City, with its listings, maps and reviews on the Directory engine.
A flight trainer for the genre’s hardest-to-please pilots.
The academy’s accounts, store and affiliate program run on Tome, on the same foundation as Vanguard’s chain of command. The trainer itself reads real flight-stick rigs in the browser and replays every training run step for step, tested by the pilots most likely to break it.
Four things change on a Tome build.
Logins, permissions, governance and training are the hardest parts of a platform to get right, and on Tome they’re already built and running in production. A build from zero spends a year or more on that plumbing before it does anything unique. On Tome the first working piece takes weeks to a few months, and that time goes to the thing only your operation does.
Tome is type-safe from the database to the screen, so whole classes of mistakes are caught before anything deploys, not by your customers. That’s where the performance, the security and the low upkeep come from.
You own your platform’s code and your data, and you hold a permanent license to the Tome parts it runs on. Nobody can raise your price or hold your data hostage. If you ever leave, we help you take the whole thing with you, and we put that promise in writing.
Every build ships with a retainer of about 15% of build value a year, billed monthly. It pays for security patches, platform updates and the next thing your operation needs built. Every Tome update has to pass its checks before it can publish, so keeping your platform current stays routine work. You can end it any time. While it runs, someone who already knows your platform keeps it current.
Tome is more than a simple website or a basic online store needs.
We’ll say so on the call, before you’ve spent a dollar. Here’s how we’d point you.
- A five-page site that brings in leads
Wabbit Static Sites. We build it, and what you pay credits toward Tome if you outgrow it.
See Static Sites → - A site you’d rather run yourself
WordPress and a good designer handle it well. We’ve put the options side by side, with prices.
See the comparisons → - An operation the tools can’t hold any more
That’s the room Tome was built for.
Start with the Sprint →
Is Tome for sale? Yes, most of it.
For years the answer was no: Tome was how we delivered, and the only way to use it was to hire us. The marketplace changed that. Today the block library installs into the Payload project you already have, and some of it is free. Plans are licensed by client site, from a free single-site account up to Studio’s ten sites, and the business engines (CRM & Marketing, Learning, Directory and Community) add on per project.
All of that checks out in the browser. Agency and Commerce are set up with us by design: Agency carries real setup work at a hundred sites, and Commerce touches the payment path, so we’d rather set it up right than hand you a button.
One set of packages is licensed only on request: the operations vertical, built for a large community that runs its fleet, operations and planning on Tome.
What still comes only one way is us: the bespoke build, where we model your operation and shape the platform to it. When we build it, we can host and run it for you too, on a monthly retainer. If you’d rather run it yourself, the code is yours.
We’d rather sell you the workshop than pretend it’s a museum.
Production-grade, observable, ours.
For engineers: the library is about 300,000 lines of strict TypeScript across nearly 60 published packages, served from a private registry we run ourselves.
Every package carries a label you can read before you install it. Stable packages follow semver and run in production. Preview packages are published and supported, but their API can still change between minor versions, so pin the minor. Vertical packages were built for one kind of organization and are licensed on request.
React with GSAP motion; App Router and server components, with client components where they earn it.
WebGL scenes, page transitions and shader blocks on one shared canvas (@wabbit/tome-webgl, running davidbickley.com today), plus a small runtime for game-like interaction and real input devices (@wabbit/tome-engine, Preview).
Each platform adds its own app layer on top. Vanguard’s adds TanStack Query, Zustand, Yjs collaborative editing and Redis.
Better Auth through a Payload adapter, with two-factor sign-in, passkeys and Google or GitHub sign-in built in. Rate limiting fails closed when its store errors.
Payload CMS 3 and the published @wabbit/tome-* packages: identity, content, training, commerce, operations, realtime and 3D, on one identity model and one audit trail.
Next.js and Node, with TypeScript in strict mode in every package.
MongoDB, with media served from a CDN.
Containers on dedicated bare-metal hardware, deployed with Coolify, at a predictable monthly cost.
Compliance is in the schema: data-subject export and deletion are modeled in, security is enforced at the database read layer rather than the interface, and every access decision leaves a trail.
Take the platform for your own build.
The blocks, plans, engines and packs on Tome’s shelf, the same ones every Wabbit platform pulls from.
- BlocksThe composed band library.

- PlansLicensed by client site.

- EnginesCommerce, CRM, learning, directory, community.

- PacksDomain packages, versioned.

Same foundation, either way
Want to build on it? Two ways in.
You don’t have to hire us to get Tome. Most platforms we ship start with a Sprint, and the shelf is open if you’d rather build it yourself.
Have it built
We model your operation and shape the platform to it.
It starts with the Architecture Sprint: about two weeks, $5,000, credited in full if you build. You walk out with a real plan (cost, phases, risks) and a verdict: build, don’t build, or not like this.
Build it yourself
Install the blocks into the Payload project you already have, with one npm install and a free account.
Other Payload kits give you blocks and pages. Tome gives you that, plus the business engines behind them. The block library is open, with real source and live previews, and some of it is free.

