Never Miss a Firma.dev Update: The Platform Updates Guide

Firma.dev ships frequently. New signing capabilities, editor improvements, language additions, and security features land on a rolling basis, sometimes multiple in a single week. If you have a live integration, missing an update can mean missing something your customers would actually use.

There's one place to track all of it: docs.firma.dev/guides/platform-updates.

What the Platform Updates Page Covers

The Platform Updates page is a reverse-chronological timeline of every platform-wide change: new features, UI improvements, expanded language support, and editor additions. It's broader than the API changelog, which focuses specifically on schema and endpoint changes. The platform updates page covers anything that affects how Firma.dev behaves, whether it surfaces in the API or not.

If you're tracking what changed in a specific API version, the API changelog is the right place. If you want to know what's new across the platform, including things that don't show up in schema diffs, the Platform Updates page is where to look. Both together give you the full picture.

Recent Highlights

To give a sense of the pace and scope, here's what shipped in the last few weeks alone:

Passkey Sign-In (March 5): Dashboard users can now register passkeys using Face ID, Touch ID, Windows Hello, or a hardware security key for one-tap login. Up to 10 passkeys per account with cloud sync support.

Signer Email OTP Verification (March 5): Signers must enter a 6-digit email code before viewing or signing a document. Configurable at workspace, template, or signing request level with a cascading defaults system.

Template Document Replacement (March 5): Swap the PDF on an existing template without losing field placements, signer assignments, or settings. Works in both the main editor and the embedded editor.

Embedded Editor Close Controls (February 17): Both the Template Editor and Signing Request Editor now support a built-in close button and programmatic close via triggerClose(), with unsaved changes detection built in.

Multi-Script Signature Support (February 11): Firma.dev automatically detects the writing system in a signer's name and presents signature styles for that script. Five families supported: Latin, Cyrillic, Greek, Japanese, and Korean.

That's 5 meaningful updates across 3 weeks, covering security, editor UX, API capabilities, and internationalization. The platform updates page captures all of it in one scroll.

Stay Updated

We push a TON of updates as quick as we can beta test them … and we only do monthly newsletters. If you're on our feature request board or are interacting with our docs or github, we'll notify you when features release. Otherwise, stay updated with our platform updates and changelog.

Bookmark docs.firma.dev/guides/platform-updates and check it before sprint planning. When something ships that's relevant to your integration or your customers, it'll be there, dated and described clearly.

For a complete picture of what's changed, use it alongside the API changelog. Platform updates covers the what and why, the changelog covers the exact schema and endpoint details. Between the two, nothing slips past.

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