Deploy it on your
infrastructure, or ours.

Yes, if you run it yourself. Download it, deploy it on your own infrastructure, and use it for your business at any scale without paying us anything - there is no seat count, no relay cap, and no trial clock. You pay for the AWS resources it runs on, the same as any software you host. If you would rather not run it, we host it for you; that is the part you pay for.

The Sustainable Use License - a fair-code licence, not an OSI-approved open-source licence, and we do not call it open source. You can read the source, modify it, self-host it, and run it for your own business at any scale. The one restriction is that you may not offer Baton to third parties as a hosted service competing with ours. If you are deploying it inside your own company, it does not affect you. It is the same licence n8n uses.

You run the stack. That means DynamoDB and SQS in your own AWS account, TLS in front of it, upgrades when a release ships, backups, and rotating your Docusign and platform credentials. Support is GitHub issues, answered on a best-effort basis. None of that is difficult, but it is yours. If you need an SLA, SSO, or someone on the hook for upgrades, that is what the cloud edition is for.

We run the infrastructure, apply upgrades, and monitor it, so nobody on your side carries a pager. It adds SSO, multi-organisation management, and a support commitment with agreed response times. The engine is identical - same code, same connectors - so anything you build self-hosted works there, and you can move between them.

Yes, and plenty of teams should. Self-host to evaluate it properly against your real Salesforce and Docusign accounts, then talk to us if operating it stops being a good use of your team's time. It is the same product either way, so nothing has to be rebuilt.

Baton works with Docusign accounts that have Docusign Workflow Builder. If you can build workflows in your Docusign account, you can trigger them from Baton. The developer sandbox is free, so you can test the whole path before committing to anything.

Ten ship today - Salesforce, HubSpot, Zoho CRM, Zendesk, BambooHR, Microsoft Power Automate, Smartsheet, Airtable, Greenhouse and monday.com - plus custom POST webhooks for anything that can send JSON. Every source is signature-verified and fails closed. You can also skip webhooks entirely and launch workflows from a spreadsheet with Bulk Upload.

Baton retries with backoff, and anything that exhausts its retries lands in the Control Center - one queue of runs needing a human, where you can retry, cancel or postpone. An automation that starts failing repeatedly pauses itself rather than flooding Docusign. Every attempt is logged with its payload, so you can see exactly what happened.

In your infrastructure, when you self-host. Baton stores webhook payloads and delivery metadata in your own DynamoDB tables, in the AWS region you choose, so data residency is your decision - ca-central-1 keeps everything in Canada, for instance. The self-hosted build sends us nothing: no telemetry, no analytics, no licence check.

The app itself is up in about three minutes with Docker. Connecting Docusign takes another ten or so, and each automation after that is a few minutes - create it, copy the webhook URL, paste it into your source platform. Salesforce is the exception and needs its own setup, which the in-app guide walks through.

Zapier and Make build multi-step workflows. Baton is the layer between your systems and Docusign Workflow Builder: it verifies events, decides which workflow each one should launch, and gives you one place to watch and fix every run. They are complementary. And unlike either, you can run Baton on your own infrastructure and read every line of it.