ISOMORPH publishes the open standard .laplaspack · v3
Editable, portable AI memory

Own your mind.
Then put it to work.

Every AI you use forgets you — or worse, remembers you in someone else's database. LAPLAS makes your memory an editable, portable file you own; LAPLAS AX serves it to every agent in your org. The model is rented; the memory is owned.

Free to own · no credit card · every answer has a receipt
The real LAPLAS desktop app: the Today view with tasks in motion, projects and their next steps
LAPLAS · own it

Your context, as a graph you keep.

Not notes. Not a chat log. LAPLAS captures what you think into typed nodes, properties, links, and decisions — then recalls it grounded, with the causal chain behind every answer.

Capture once, structured at write-time
A thought becomes a node with properties and links the moment you write it — the structure is the search index.
Recall with receipts
recall_why walks the causal chain — derived-from, supports, supersedes — so you see why it knows, not just what.
A file you own
Everything lives in a local .laplaspack — an open, MIT-licensed SQLite container you can read, sign, export, and leave with.
LAPLAS in light theme — the same Today view: tasks, projects, and recent commits
The real LAPLAS AX console — the Approvals gate: two staged commits (a pricing decision and an onboarding note) waiting for a human, each grounded in sources, with Commit to memory and Discard
LAPLAS AX · serve it

One memory for every agent — with a human at the gate.

AX is the memory plane for your company's AI. Mount your team's packs, run any agent on top — grounded and cited — and let agents propose writes that a human approves into the org's canon.

Desktop → org, one identity
Share a space from LAPLAS with your LAPLAS ID; it lands in the console, mergeable into one org memory — contradictions surfaced, not overwritten.
Agents propose. People approve.
No agent touches memory directly: staged commits, one-click approval, a full audit trail. Trust is a workflow, not a promise.
Any harness, your keys
Memory agent, code reviewer, site publisher — or bring your own contract. Runs are metered, logged, and reproducible.
The file underneath

.laplaspack

Everything above runs on one open, MIT-licensed format: a SQLite container with causal provenance, offline signing, and a formal grammar. Read it with a zero-dependency script. Verify it without a server. Leave with it any time.

founder.laplaspack
## Subscription [[Subscription]]
>>type: offer   >>status: core
>>derived-from: [[Founder Interview]]

$ laplaspack read --why "core offer"
◈ Subscription
   derived-from  Founder Interview
   supports  Pricing Principle
3 ancestors · offline · provenance intact ✓
Manifesto — the free taste of your pack Free
Publish any pack as a grounded concierge for your site: it answers “why you” with a receipt on every claim, and it never makes things up.
Open Manifesto →
Pricing

Own it for free. Pay when it works for your org.

Your memory is yours at $0, forever — pricing starts where serving it to a team does.

LAPLAS· the desktop, for you
Free
Own your memory, locally
$0
  • Unlimited local capture, recall & packs
  • Typed graph, thinks, causal recall_why
  • Export / import — your file, always
  • Manifesto publishing included
Download for Mac
Pro
Sync it, share it, back it up
$19 / month
  • Everything in Free
  • Cloud sync & encrypted backup
  • Share spaces to an AX workspace
  • Priority support
Get Pro
Ships with notarized builds — everything local stays free.
LAPLAS AX· the memory plane, for your org
Free
Evaluate the loop, end to end
$0
  • 100 grounded answers / month
  • Mount packs & merge to an org canon
  • Approvals, audit log, evals
  • Community support
Open the console
Team
Your first agents in production
$49 / month · per workspace
  • Everything in Free
  • 1,000 grounded answers / month · then $0.05
  • Unlimited members — one LAPLAS ID each
  • Org canon: merge, contradictions, provenance
Start Team
Enterprise
Your boundary, our loop

Deploy inside your boundary — custom harnesses & eval gates, security review, SLA. We help compile your org's memory hands-on.

Talk to sales
Bring your own LLM key — included answers cost 40% less. “Rent the model, own the memory,” literally on the invoice.
Prices in USD. Cancel anytime — your memory is a file; export it and walk.
FAQ

Fair questions, straight answers.

Is my data actually local?
Yes. LAPLAS is local-first: your memory lives in a .laplaspack file on your disk. Nothing leaves your machine unless you choose to sync, share a space to a workspace, or publish a Manifesto.
What exactly is a .laplaspack?
A single SQLite file holding your memory: the human-authored source, a typed graph (nodes, properties, links, decisions), and causal provenance. The spec is MIT-licensed and public, with a zero-dependency reference reader — any program can open your pack, with or without us.
Do I need my own model keys?
On AX you can bring your own keys — included answers cost 40% less — or use the metered playground (100 grounded answers a month, free) while evaluating. LAPLAS structures and recalls the memory; whichever model you rent reads it.
Is .laplaspack an industry standard?
Not yet — and we won't pretend otherwise. It's a v3 draft we authored, published in the open under MIT with a reference implementation and a research preprint. Standards are earned; this one is on the table.
What happens if I cancel?
You keep everything. Your memory is a file you already have — export any workspace pack, cancel, and walk. That's the point.
Where does Manifesto fit?
Manifesto is the free taste: publish any pack as a grounded Q&A concierge for your site. It's how most people first see their memory answer for them — LAPLAS and AX are where that memory lives and works.
The thesis

The model is rented.
The memory is owned.