A Tallystone product · available now

CRIMS Guard

Upgrade-regression assurance for CRIMS. Prove that moving from one release to the next preserves every function your business depends on — before it reaches production.

The problem

Every CRIMS upgrade is a risk you cannot see.

CRIMS ships up to three releases a year — versions like 23r2 or 26r1, each with its own patch line — and an instance can sit several versions behind before it moves. The further the jump, the more behaviour has had the chance to shift underneath you.

The risk in every upgrade is the same: something that worked before behaves differently after, and nobody notices until a claim is mispriced or a record goes missing. The differences hide in millions of rows and dozens of screens, which is precisely where manual checking runs out of patience.

CRIMS Guard exists to take that risk off the table — and to take the manual grind of regression checking off your team's plate.

How it works

Two data sets in. A tracked list of regressions out.

You submit two versions

Export database extracts and screenshots from your current CRIMS version and from your upgraded test environment. Drop both into your private, encrypted delivery area — a short manifest tells us which project and which side each belongs to. No connection to your live systems.

We compare, exactly

Tallystone computes a deterministic diff across every table, column, row and screen — then has AI classify each difference as an expected upgrade change or a likely regression, with a written rationale. Version noise never reaches your reviewers.

Your team triages

Each finding lands in your portal, ranked by severity. Your people accept valid changes and confirm real regressions — the decision always rests with you, never the machine.

Fixes tracked to verified

Confirmed regressions move through fix and patch to re-verification against a fresh comparison. Every decision is logged, giving you an auditable record that the upgrade preserved behaviour.

Built for the way CRIMS works

Version-aware from the ground up.

CRIMS Guard understands CRIMS release numbering — year, release (1–3), and patch — so a project is framed the way you actually think about it: moving a named instance from one version to another. Findings, submissions and sign-offs all hang off that upgrade.

And your data stays yours alone. Clients never see one another; each company's extracts, screenshots and findings are isolated by design. More on security and isolation →

Get ahead of your upgrade.

We're onboarding CRIMS clients now, before the rush. Tell us which versions you're moving between and we'll show you what CRIMS Guard finds.

Talk to us