What does ml-connector cost?

Start on a free sandbox and test against your real systems at no cost. Paid plans begin when you move to production and want a dedicated environment. Start a chat and we will size it against what you actually need to move.

How do you keep my credentials safe?

Every credential is encrypted with a key unique to your environment and is never displayed again after you save it. Logs redact credential fields automatically, and credentials are decrypted only in memory at the moment a flow runs.

How is my data separated from other customers?

Every paying customer runs in a dedicated environment with its own database, queue, worker, and encryption key. The per-customer schema has no tenant column, because there is only ever one tenant in it.

What happens when a sync fails?

It retries automatically, with stricter limits on high-stakes flows such as bills and payments. Records that still cannot be processed land on an errors screen where you can replay them once the cause is fixed.

Can a retry post the same invoice twice?

No. Jobs carry a deduplication key and outbound writes use idempotency keys where the vendor supports them, so a retry or a replay resolves to the same single record.

Do you build the field mappings?

Yes. Complete field mappings are part of what we deliver, not homework handed back to you.

Can flows be triggered by events rather than a schedule?

Yes. Flows run on a schedule, on a verified webhook from the source system, or on demand. Inbound webhooks are signature checked and rejected outright if the signature does not match.

Do I get told when something breaks?

Yes. Alerts can be sent by email when a flow fails or a record needs a person, so you are not relying on noticing a dashboard.

How do I get a human?

Start a chat from any page on this site. For scoping a specific integration with an engineer, there is a paid one hour engineer call.

FAQ

Common questions

The questions people actually ask before they commit, answered straight. If yours is not here, start a chat and a real person will pick it up.

Getting set up

Starting is deliberately low commitment. A free sandbox with no card lets you connect your real systems and run test syncs against them, so the decision is based on your own data rather than a scripted demo. Moving to a paid plan provisions a dedicated environment and puts your flows on a schedule, carrying over everything you built in the sandbox.

Security and your data

Credentials are encrypted before they are stored and are never shown again after you save them. Every paying customer runs in a private environment with its own database and its own encryption key, so your data is not commingled with anyone else's. Every meaningful action is written to an append-only audit trail scoped to your workspace.

Systems and connectors

We catalogue over 1,700 business systems across ERP, accounting, procurement, commerce, payments, EDI, logistics, analytics, and more, with 120 finished connectors available today. Anything not yet built is built as a bespoke connector inside your own environment, which is the normal path rather than an exception.

Running and monitoring flows

Flows run on a schedule, on a webhook from the source system, or on demand. Failures retry automatically with stricter limits on high-stakes flows, unprocessable records land on an errors screen you can replay from, and alerts reach you by email when something needs a person. Retries are deduplicated, so replaying a failure cannot double-post a bill.

Support

Support is a person, not a ticket queue you shout into. The chat on this site reaches us directly, and for scoping work that needs an engineer rather than an answer, there is a paid one hour engineer call.

Common questions

What does ml-connector cost?: Start on a free sandbox and test against your real systems at no cost. Paid plans begin when you move to production and want a dedicated environment. Start a chat and we will size it against what you actually need to move.
Which systems can you connect?: Over 1,700 systems are catalogued and 120 have finished connectors today, across ERP, accounting, procurement, commerce, payments, EDI, logistics, and analytics. If yours is not built yet, we build it into your environment.
How do you keep my credentials safe?: Every credential is encrypted with a key unique to your environment and is never displayed again after you save it. Logs redact credential fields automatically, and credentials are decrypted only in memory at the moment a flow runs.
How is my data separated from other customers?: Every paying customer runs in a dedicated environment with its own database, queue, worker, and encryption key. The per-customer schema has no tenant column, because there is only ever one tenant in it.
What happens when a sync fails?: It retries automatically, with stricter limits on high-stakes flows such as bills and payments. Records that still cannot be processed land on an errors screen where you can replay them once the cause is fixed.
Can a retry post the same invoice twice?: No. Jobs carry a deduplication key and outbound writes use idempotency keys where the vendor supports them, so a retry or a replay resolves to the same single record.
Do you build the field mappings?: Yes. Complete field mappings are part of what we deliver, not homework handed back to you.
Can flows be triggered by events rather than a schedule?: Yes. Flows run on a schedule, on a verified webhook from the source system, or on demand. Inbound webhooks are signature checked and rejected outright if the signature does not match.
Do I get told when something breaks?: Yes. Alerts can be sent by email when a flow fails or a record needs a person, so you are not relying on noticing a dashboard.
How do I get a human?: Start a chat from any page on this site. For scoping a specific integration with an engineer, there is a paid one hour engineer call.

Keep reading

Still have a question?

Start a chat and a real person will answer it. No ticket queue.

Start a free workspace