How to Add E-Signatures to Your InsForge App

InsForge has become one of the leading backend platforms for agentic development. You connect your coding agent, describe what you want, and InsForge handles the database, auth, storage, and compute so your agent can ship a fullstack app end to end. But when your app needs to send contracts, collect signatures, or manage compliance documents, you need a purpose-built signing layer.

That's where Firma.dev comes in. It connects to InsForge through compute functions, giving your app a complete e-signature backend that handles everything from sending documents to tracking when they're signed.

👉 Already know what you're doing? Jump straight to the full InsForge integration guide on docs.firma.dev

How it works (without the technical details)

InsForge gives your coding agent serverless compute functions out of the box, which is exactly what Firma.dev plugs into. Your app sends a signing request through Firma.dev's API, the signer recieves the document, signs it, and your app gets notified when it's done.

There are two ways to set this up, and the integration guide covers both. The most direct path has your coding agent write a TypeScript compute function that calls the Firma.dev API. You store your API key as a secret in InsForge's dashboard, and the function handles the rest. For teams that want to move even faster, you can connect the Firma.dev Docs MCP server to your coding agent so it generates the entire integration against accurate API references in a single pass.

The important thing is that neither path requires you to become a backend engineer. If you're already building with an AI coding agent on InsForge, adding e-signatures follows the same workflow you're already using: describe what you need, and your agent builds it.

What you get out of the box

Once connected, your InsForge app can send documents for signature, track signing status in real time through webhooks, and embed the signing experience directly inside your app so users never leave your interface. Every signature is legally binding under ESIGN, UETA, and eIDAS (SES and AdES) frameworks.

Firma.dev also gives you Customer Workspaces, which means if you're building a multi-tenant SaaS product on InsForge, each of your customers gets their own isolated signing environment with separate templates and usage tracking. No data bleeds between tenants, and you get clean per-customer reporting without building any of that plumbing yourself.

The pricing makes sense for builders

Most e-signature providers charge per user per month, which gets expensive fast when you're embedding signing into a product. Firma.dev charges €0.029 (~3 cents) per envelope with no monthly fees, no minimums, and no contracts. You pay for what you use. For an InsForge app that's still finding its footing, that means you can ship the feature today and only pay when people actually use it.

Point your agent at the guide

The full integration guide walks through every step, from storing your API key as a secret to setting up webhook handlers and embedding the signing UI. If you're using Cursor, Claude Code, or any MCP-compatible agent, you can connect the Firma.dev Docs MCP server and let your agent read the guide itself. One prompt, one pass, working integration.

Read the full InsForge integration guide on docs.firma.dev

Get started with Firma.dev for free, no credit card required.