---
title: "DEVLog - October"
date: "2026-11-01"
description: "Discover what happened in October 2026. Qualified signatures opened as a private beta at SignatureAPI, six public framework starters shipped, and ParentSignature for Schools got ready for launch."
tags: ["Devlog"]
url: "https://rolandoandrade.me/blog/devlog-october-2026/"
author: "Rolando Andrade"
---

# DEVLog - October

> Discover what happened in October 2026. Qualified signatures opened as a private beta at SignatureAPI, six public framework starters shipped, and ParentSignature for Schools got ready for launch.

October had 923 commits across 13 repositories. After the rush of September, this month was about finishing. Qualified signatures went public as a beta, and the school app got ready for real users.

I wrote this devlog later, from my GitHub history, to fill a gap in the series.

## Qualified signatures in beta

[**SignatureAPI**](/projects/signatureapi/) got 479 commits from me. The main story was qualified electronic signatures, the kind that has the same legal weight as a handwritten signature in the European Union. We announced them as a private beta, and I wrote the docs for them and for SWP/1, our Signing Worker Protocol.

The hard part was the flow. A qualified signature comes from an outside provider, so SignatureAPI cannot finish the document in one step. I built a deferred signing flow for that. SignatureAPI prepares the document, waits for the signature to come back, and then finishes the document. I also added support for the CMS signature format, a standard way to package a digital signature, on top of SWP/1.

I also wrote a post for the Devs section of our blog about the new first-envelope onboarding and how its first week went. And two more things reached the changelog: the MCP server is now generally available, and our Claude plugin is listed in the Claude plugin directory.

[SignatureAPI](https://signatureapi.com): Electronic signature API for workflows, applications and platforms.

## Six starters, one per framework

Every developer starts from a different stack. So I published six public starter projects for SignatureAPI, one for each popular framework:

*   [Next.js](https://github.com/signatureapi/signatureapi-nextjs-starter)
*   [Express](https://github.com/signatureapi/signatureapi-express-starter)
*   [FastAPI](https://github.com/signatureapi/signatureapi-fastapi-starter)
*   [Laravel](https://github.com/signatureapi/signatureapi-laravel-starter)
*   [Ruby on Rails](https://github.com/signatureapi/signatureapi-rails-starter)
*   [.NET](https://github.com/signatureapi/signatureapi-dotnet-starter)

Each one does the same three things: send a document for signature, verify webhooks (the messages SignatureAPI sends when something happens), and download the signed PDF. You clone the one that matches your stack and you have a working example in your own language.

![The Next.js starter after a test agreement was signed, with a link to the signed PDF.](https://storage.rolandoandrade.me/blog/devlog-october-2026-nextjs-starter.webp)

## Schools get ready to launch

**ParentSignature for Schools** got 287 commits and 25 merged pull requests, all about launch.

New schools now start with a guided practice send. Instead of watching a video, you walk through the steps and send a practice form yourself. AI assistants now connect over OAuth, with AuthKit handling the login. I added privacy policy and terms pages, and a way to schedule a school's deletion and undo it.

I also built an end-to-end test suite in three waves. These tests click through the app like a real user, from start to finish. I also fixed five race conditions before launch. A race condition is a bug that only appears when two things happen at almost the same moment.

Resends changed too. They no longer call SignatureAPI each time. Instead, the app has its own limit: one resend every 15 minutes, and up to 3 a day.

[ParentSignature](https://parentsignature.com): A free tool that lets teachers collect parent signatures on school forms digitally.

## A private planning project

I also started a private project to plan my next ideas. It collects research on real problems people have and groups them by type. I am not ready to share more yet.

## What's next

*   **ParentSignature for Schools:** launch.
*   **SignatureAPI:** grow the qualified signatures beta.
*   **Starters:** keep them in sync with the API.

Thank you for reading. If you are starting a SignatureAPI integration, pick a starter and tell me how it goes!

[Book a call with Rolando](https://rolandoandrade.me/pricing/)