
Firma.dev
Electronic signature api at just $0.029 for developers
598 followers
Electronic signature api at just $0.029 for developers
598 followers
At €0.029 per envelope (about 3¢), Firma.dev runs about 99% cheaper than DocuSign's API pricing. Pay-as-you-go, no minimums, no contracts. It's built developer-first for startups and SaaS companies: a clean REST API, embeddable template and signing editors, and integration that takes hours instead of weeks. Every customer gets a dedicated workspace, so templates and documents stay separated. Designed to support ESIGN, UETA, HIPAA, GDPR, and eIDAS. Sign up, grab an API key, and start building.
This is the 2nd launch from Firma.dev. View more
Firma.dev
Launching today
At €0.029 per envelope (about 3¢), Firma.dev runs about 99% cheaper than DocuSign, where one envelope can cost $4-5. Pay-as-you-go, no minimums, no contracts. Built developer-first for startups and SaaS teams who'd rather integrate signing in an afternoon than sit through a sales cycle: clean REST API, embeddable template and signing editors, integration in hours. Test everything free with a sandbox key, real docs and unlimited usage, before you pay a cent. Get an API key and start building.






Free Options
Launch Team / Built With



Firma.dev
Hey Product Hunt, Derick here, co-founder of Firma.dev.
We built Firma.dev because every e-signature API we tried was either priced for enterprises or was an end-user app with an API bolted on as an afterthought. We wanted the opposite: an API-first product where signing is something you integrate in an afternoon, not a procurement cycle.
💸 Pricing. €0.029 per envelope, about 3¢, pay-as-you-go with no minimums or contracts. DocuSign can run $4-5 for a single envelope, so for most teams that's around 99% less.
🛠️ Who it's for. If your product touches contracts, you need this: HR and onboarding tools sending offer letters, property platforms handling leases, freelance marketplaces with client agreements, healthtech collecting consent forms, fintech onboarding flows, or any SaaS sending NDAs and proposals. At 3¢ per envelope you can make signing a built-in feature instead of a cost center.
⚡ Developer-first. Clean REST API, embeddable template and signing editors, and you can give each of your own customers an isolated workspace with separate templates and usage.
🤖 Built for AI-assisted development. We ship two MCP servers, one for our docs and one for the API itself with 84 tools, so coding agents generate accurate Firma.dev integration code and can even manage signing requests directly. We have a guide for Claude Code, plus Antigravity, Cursor, Lovable and the rest in our docs.
🌍 Legality. Designed to support the frameworks that matter, and e-signatures are legally recognized in 55+ countries.
🔑 Try it free. There's a sandbox key with real documents and unlimited usage, so you can test the whole flow before paying anything. No demos, no sales calls.
We'd love your feedback, especially from anyone who's fought with e-signature integrations before. I'll be around all day to answer questions.
Derick
Happy Friday hunters. 😎
Contral
@derickd Man it's crazy how cheap this is. Can i get a mail where i can contact you can talk more about the business side of things? Would love to talk.
Firma.dev
@samagra_gune Hi Samagra! Yes of course .. I have full visiblity into support@firma.dev .. theyll tag me if I dont see it myself, just ask for me :)
Our goal is to make e-signatures available to everyone.
Awshar AI
The pricing is compelling, but pricing alone rarely wins enterprise deals. What feature or capability do customers cite most often when choosing Firma.dev over DocuSign besides cost?
Firma.dev
@ankit_narang1 GREAT question yes obviuosly cost is very compelling, but outside that, we find our top customer needs are, in this order:
Legality in your country .. this is binary, you either are or you arent. E.g. we're not legal in China, but we are in 55+ other countries including EU, LATAM, US, and a lot of APAC.
API capability (usually this translates to white label) .. this is an area where we really shine. We built what we always wanted and I think it shows.. we're proud of it.
Wow, the 84-tool MCP server is the interesting part. Pricing an e-sign API at 3¢ basically makes it cheap enough for an agent to fire envelopes on its own, which is great right up until an agent fires one it shouldnt. Whats the guardrail there, can you scope what an agent is allowed to send per workspace? Overall, well done!
Firma.dev
@artstavenka1 Hi Art. Yup, you sure can. One of our key differentiors at Firma.dev is that we have workspaces (like, at all). Docusign has the capability in its highest tier enterprise plan$.
We created Firma.dev and workspaces because at our previous startup, we wanted to offer e-sign for free to our customers (we never could before), and do it in a secure way.
So the guardrail for the MCP ... itll ask you what workspace you want to engage with, and you have to "manually" switch workspaces. So if you're working with a particular set of customers, one customer, or a team, it works. Its like this: Use workspace Sales Team and send out the Customer Agreement to Derick at support@firma.dev
... make sense?
We're seeing a growing amount of our customers (especially on the real SMB side) using agentic workflows like that.
The pricing is the obvious hook, but the sandbox key is what would make me try it. E-signature APIs always feel painful until you actually test the full flow. Curious how you handle audit trails and signer verification?
Firma.dev
@farrukh_butt1 Thanks Farrukh. We're devs, and had the pain point first hand of having TERRIBLE APIs with the existing e-sign providers, so we built it how we would want. The thing about e-sign is, there's a lot of little laws you need to follow and be aware of .. audit trails are part of that. We have fully legal, compliant audit trails (just like Docusign) in 55+ countries. Okay fine if you need documents in China, use Docusign and pay $5 an envelope. But ours are totallly compliant and you can even configure them via the API / GUI.
Mailwarm
Does it support advanced stuff like multiple signers with order, reminders, and webhooks for status changes?
Firma.dev
@thamibenjelloun Hi Thami. Yes, our API is very powerful, and one of the largest on the market. We have everything you asked about: multiple signers with order, reminders (from us or you), custom domains, graphics, etc per workspace, and tons of webhooks (and those are even per workspace). Thanks for taking a look!
Is this API-only? We use PandaDoc, but not through the API—we use it as regular users to manually sign documents with clients and partners. Do you have a B2C/self-service option as well? If so, how much does it cost?
Firma.dev
@natalia_iankovych Hi Natalia! Great question. We probably aren't the best fit for you, unless you're retooling some of your workflows, e.g. building internal mini apps, or have software using an API. We do have a full powered GUI (that we're proud of) .. but white labeling via API for super cheap volume senders will always be our focus. 98% of our users send via API, 2% GUI.
We also play really well with things like N8N, Salesforce, etc. Our "self service" option is mostly used by people that connect our MCP server right into their Claude/ChatGPT .. but honestly thats pretty case dependent, you know?
However, if you find yourself thinking about processes in your org, and e-sign is part of that, hit us up.
Firma.dev
@natalia_iankovych Just to clarify .. I mean if youve got 50 sales people each with a docusign sub.. then yah its worth figuring out how to build us in.. but we're not designed to be a 1:1 replacement for Docusign end users.. just their API.
The dedicated workspace model seems underrated. Many teams building multi tenant SaaS products spend a lot of time figuring out document separation and permissions. Was this designed from customer feedback or from your own experience?
Firma.dev
@darly_selby YES DARLY THANK YOU--I feel seen 😅 that's one of our true core features is that the entire API(branding, webhooks, keys, everything) can be silo'd. E.g. You're a multi tenant saas and a new customer signs up, you auto-provision a new workspace, they can create their own templates, domains, etc, but yah you get it.
But to answer your question .. yah it was built from our own (painful) experiences on the customer side.
It came from that feature not existing in the open market when we were building an HR app. At that company, were using a Docusign knockoff and their API cost around 50 cents per doc, but we had to go an manually (through the GUI) make a team, and then our support staff would have to manually create their templates for them .. super labor intensive.
We didn't even know what to call them b/c the concept didn't exist, when all those other e-sign companies are built around the concept of a GUI and individual users sending docs .. not an API.
Thanks for taking a look.