About
Loreflow started from a simple frustration: the reasoning behind good decisions disappears into chat threads, call recordings and documents nobody reopens. We rebuild that layer.
Knowledge tools failed because they asked people to write things down twice. The context already exists — it is just scattered across a dozen products. The job is connection, not capture.
A distributed team of 34 across engineering, product, revenue and support, previously building infrastructure and collaboration tools. We run the company on Loreflow itself.
Loreflow is funded by a mix of institutional funds, operator angels and a syndicate of customers. Our investor updates are, unsurprisingly, written in Loreflow.
By the numbers
We are deliberately small and deliberately close to the product. These are the numbers we look at internally, published as they stand today.
0
People
Across nine countries, remote-first since day one.
0
Workspaces
From two-person startups to 400-person scale-ups.
0.00%
Uptime, 90 days
Sample figure, on the API and sync workers together.
0
Years of context
The oldest workspace history we have back-filled for a customer.
We tried the wiki route ourselves and watched it rot. The pattern is always the same: documentation peaks in month one and decays from there, while the real context keeps accumulating in the tools nobody calls a knowledge base.
Distribution measured across our own demo and design-partner workspaces.
Where company reasoning actually lives
Share of captured context by source type.
How we got here
2022 — The internal tool
Built as a weekend script to answer 'why did we decide that' inside our own consultancy. It only read Slack and it was already useful.
First version: 400 lines of Python
2023 — The graph
We stopped treating artifacts as documents and started treating them as nodes with influence. That rewrite is when answers started carrying receipts.
Second rewrite
2024 — Design partners
Twelve companies between 20 and 300 people ran on it for a year. Their edge cases shaped permissions mirroring and decision records.
12 design partners
2026 — Loreflow
Investor updates, an editable context map and guided onboarding shipped. We run the whole company on it, including the page you are reading.
Release 5.1
Inside the team
Our workspace, unfiltered — the same panels you get on day one.
Connected artifacts by team
Loreflow's own workspace.
Context captured over time
Weekly connections, last quarter.
Start a 15-day free trial on any annual plan, connect your first sources and ask Loreflow a question only your company could answer.
Because most decisions lose their reasoning within weeks. Companies do not have a knowledge problem — they have a recall problem.
Small and deliberately senior, working in public.
Startups between ten and two hundred people, usually with a founder who is tired of re-explaining the same context.
The contact page reaches the team directly, and security or procurement questions get an answer within one business day.