Where Weredi runs: hosted in Montréal, built to keep your orders moving

Your trading partners don’t care which server your EDI runs on. They care that the order is acknowledged on time and the ship notice arrives before the truck. That depends on infrastructure you never see, so here it is.

Hosted in Canada, in Montréal

The Weredi platform, its database, your EDI documents and their encrypted backup copies are hosted by Amazon Web Services in its Canada (Central) region, in Montréal. Our AWS organization is locked to that region by policy, so nothing can be created elsewhere, even by mistake.

Weredi is based in Montréal, and our privacy practices are written with Québec’s Law 25 in mind. A few specific services we rely on, such as card payments and sign-in with Google or Microsoft, are run by their own providers; each one is named on our legal page.

Built to survive a failure

Every piece of hardware eventually fails. The question is what happens next. An AWS region is made of separate data centres called availability zones, and Weredi is spread across two of them.

Backup copies are also locked when they are written: neither the platform nor a script running on it can alter or delete them before they expire. And a backup only counts if it restores, so we test restoring both the database and the files.

Watched every minute

An independent monitoring service checks the platform every minute from at least two locations, at least one of them in Canada, and publishes the results on our status page, status.weredi.io.

Those same measurements back our commitment: a monthly uptime of at least 99.9%, with service credits if we miss it. The terms are in the Service Level Agreement on our legal page.

Security in layers

• Encrypted in transit. The application is served over HTTPS, and partners can exchange documents over encrypted channels: AS2, SFTP or FTPS.
• Encrypted at rest. The database, the document storage, the server disks and every backup.
• One locked folder per partner. Each trading partner gets its own file-transfer account, confined to its own folder.
• Documents kept away from the web. EDI files are stored outside anything the web server publishes.
• No open SSH port. Administrative access goes through audited sessions, and every action in our AWS accounts is recorded in an audit trail.
• Stronger sign-in. Users can sign in with a passkey, and account owners and admins see a log of the account’s security events.

Changes are rehearsed first

Production has a twin: a staging environment in its own, separate AWS account, built from the same scripts. Every change is deployed and tested there first, and goes to production only once a person approves it.

Questions