Where we stand
The current release, in plain words
How validation works, what connects, what the audit trail covers, and how Mergiva fits your infrastructure.
What the current release covers
Each line below is backed by code and test runs. We will walk your QA and IT teams through the evidence behind any of them.
- Validation
- Built for GxP and designed to align with 21 CFR Part 11 and EU GMP Annex 11. Validation is executed with your QA team, on your infrastructure, using the evidence pack we supply.
- Connectors
- Seven connectors move data today, in any direction, and all 49 source-to-destination pairs have passed against real endpoints. Seven more connect and test today, with transfers on the roadmap.
- Audit trail
- Every state-changing route writes to the hash-chained ledger or carries a written reason why it is not a regulated record: 130 of 147 write to it. A new route that does neither fails the build. A deal’s complete trail exports as CSV or PDF, with every signature and the chain check.
- Signatures
- Every wave is e-signed by two different people, each after logging in again. Stage changes carry the signatures the gate profile requires. Exception decisions are recorded with a written reason in the audit trail.
- Access
- By default, a user can open a deal only while on its deal team. Revoking a user takes effect at the gateway at once, and in every data service within the token’s remaining life, at most five minutes.
- AI classification
- Runs on the model and account you choose, directly or through your own AI gateway. Detected personal data is redacted before a classification request leaves your cluster.
- Backups
- The ledger lives in your PostgreSQL, so your platform’s database backups protect it.
- Clouds
- Runs in your own Kubernetes cluster. The setup command writes the settings for AWS or your own data centre, and Terraform for AWS is included as reference infrastructure.
Start with one deal.
Judge us on the ledger, not the demo.
1
Name the pair
Tell us the two systems you need to connect. We produce that pair’s evidence before the pilot starts.
2
Scan one estate
Run a Data Estate Scan in your own cluster. You get the PDF report and a classification your QA team can inspect.
3
Plan validation together
Evidence maps, the control inventory and test artefacts, executed with your QA team on your infrastructure.
4
Run the first wave
Two signatures, a verified transfer and a compliance report you can hand to an assessor.
Or write to contact@mergiva-ai.com.