Ben Lang

Firma.dev - E-signatures API for your app averaging ~3¢ per envelope

by
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.

Add a comment

Replies

Best
Büşra Şeker

The pricing is what made me stop and look. Most esignature APIs seem affordable until you start scaling usage.

Derick Dorner

@busra_seker1 Yah thanks Büşra .. dont get me started on what real volume means to Docusign etc. Its crazy. Even then, they don't come down to our prices. Thanks for taking a look. 😁

Thami Benjelloun

Does it support advanced stuff like multiple signers with order, reminders, and webhooks for status changes?

Derick Dorner

@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!

Ivan Stakhov

3 cents per envelope with no minimums is honestly the pricing model e-signatures should have had years ago. Indie hackers and small SaaS teams have been stuck either paying DocuSign enterprise rates or duct-taping PDFs together. Really excited to try this out.

Derick Dorner

@ivan_stakhov Thanks!! We're excited to have you let us know if you need anything support@firma.dev We have a lot of spam tickets to work through from the launch but we're generally very responsive.

Ada Johnsen

The pricing caught my attention first but the sandbox plus no minimums part is probably even more valuable for smaller teams

Derick Dorner

@ada_johnsen Yup! And you can get started super easy .. versus talking to a sales team and getting quotes for API usage. Thanks for looking! 😁

Darly Selby

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?

Derick Dorner

@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.

Peter Nick

I love the idea of making e signatures cheap enough that team stop treating them as a premium feature. One founder might see signing as a revenue stream, while another sees it as infrastructure. Your approach clearly leans toward the second philosophy.

Derick Dorner

@peter_nick Thanks Peter. Appreciate the support :)

Alper Tayfur

@derickd The API-first angle makes a lot of sense here. E-signatures are usually treated like a standalone tool, but for many products the real need is embedding signing cleanly into an existing workflow without making users leave the app.