FAQ

Connectors and coverage#

Which ERP is supported first?#

NetSuite is the first connector, and today it is the only one. Which connector is built next is decided by what people actually run and ask for, and the ERPs on that list are Odoo, SAP Business One, Dynamics 365 Business Central, QuickBooks and Xero. None of them has a connector yet, and no date is published for any of them.

Does every ERP connector include the same data?#

No. Record, file, configuration and history coverage depends on the ERP, the connector, the account permissions and the data available from the source. Each connector has its own coverage.

What decides how much a connector can see?#

The ERP identity you authorize. A connector reads the records, files, configuration and source history that identity is allowed to read, and nothing beyond it.

History and recovery#

How far back can history go?#

Playback uses the history the ERP exposes during backfill, plus the changes captured after the connection was made. Events the source never recorded or never exposed cannot be reconstructed.

What does history playback mean?#

Playback is a best-effort reconstruction from capturable data. It can show captured versions and the differences between them, but it is not the same as rewinding an entire ERP database to an exact second.

Is the archive the same thing as history?#

No, and they are delivered separately. The archive is the retained copy of the data. History is the timeline of captured versions over that copy. Recovery is putting something back. Each makes its own promise.

Storage and access#

Where are archived files kept?#

In hosted storage by default. Approved S3-compatible destinations can be connected as additional targets, each pinned to a region, and configured together with you.

Does the archive write back to the ERP?#

No. Archive, history and read-only SQL access do not write to the ERP. Two-way sync between platforms is a separate product with its own rules and approvals.

Is SQL access read-only?#

Yes. SQL and OData access are read-only, with administrative, filtered and scoped access profiles. A separate restricted API covers integrations that do not need SQL.

Is the access log on by default?#

No. Access recording is off by default. Nothing is recorded, and nothing appears in the access log, until it is switched on. See Access log.

What security or compliance certifications are held?#

None today. Work is under way toward SOC 2 and the other certifications customers commonly ask for, and that list expands as demand reaches new frameworks.

Pricing and limits#

How is pricing counted?#

Per connected ERP account rather than per user, so adding teammates does not change the bill.

Does the access log count against my storage?#

Yes, and this catches people out. Access log entries live in the tenant database and count against the same single database allowance as your captured history. A longer retention window can fill that allowance without capturing a single extra record. See Usage and limits.

What happens when I pass an allowance?#

Capture keeps running and the extra is billed, unless you have set a budget limit of your own. A limit is the way to say you would rather capture stopped than be billed for the overage.