Every new EDI trading partner has historically meant a small infrastructure project before the real integration work begins: provision an SFTP server or an S3 bucket, secure it, hand over credentials, and maintain it for as long as that relationship lasts. Celigo's native file storage — combined with a Celigo-hosted SFTP server layer — collapses that into something closer to creating a folder. The trading partner gets an SFTP endpoint that lives inside Celigo itself, not a separate piece of infrastructure someone has to stand up and maintain.
At a Glance — Celigo Storage & Hosted SFTP
- Celigo Storage: a platform-managed place to store, organize, and browse files directly inside integrator.io — no external SFTP server, S3 bucket, or third-party file service required
- Hosted SFTP server: a Celigo-managed SFTP endpoint that gives each trading partner their own folder, rather than access to a separately provisioned server
- What it doesn't replace: EDI B2B Manager still handles document types, trading-partner profiles, and transaction mapping — this is the file transport/storage layer underneath, not a replacement for the EDI logic
- Still works alongside AS2/FTP/other SFTP: B2B Manager continues to support existing communication channels for partners who require them
- Referenceable from flows and AI agents: stored files can be pulled directly into integration workflows without a separate retrieval step
What actually changed
Two related capabilities: Celigo Storage gives your integrator.io account a managed file store — create folders at any depth, upload and browse files, and reference that content directly from flows. On top of that, a hosted SFTP server exposes part of that storage as a real SFTP endpoint external parties can connect to. A trading partner who needs to drop a file for you, or pick one up, does it against a Celigo-managed address instead of a server your team provisioned specifically for them.
The practical shift: onboarding a net-new EDI trading partner no longer requires a separate infrastructure decision before the mapping and transaction work can start. The file exchange point already exists — you're creating a folder and issuing credentials, not standing up and securing a server.
What this doesn't replace
This is a transport and storage layer, not a replacement for Celigo's EDI B2B Manager. B2B Manager still owns the actual EDI logic — document types (850 purchase orders, 856 ship notices, 810 invoices, and the rest), trading-partner profiles, and the transaction mapping that turns a raw file into usable data on either side. Celigo Storage and the hosted SFTP server address a layer underneath that: how the file physically gets from the trading partner's system into yours. B2B Manager continues to support AS2, FTP, and externally hosted SFTP connections for partners who need or already use those specific channels — the native option is an addition to that list, not a forced migration off it.
When to use it vs. keep your existing setup
Good fit: net-new trading partner onboarding
For a new relationship where nothing is already built, the hosted option removes a real step — no server to provision, secure, or maintain for the life of that single relationship. This is where the time savings is most concrete: onboarding goes from "set up infrastructure, then configure the integration" to just the integration configuration.
Good fit: consolidating file exchange with existing flow logic
Because stored files are referenceable directly from flows — and from AI agents, per Celigo's own documentation — keeping the file exchange point inside the same platform running the integration logic removes a hop that used to require a separate retrieval or polling step against an external server.
Keep your own setup: partner-mandated infrastructure
Some trading partners' own IT or security policy specifies a particular external endpoint they'll connect to — that requirement doesn't go away because Celigo now offers a hosted alternative. If a partner's security review is tied to a specific server they've already vetted, migrating them provides no real benefit and adds unnecessary friction to the relationship.
Keep your own setup: already-integrated partners
If a trading partner is already exchanging files against your existing SFTP setup without issues, there's no strong reason to migrate them just because a native option now exists. This is squarely a tool for reducing friction on new onboarding, not a mandate to re-architect working relationships.
For the full picture of how Celigo's B2B Manager handles EDI document types, trading-partner setup, and transaction mapping — the layer this storage/SFTP capability sits underneath — see our EDI / B2B capability page.
Frequently Asked Questions
What is Celigo Storage? A platform-managed file store inside integrator.io — folders, file upload/browse, and direct referencing from integration flows and AI agents, without needing an external SFTP server or S3 bucket.
What is Celigo's hosted SFTP server? A Celigo-managed SFTP endpoint that gives each trading partner a folder inside Celigo, rather than access to a separately provisioned server your team has to maintain.
Does this replace EDI B2B Manager? No — B2B Manager still owns document types, trading-partner profiles, and transaction mapping. This is the file transport/storage layer underneath, and works alongside AS2, FTP, or an existing SFTP connection.
When should you still use your own SFTP server? When a partner's security policy requires a specific external endpoint, or when a partner is already integrated against your existing setup with no real benefit to migrating.
Entech Solutions builds and manages EDI/B2B trading-partner integrations on Celigo, including onboarding decisions like this one. See our EDI / B2B capability page, or get in touch to scope a specific trading-partner setup.