Zero-Copy Stops at the Company Line

The largest enterprise-software platforms spent this fall making the same promise in slightly different words: stop copying your data from system to system, and let software — increasingly, autonomous agents — read it where it already lives. The pitch has a name now, "zero-copy" data sharing, wrapped in talk of a unifying data fabric. It's a genuinely good instinct. It's also one we've been building on from the start — and it runs out at a boundary most of the announcements step carefully around.

An old instinct, newly fashionable

For years the default answer to "our systems don't talk" was to copy everything into one more system — a warehouse, a lake, a central database that becomes the place everyone re-keys into. Zero-copy is the quiet admission that this never really worked: every copy is a second version to reconcile, a fresh place for data to drift out of sync, and one more set of books someone has to trust. Reading the fact where it lives, instead of duplicating it, is the whole premise behind moving metadata rather than archives. Seeing the biggest platforms converge on it is less a surprise than a confirmation.

What the fabric gets right

The architecture underneath these announcements is sound where it applies. Instead of a nightly export that's stale by morning, a data fabric lets one system reference another's current state directly — so an agent acting on an inventory level, a schedule, or an authorization status is acting on what's true now, not on a snapshot. No second copy means no reconciliation and no drift. That's exactly the discipline autonomy needs: software can only take the next action safely if the picture it's reading is live and singular. On this point, the market and ATG agree completely.

Where the fabric ends

Here's the boundary the announcements tend to glide past. These fabrics knit together systems that sit inside one vendor's gravity — its own products, its partner clouds, a consortium that has already agreed to cooperate. Inside that perimeter, zero-copy is elegant. The moment a fact has to cross into a company you don't control — your carrier, your subcontractor, your specialist, your payer — the fabric stops. Not because the technology fails, but because the other party was never going to join your data fabric. They have their own system of record, their own vendor, and their own reasons not to expose their books to a customer or a competitor.

The company line is the actual problem

And the company line is where document-heavy operations actually break. A single business's internal silos are, by now, a largely solved problem; plenty of tools stitch those together. What stays broken is the hand-off between independent parties — the gap where status goes dark, where the same fact gets re-keyed by someone who can't see the first entry, where everyone waits on a phone call to learn what's already true somewhere else. A data fabric that assumes everyone shares one won't cross that gap, because its central assumption — common ownership, a common platform — is precisely what's missing between companies.

A neutral layer, not a bigger fabric

Veritas by ATG applies the zero-copy instinct where it's hardest: across the company line, between parties who share nothing. It moves the fact — a status, a milestone, a document reference — without duplicating anyone's archive, and it belongs to none of the parties it connects. Each side keeps its own system of record; no one is asked to pour their data into a counterparty's fabric. That neutrality isn't a nicety. It's the only arrangement independent companies will actually adopt, which is why a shared layer has to be owned by no one to work at all.

The line to hold

Zero-copy is the right idea, and it's encouraging to watch the whole industry arrive at it. But read the announcements closely and the boundary is always the same: inside the walls. The connective problem worth solving lives outside them — between the companies that will never merge their systems and still have to act on the same facts. Moving the metadata, not the archive, across that line, on neutral ground, is the part no fabric reaches. It's the part we build.