Where Weave runs, and what it keeps.
How Weave reaches your two systems, who can see what, and what is stored.
Where it runs
The application and its scheduled jobs run on Vercel in Frankfurt (fra1). The database is PostgreSQL on Neon in Frankfurt (eu-central-1). Every provider is on the sub-processors page.
Signing in to Weave
Microsoft work accounts only, through Entra ID. Weave holds no passwords. Signing in proves an address; a person sees a company's data after an administrator adds them, as an admin, an operator or a viewer.
One company, one scope
Every query that runs for a customer is restricted to that customer in the data-access layer. A new customer is rows in the database, on the same reviewed code.
Reaching Business Central
Weave signs in as its own Microsoft Entra application, with the permission sets you assign it, and talks to the API pages its own extension publishes. Every posting names Weave's application user.
Reaching the warehouse
The clients that read Ongoing can only read: one sends only GET requests, the other carries a fixed list of read operations. Writes go through one separate list of named operations (put an article, put a purchase order, put an order and a few more) with its own credential. The one cancel is a sales order a person deleted in Business Central before picking started, and only when you switch that on.
Confirmed before it writes
Anything run by hand is a dry run until confirmed, and writing to a production connection takes a second, separate confirmation.
Credentials
Credentials for the connected systems are encrypted at rest with AES-256-GCM, with the key held apart from the database. They are kept out of command lines, committed files and logs, and redacted before anything reaches the audit log.
The record
An audit log of every request Weave made to either system and the answer it got. Every call from outside, such as Business Central asking whether the warehouse has started an order, is authenticated with a key per customer and logged.
What it keeps
What Weave needs to post each event once and to explain recent work: warehouse events, postings, exceptions and the audit log. Business Central keeps the posted documents and Ongoing the warehouse history. Finished records are deleted after a retention period you set, 90 days by default and at least 30, once you switch deletion on. Sales history used to check returns is kept up to three years from the sale.