500 Envelopes A Month: $375 On BoldSign, €24.50 On Firma.dev

The Math At Three Volumes

BoldSign’s formula is published in its own FAQ: the plan starts at $30 a month with 40 envelopes, and once those are used a pay-as-you-go rate of $0.75 per envelope starts. Ours is €0.049 times the number of envelopes. Nothing else.

40 envelopes a month: $30 on BoldSign, €1.96 on Firma.dev. 500 a month: $375 against €24.50. 2,000 a month: $1,500 against €98.00.

We have not converted currencies on purpose. BoldSign prices in US dollars; we list in euros and bill you in your own currency at the payment processor’s rate, with no markup from us.

Read This Before You Compare Envelope Counts

An envelope does not mean exactly the same thing on both sides, and most comparison pages skip this.

BoldSign lets you put several documents in one envelope and counts it as one. On Firma.dev one envelope is one document sent for signature, whatever the number of signers or pages.

So the numbers above assume one document per envelope, which is how most in-app signing works: one lease, one contract, one consent form. If you routinely bundle several documents into one send, count your documents, not your sends, before you compare.

A Separate Workspace For Each Of Your Customers

Workspaces let your application create an isolated environment for each of your own customers or business units, provisioned through the API. Each one has its own API key, its own templates and documents, its own envelope usage, its own branding and sending domain, and its own webhook secret. Nothing is shared between them.

BoldSign lists “Multitenant SaaS app integration” on its Enterprise API plan, so it has an answer here too. Ours is that creating a workspace is a single call to POST /workspaces, keys rotate per workspace, and usage is counted per workspace, so if you bill your customers for their own signing volume, the numbers are already separated for you. Workspaces come at no extra cost.

I think cost was kind of the number one criteria initially, and then everything else kind of fell into place because it was so easy to deploy.

Pierre Hulin, Founder, Keylio, who had the integration running in under an hour

Keylio charges its users $10 a month, and each one sends about one signature a month. Pierre’s own math: “If one signature is $3, that's a 30% cost from our subscription.” At €0.049 it barely registers, so Keylio ships signing as a bundled feature.

Creating And Sending A Document Is One Authenticated Call.

const response = await firma.signingRequests.createAndSendSigningRequest({
    "name": "Employment Contract - John Doe",
    "document": "JVBERi0xLjQKJeLjz9MK..."
});

That returns a 201 with the request already in sent status. Authentication is your API key in the Authorization header. We also publish two MCP servers: a Docs MCP that lets Claude, ChatGPT, Cursor or GitHub Copilot read our API reference and write the integration for you, and a Data MCP that operates on your account. BoldSign also publishes an MCP server for agent actions; we did not find a documentation MCP from BoldSign.

Moving From BoldSign, Step By Step

Most teams integrate Firma.dev in under a day. The order we suggest:

1. Sign up and take the free testing mode API key. No credit card.
2. Create a workspace for each customer with POST /v1/workspaces. Each gets its own scoped API key.
3. Upload your PDFs and rebuild your templates, by API or in the embeddable template editor.
4. Swap your send call for POST /v1/signing-requests/create-and-send.
5. Swap the BoldSign embedded signing view for our embeddable signing experience, authorised with a short-lived JWT.
6. Point your webhook handler at our events: viewed, partially signed and completed.
7. Run your test documents in testing mode, then go live. Let envelopes already out on BoldSign finish there.

Questions Teams Ask