Skip to content
Mergiva logoMergiva M & A Intelligence logo with line-chart and database iconMergivaM & A INTELLIGENCE

The product

One application from the first scan to regulator-ready evidence

Deal-first, not folder-first. In Mergiva, every file, every decision and every signature belongs to a deal. Signatures, stage changes and verified files are written to an append-only, hash-chained ledger.

7

Pipeline stages

Connect, discover, classify, approve, transfer, verify, evidence.

9

Lifecycle stages

Pre-deal to archived, with the regulated gates enforced by a state machine.

16

Roles in four tiers

One vocabulary shared by the gateway, every service and every screen.

49/49

Transfer pairs proven

Every source-to-destination pair, read straight back out of the destination and hashed again. 26 September 2026.

How it works

Seven stages, one deal-scoped record

  1. 1Connect

    Register the systems on both sides of the deal. Credentials are encrypted with AES-256-GCM before they are stored, and each connection can be tested and monitored.

  2. 2Discover

    Scan a source and record each file’s SHA-256, size, content type and last-modified date. The scan feeds the Data Estate Report, a PDF built from real scan data.

  3. 3Classify

    A large language model places each file in your taxonomy and gives it a sensitivity score. Detected personal data is redacted before a classification request leaves your installation, and you choose the model.

  4. 4Approve

    A wave of files moves only after two different people sign for it, each after logging in again. The person who created the wave cannot approve it.

  5. 5Transfer

    A transfer worker written in Go moves each file in chunks and records every chunk it completes. After a crash it resumes from the last good chunk.

  6. 6Verify

    Every file is read back out of the destination and hashed again. A mismatch fails the file and holds the wave at FAILED; it never reports success over an unverified file.

  7. 7Evidence

    Each step is written to a hash-chained ledger that database triggers keep append-only. Closing a wave requires its compliance report.

Discover and classify

See what the estate holds before anything moves

Discovery tells you what exists. Classification tells you what it is. Together they turn an unknown estate into a list of files you can scope, sign for and move in batches.

Discover

  • Scans Amazon S3, Azure Blob Storage, Google Cloud Storage, MinIO, SharePoint Online, SFTP and local or NAS sources.
  • Records each file’s SHA-256, size, content type and last-modified date.
  • Feeds the Data Estate Report, a PDF built from the scan’s real data.
  • A scan that fails shows its reason, so your team can fix it and run it again.
  • Allowed from pre-deal through the TSA period, so diligence can start before signing.

Classify

A pharma taxonomy of eight categories

GxP-ClinicalGxP-ManufacturingGxP-RegulatoryPHIPIIFinancialLegal-AntitrustOther

Sensitivity, scored 1 to 5

  1. 1Public
  2. 2Internal
  3. 3Confidential
  4. 4Restricted
  5. 5Highly Restricted
  • AI-assisted by default. Microsoft Presidio redacts detected personal data before a sample leaves your installation.
  • You choose the model for each AI feature, and whether calls go to Anthropic with your key or through your own AI gateway.
  • A wave’s file scope can be narrowed by classification category and sensitivity, as well as by path, file type and size.
How AI classification works

Find waste first

Redundant, obsolete and trivial files, before you pay to move them

Waste detection is an optional module. It reports; it never deletes.

Redundant

Identical SHA-256 within a deal. The oldest copy is kept as the original.

Obsolete

Untouched for longer than a threshold, by default three years.

Trivial

Empty files, known junk names, and non-documents under 1024 bytes.

  • It reports and never deletes. The service has no delete route.
  • Files under legal hold or a retention policy are shown but never counted as reclaimable.
  • A file that is both redundant and trivial is counted once in the reclaimable total.
  • Thresholds can be changed per installation and per scan through the API.

Deal lifecycle

The deal’s stage decides what the platform allows

A deal moves through nine stages, and each change of stage carries the signatures the default gate profile requires. No wave can start before Integration: the wave planner asks the deal’s stage first, and refuses if it cannot get an answer. So antitrust separation is a control rather than a policy people promise to follow.

  • Pre-deal

    Discovery and classification. No wave can start.

    Created by the deal team.

  • Diligence

    Discovery continues. No wave can start.

    One signature: the deal lead or corporate-development lead.

  • Antitrust gate Sign to close

    Discovery continues. Nothing moves to the acquirer.

    Two signatures: the deal lead or corporate-development lead, and antitrust counsel.

  • Day 1

    Clean-team access ends automatically. Waves start at Integration.

    Two signatures: the deal lead or corporate-development lead, and the IMO lead.

  • Integration

    Wave migrations begin.

    No signature: automatic, or started by the IMO lead.

  • TSA

    Waves continue until the services agreement ends.

    One signature: the IMO lead.

  • Closed

    No new wave can start. The records stay.

    Two signatures: the IMO lead, and the CIO or a tenant administrator.

  • Archived

    Kept for its records. The ledger can still be re-verified.

    No signature.

  • Terminated

    Every deal-team assignment ends. No new wave can start.

    From any stage, two signatures: the deal lead or corporate-development lead, and antitrust counsel.

