For anyone who runs a business
Your company, on the record.
Every company already has an operating system. It has never been written down. muniment writes it down as your company system of record, with every fact traced to its source sentence.
Waitlisters hear from us when a harness is available for download.
Thread / renewal
“I own the Northstar renewal.”
Commitment / renewal owner
Maya Chen → owns → Northstar renewal
Source: “I own the Northstar renewal.”The company graph
The business between your tools.
People, organizations, deals, threads, tickets and commitments already connect your business. Your tools each hold a part of it.
Our shared schema writes those connections down, with an append-only event log and provenance for every extracted fact.
Importers fill the graph from Stripe, GitHub, Gmail, Slack and your helpdesk. You start with a read-only key.
- Stripe
- GitHub
- Gmail
- Slack
- Helpdesk
The grooming report
See what needs your attention.
The grooming report reads the resolved graph. It arrives as fast as your API limits allow.
Each finding is a proposal you review and commit. The report on your own data is the demo.
Grooming report / illustrative findings
The same person, separate records.
Maya appears in Stripe, GitHub, Gmail and Slack.
Propose identity merge
Fields nobody reads.
A customer field holds data that no workflow uses.
Propose field retirement
Seats for people who left.
A paid seat remains assigned after a person leaves.
Propose seat removal
Systems that disagree.
The deal says renewed. The support thread says canceled.
Propose record review
Local by design
It runs on your machine.
The local product publishes its source under FSL. You can check where your data goes.
Your data stays on your machine, and the relay carries an encrypted session you chose to open.
When a second person joins, or a workflow has to run without you, the paid console is the next step.
Join the waitlist