Shippeo Retired the Calva AS2 Platform One Partner at a Time With Files.com

Shippeo runs a real-time transportation visibility platform for large shippers and logistics service providers: where every shipment actually is, and when it will actually arrive, across transportation networks.

The hard part of that business is not the prediction. It is the connection. Visibility data only exists if it arrives, and Shippeo does not get to choose how the parties in its network exchange data. They send what their systems can produce, over whatever channel they can operate. Some integrate by API. Most exchange files. And some trading partners in large logistics networks require EDI over AS2, the signed and receipted B2B protocol.

One Hub for Every Interface, and a Separate Platform for AS2

For years, Shippeo answered the AS2 requirement with a dedicated system: Calva, an AS2 platform that ran alongside the rest of the integration estate.

Everything else already ran through Files.com. Shippeo's Files.com site was where partner interface accounts lived, where files arrived over SFTP, FTP and email, and where its Talend ETL pipelines collected the order, event and EDIFACT data that fed the product. By March 2025, that site was handling 6.8 million calls a day, 95% of them SFTP and FTP connections.

Calva was the exception: a second front door outside the Files.com hub and the Talend path Shippeo used for every other file exchange. The platform itself had to be paid for and operated. And whenever a partner's configuration changed or a connection misbehaved, the work happened on a system apart from the tooling and logs the team used all day.

Why the Cutover Had to Run One Partner at a Time

The reason Calva survived so long was the reason AS2 migrations rarely happened at all. An AS2 connection was a bilateral agreement between two companies. Certificates were exchanged, MDN signing and validation settings had to match on both sides, and each side pointed at the other's endpoint. Shippeo's trading partners, warehouse operators and freight forwarders among them, each sat behind their own AS2 provider with its own constraints and questions. A synchronized cutover would have meant coordinating simultaneous changes across companies Shippeo did not control, against production EDI flows that included EDI 214 transport-status messages feeding the visibility product itself.

So the requirement was never just an AS2 endpoint. Shippeo needed an endpoint its partners would see as standards-compliant AS2 like any other, running under Shippeo's own domain and able to take partners one at a time while the rest kept transmitting to Calva. And it needed inbound EDI to land where every other file already landed, so the downstream pipelines would not care which door a message came through.

Files.com was already the answer to that second half.

Shippeo selected Files.com's built-in AS2 to take over the trading-partner flows and retire Calva.

AS2 on Files.com, Partner by Partner

Through 2023 and 2024, the cutover ran one trading partner at a time. Each partner was configured as a Files.com AS2 trading partner, with certificates exchanged and MDN signing and receipt settings worked through with the partner's own AS2 provider, then switched over only when both sides were ready. By March 2024, the first partner, a warehouse operation, was in production on Files.com while the next was still being configured. Calva kept carrying every partner that had not yet moved, and no production flow had to stop for the migration's sake.

On Files.com, AS2 arrived as part of the file system rather than as a separate product. The platform created an inbox, an outbox and a sent folder for each trading partner. An inbound EDI message was decrypted, verified and delivered into that partner's inbox on the same site the Talend pipelines already polled, so an AS2 document entered Shippeo's ETL exactly the way an SFTP upload did. A file dropped in a partner's outbox went out over AS2, retried until delivery was confirmed, and came back with a signed MDN receipt proving the partner received the exact bytes sent.

The Partner That Couldn't Accept 90-Day Certificates

After the migration, one partner-specific constraint still had to be addressed. Files.com rotated a site's SSL certificate automatically every 90 days, and one trading partner pinned Shippeo's certificate on its side and could not support a renewal every three months.

Files.com accommodated that requirement with a customer-managed certificate. Shippeo applied its own two-year certificate to the AS2 endpoint on its custom domain, scheduled the March 2025 change directly with the affected partner, and kept the connection transmitting without 90-day certificate renewals.

Calva Retired, and AS2 Turned Into Routine Work

Every AS2 flow Shippeo needed was live on Files.com by November 2024, and Shippeo decommissioned Calva. A whole platform, and the exception it represented, came out of the estate.

• Shippeo operates and pays for one file-exchange platform instead of two, and retiring the standalone AS2 platform saved money outright.
• The migration finished without a big-bang cutover. Each partner moved when it was ready, and Calva ran until nothing was left on it.
• EDI now carries the same record as every other exchange: each transmission is logged with its MDN receipt on the same Files.com site, so an integration question about an AS2 partner is answered from the same history as any other partner.
• Adding an AS2 trading partner is routine integration work rather than a project on a separate specialist system, and the partner roster has kept growing through 2026.

The larger change is what AS2 stopped being. It had been a protocol hosted on a platform the team did not otherwise touch. Now the pattern exists on the platform they work against all day: exchange certificates, configure the trading partner, and the messages flow into folders the pipelines already read. The next AS2 partner costs a configuration, not a separate platform.

The retirement itself is the transferable part.

A standalone AS2 platform does not have to be replaced all at once to be replaced completely.