December 29, 2026 has been the target for Figranium v1 for a while. But with the latest development progress, there's a good chance it won't take that long.

Over the past few releases, some of the biggest remaining pieces have fallen into place: scoped API keys, reusable cookie states, templates, and Vault integration with 1Password. The broader ecosystem—from SDKs and the CLI to MCP and integrations—has also continued to mature.

That changes what needs to happen next.

From features to stability#

I'm getting close to the point where Figranium doesn't need another major feature to justify v1. It needs confidence.

The focus now is on verifying existing workflows, testing integrations, resolving regressions, tightening security, and making sure upgrades behave predictably. I also expect to ship a release candidate before calling anything stable.

That's a different goal from simply finishing a checklist. A stable release should be something people can rely on, not just a version number.

So, is v1 coming early?#

Probably. December 29 remains the original target, but I now expect Figranium v1 could arrive earlier if testing goes well.

I'm not announcing a replacement date yet. There are still things to validate, and I don't want to trade reliability for a few weeks on the calendar.

For now, the plan is straightforward: finish the remaining work, release a candidate, test it thoroughly, and publish v1 when it's genuinely ready.

The finish line is looking a lot closer.