lode.
Lode · the data house

Run your company
from your deck.

One brain per vessel. Twelve chapters that render every document, every surface, every stakeholder view from one source of truth.

↗ Start your vesselSee pricing
Why Lode

One source, every surface.

The brain

Twelve chapters, one source

Identity, narrative, product, market, business, finance, people, brand. Every brain field carries provenance. Every document renders from the snapshot.

The graph

P2 is your CRM

One person, many relationships, many vessels. The cross-vessel signal that a per-vessel tool literally cannot see surfaces on your morning queue.

The matrix

Permission is data

Investor sees Slide. Founder sees Slide + Live + Ops. Accountant sees CH10 only. One Postgres resolver. Every RLS calls it. Edit a row, access flips.

Tiers

Pick your altitude.

founder

Founder

49/mo

One vessel. The brain that maintains itself.

See more →
builder

Builder

149/mo

Up to 3 vessels. Real machinery.

See more →
studio

Studio

399/mo

Unlimited vessels. Portfolio brain.

See more →
From the manifesto

Building Lode.

Manifesto

The deck that maintains itself

Founders shouldn't update three artifacts to ship one update. One brain, every surface follows.

10-6-2026 · 4 min read
Inside the brain

Why the graph is the CRM

One person, many relationships, many vessels. The cross-vessel signal a per-vessel tool literally cannot see.

6-6-2026 · 5 min read
Engineering

The matrix as data

Permissions aren't code. They're a row in `grant_templates`. Edit, and the resolver responds.

30-5-2026 · 6 min read