Software for the parts of family law that have to be exactly right.

Case management for family mediation, from the first MIAM to a bundle a court will accept. Aequis keeps one continuous record of a case, so the work a mediator does in the first week still stands up when a solicitor files in the ninth month.

• Court-form continuity across C100, C1A, Form A and D81, with the MIAM four-month rule checked rather than assumed.
• Confidential addresses are separated into a C8 schedule automatically, not left to whoever is typing.
• Mediator-to-solicitor handover behind two gates: automated continuity validation, then a named solicitor's endorsement under FPR 2010 Part 17, with their SRA number on the record.
• An append-only activity log, each entry checksummed, so the history of a case cannot be quietly rewritten.
• Every table carries its own access rules in the database, and case data needs a two-factor session to reach it at all.

The training side of the same platform, for practices bringing mediators through accreditation. Trainees learn on the software they will qualify into, without ever being one misconfigured permission away from a real family's case.

• Trainee records, supervision, and CPD logging with an export a portfolio reviewer can read.
• Training accounts are held apart from live case data by the database itself, not by a check in the browser.
• Assessment and course enrolment handled in the same place as the practice's own billing.

A document vault for firms and their clients, built so that we cannot read it. Everything is encrypted on the client's own device before it leaves it; our servers hold ciphertext and anonymous structure. A breach of our database reveals nothing readable, and neither does a member of our staff.

• Keys are derived on the device from the client's own passphrase, with a recovery key they print and keep.
• Release to the people they nominate needs several of them to agree — two of three, by default. The agreement threshold is cryptographic: no number of people short of the threshold can open the vault, and nor can we. A waiting period and the client's refusal are enforced in the database rather than by the encryption, and the screens for them are still being built, so today a release is arranged with us rather than self-service.
• Sharing is only to a person whose key has been checked out of band, by reading a safety number to each other.
• A tamper-evident audit log that records what happened and never what was in it.
• Hosted in the United Kingdom. The firm's own brand, on the firm's own address.

A consumer product on the vault engine: a person's life story, their wishes, letters to particular people, and the papers their family will need, released to the people they choose when the circumstances they set come to pass.

• The engine is built and live; the product is not. The release mechanism it depends on is finished and tested; the rest — the writing journeys and what a bereaved family sees — is specified and not yet built.

Mediation on its own, for mediators who do not want a case-management platform. The same engine as Aequis cut back to one job, as an app from the usual stores rather than a workspace to sign in to.

• Specified and not yet built. Nothing is deployed at the address above.
• The same choice over records as Aequis: held on the mediator's own device, or in AegisGate Vault where we cannot read them. That choice is the point of the product, not a setting inside it.