Changelog
All systems operational. Sample uptime over the last 90 days: 99.98%.
Invite investors by type, publish periodic updates and control exactly how much of the workspace each one can open.
The context map became a first-class canvas: add nodes, relabel them, re-link them and choose your own layout.
A four-step activation flow shipped to 100% of workspaces, moving activation seven points.
API, sync workers and search are all operational. Subscribe on the contact page for incident notifications.
Shipping cadence
We publish every release and every incident. Nothing here is rounded in our favour.
0
Releases this year
Roughly one meaningful change per week.
0.00%
Uptime, 90 days
Sample figure, across API, sync and search.
0 hrs
Median fix time
From confirmed report to deployed patch.
0
Unplanned outages
In the last 90 days. Full history on the status page.
Each release is measured against one number we said it should change. When a release does not move its number, we say so in the notes rather than quietly moving on.
Changes shipped per week
Excludes documentation and copy changes.
Activation after 4.9
Onboarding funnel across the release.
−25% from previous step
−38% from previous step
−51% from previous step
−22% from previous step
Release history
5.1 · Investor Updates
Invite investors by type, publish periodic updates and control exactly how much of the workspace each one can open.
Current release
5.0 · Editable Context Map
The map became a first-class canvas: add nodes, relabel them, re-link them and choose grid, radial or clustered layouts.
Six weeks earlier
4.9 · Guided onboarding
A four-step activation flow rolled out to every workspace, moving activation seven points within a month.
Q3
4.8 · Faster search
Query latency down 62% at the 95th percentile after re-indexing the graph store.
Q3
Running right now
The same panels the on-call engineer looks at.
Health
API, sync workers and search all reporting operational.
Sync volume by source over the last 24 hours.
Indexing throughput by workload class.
−25% from previous step
−38% from previous step
−51% from previous step
−22% from previous step
Deployment pipeline: every change passes all four gates.
We send one short email per release and nothing else. Incident notifications are separate and immediate.
Continuously. Anything user-visible is listed here, grouped by release, with connector additions called out separately.
No. Loreflow is hosted, so every workspace is always on the current release.
Marked explicitly in the entry, with the migration path and a notice in-app before the change lands.