Regulated signature slots, such as antitrust counsel, cannot be filled by an administrator standing in for the required signer.

Waves

One wave: approve, execute, verify, report

  1. 1

    Plan

    Choose the source, the destination and the file scope. A draft can be edited until it is submitted.

  2. 2

    Sign

    Two different people sign, each after a fresh login. The wave’s creator cannot approve it.

  3. 3

    Transfer

    The Go worker moves the bytes in chunks and resumes from the last good chunk after a crash.

  4. 4

    Verify

    Every file is re-read at the destination and hashed again. Any mismatch fails the wave.

  5. 5

    Close

    Closing requires the compliance report. Cancel and reopen are e-signed. Each step is written to the ledger.

Wave states

DraftPending approvalApprovedRunning / PausedCompletedClosedFailedRolled backCancelled
  • A wave can start only in the Integration or TSA stage. The planner asks the deal’s state machine first and refuses if it cannot get an answer.
  • Signatures use a fresh RS256 token from your Keycloak, checked against its published keys and valid for 300 seconds.
  • Two distinct signers are enforced by the service and by a unique index in the database.
  • A failed wave rolls back what it wrote at the destination, and each failed file raises an exception for a steward.

Integrity

Re-read at the destination, hashed again

A checksum the sender calculates only proves the sender did its arithmetic. Mergiva reads each file back out of the destination and hashes it again, and a wave never reports success over an unverified file.

  1. 1. Hash at discovery

    SHA-256 of the source bytes as they are read.

  2. 2. Transfer

    The worker copies the file to the destination in chunks.

  3. 3. Re-read and hash again

    The file is read back out of the destination and hashed.

  4. 4. Compare

    The two digests must match.

  5. Match

    A file-verified entry is written to the ledger with both digests.

    Mismatch

    The file fails, the wave is held at FAILED, and an exception is raised.

Operations

Run it day to day

Reports

A Data Estate Report as a PDF from real scan data, and a compliance report when a wave closes. Reports can be scheduled daily, weekly or monthly and e-mailed through your mail relay.

Notifications

E-mail through your SMTP relay; Slack and Microsoft Teams through incoming webhooks. Every notification is logged with its delivery status.

Exceptions

A failed transfer raises an exception on its own. Stewards retry, skip or accept it, with a written reason. An AI suggestion is advisory and limited to the roles that triage; a person decides.

Retention

Policies with a fifteen-year default, applied to a wave’s verified files in one step, and per-file legal hold with a reason and an accountable user. Managed from its own screen or the API.

Roles

Sixteen built-in roles in four tiers

The roles are built in. An installation uses all sixteen or a smaller profile, and there is no runtime role editor, so a change to a control goes through your change control.

Platform

Platform adminTenant admin

Deal leadership

Deal ownerIMO leadDeal leadCorporate development leadWorkstream lead

Operations

StewardReviewerOperator

Restricted

Clean teamObserverAcquired employeeBuyer representativeAntitrust counselCIO

IMO lead: the lead of the integration management office.

A deal from start to finish

Putting it together: one acquisition, stage by stage

The seven stages repeat for every batch of files. Around them sits the deal itself, which decides what is allowed at each point. This is how a typical acquisition runs through the platform.

  1. Before signing

    See the estate before you plan anything

    A deal starts in the Pre-deal stage, where the work is discovery: no wave can start yet. Register the seller’s systems, run a Data Estate Scan, and every file is recorded with its SHA-256, size, content type and last-modified date.

    AI classification then places each file in your taxonomy and scores its sensitivity, and the Data Estate Report turns the scan into a PDF. One signature moves the deal into Diligence, and discovery continues.

  2. Between signing and closing

    The antitrust gate holds

    Entering Sign to close takes two signatures: the deal lead or corporate-development lead, and antitrust counsel. From here discovery continues, but nothing moves to the acquirer.

    This is enforced, not requested. The wave planner asks the deal’s state machine before every start and refuses if the stage does not allow it, or if it cannot get an answer.

  3. Day 1

    The deal closes, with two signatures

    Two signatures move the deal to Day 1: the deal lead or corporate-development lead, and the IMO lead. Clean-team access ends automatically, and each ending is recorded in the ledger. Integration follows, and with it the first waves.

  4. Integration and TSA

    Waves carry the estate across

    Wave migrations begin in Integration and continue through the TSA period. Each wave is planned, signed by two different people, transferred in chunks by the Go worker, then re-read and re-hashed at the destination.

    A mismatch fails the file and holds the wave at FAILED, and a steward decides what happens next, with a written reason. A wave that completes is closed with its compliance report.

  5. Closing

    Archive, and keep the proof

    Closing takes two signatures: the IMO lead, and the CIO or a tenant administrator. No new wave can start after that. The deal is then archived, and its ledger can still be re-verified entry by entry.

Start with one deal.

Judge us on the ledger, not the demo.

Talk to us

  1. 1

    Name the pair

    Tell us the two systems you need to connect. We produce that pair’s evidence before the pilot starts.

  2. 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. 3

    Plan validation together

    Evidence maps, the control inventory and test artefacts, executed with your QA team on your infrastructure.

  4. 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.