Changelog

What shipped, and what we got wrong

Product changes, incidents, and corrections to published figures, in one list. Corrections appear here rather than being applied silently, because a research page that changes quietly is one you cannot cite.

Get change notices

Customers are notified of material changes directly. Anyone else can subscribe to the same notices.

1 / 3
Corrections includedIncidents includedDated, never silent
Aug 2026Product

Scheduled data export to customer-controlled storage

Export to S3, GCS, Azure Blob, or SFTP on a schedule you configure, including the audit trail. Built after a customer pointed out that an export available only on request is not a real exit.

Aug 2026Research

Benchmarks now publish interquartile spread

Previously we published medians only. A prospect said a median without a spread was useless for planning, which was correct. All workflow figures now show the range, and the bottom quartile is materially below the median.

Jul 2026Product

Agent authority ceiling made non-configurable

Payment release, vendor banking changes, permission grants, period close, and statutory filing were previously configurable at the tenant level. They are now fixed. Two customers had enabled one of them; both were contacted and migrated to a person-approved workflow.

Jul 2026Correction

Implementation cost multiple restated

Our pricing study originally reported a median implementation multiple of 1.2×. Recomputing with eleven additional quotes moved it to 1.4×. The earlier figure is superseded and the page is dated.

Jun 2026Product

Point-in-time reconstruction across all subledgers

Previously available for the general ledger only. Now covers AR, AP, inventory, and fixed assets, which is what auditors were actually asking for.

Jun 2026Incident

Read-model rebuild degraded query performance

Three hours 41 minutes on 12 March. Ledger posting unaffected. Post-mortem published; connection ceiling and isolated rebuild capacity added.

May 2026Product

Field-level permissions extended to exports

A field a portal user could not see in the interface was still present in some export formats. Fixed, and every affected customer was notified with the specific exports involved.

May 2026Research

Failure-mode sample expanded to 41 deployments

Previously 33. The distribution of primary causes was stable as the sample grew, which is modest evidence it is real.

What goes in here

Four categories, and two of them are the ones most changelogs omit.

  • Product. Functionality added, changed, or removed, including changes that reduce what the software will do.
  • Correction. Any published figure that changed, with the previous value stated. Four of the entries above are corrections and one is a restatement of a number we had been quoting in sales conversations.
  • Incident. Anything customer-affecting, cross-referenced to the post-mortem.
  • Policy. Changes to terms, privacy, subprocessors, or the authority model.
A research page that changes quietly is a page you cannot cite. Corrections belong in a dated list, not applied in the background.

Why removals are logged too

The July entry above records making the agent authority ceiling non-configurable — a change that reduced what customers could do, and which two of them had actively enabled.

Logging that is uncomfortable and it is the entry most worth having. A changelog containing only additions describes a product that has never reconsidered anything.

Notification

Customers are notified directly of anything material — a removal, a policy change, a correction to a figure they may have relied on. This page is the record rather than the notification mechanism.

Questions

Common follow-ups.

Why are corrections in the changelog?
Because a published figure that changes silently makes every other figure less trustworthy. Four entries above are corrections, including one to a number we had been using in sales conversations.
Do you log things you removed?
Yes, including the July change that reduced what customers could configure. A changelog containing only additions describes a product that has never reconsidered anything.
How am I notified?
Customers are contacted directly for anything material. This page is the permanent record rather than the notification.
Where are incident details?
Summarised here and written up in full on the status page, with cause and fix rather than a note about elevated error rates.
How far back does it go?
To the first customer deployment. Entries are never removed, including ones we would rather not have written.

Four corrections and one removal.

A changelog with only additions describes a product that has never reconsidered anything.