Pulley's cap table platform is shutting down, and Google quietly walked back the Gemini 2.5 shutdown dates

A significant SaaS shutdown landed tonight, and a re-verification caught a date that a vendor had quietly removed. Three new entries, one correction to an existing one.

New: Pulley cap table platform is shutting down — 8 December 2026

Pulley, the venture-backed cap table and equity-management platform startups use to track ownership, issue equity grants, run 409A valuations and hold stakeholder records, is shutting down completely. Its own homepage says it plainly: “Pulley will be shutting down and will cease all operations and services on 12/8/26.”

This is a whole-company shutdown, not a feature retirement, and what’s inside the platform makes it serious: a cap table is the authoritative legal record of who owns a company. Pulley says it has an exclusive partnership with Carta and that existing customers may qualify for an assisted migration. The move to make now is twofold — log in and check whether you’re eligible for the Carta migration offer, and, regardless of where you land, export everything while the platform is still live: the full cap table, option ledgers, 409A history and board documents. Reconstructing a cap table after the service is gone is far harder than exporting it today. Because Pulley is hosted SaaS, there’s no code fingerprint to catch it — this one is a date to track.

Correction: Google’s Gemini 2.5 shutdown dates — only Flash Image is still dated

A within-window re-check of Google’s official Gemini API deprecations page turned up a change we’ve corrected tonight. Earlier in 2026 the page listed Gemini 2.5 Pro, 2.5 Flash and 2.5 Flash-Lite with a shutdown date of 16 October 2026. That date is gone — all three now read “No shutdown date announced.” Google removed the date rather than moving it, so the 2.5 text models keep answering with no published end date.

The one model that is still dated is Gemini 2.5 Flash Image (gemini-2.5-flash-image), scheduled to stop on 2 October 2026, with gemini-3.1-flash-image-preview as its replacement. We’ve updated the entry accordingly, dropped the now-dateless CLI fingerprints for the three text models (a deprecation with no date must not fire a dated warning), and kept the one for Flash Image. Every 2.5 model is still marked deprecated with a named 3.x successor — but if you were planning around a 16 October cutoff for the text models, that deadline no longer exists. The lesson holds for any fast-moving deprecations table: trust the current primary source, not a figure quoted elsewhere.

New: two short-lived runtime releases reaching end of life

Both are non-LTS releases with deliberately short support windows — the kind of version that looks stable because of its number but isn’t:

• MariaDB 13.0 — 31 December 2026. A rolling release that shipped on 15 September 2026, so its whole maintenance window is about three and a half months. After the EOL date the 13.0 line gets no further releases, including security fixes. For production, move to an LTS line: MariaDB 12.3 (to June 2029) or 11.8 (to June 2028), and swap mariadb:13 tags accordingly.
• Oracle JDK 27 — 31 March 2027. A non-LTS feature release (shipped 15 September 2026) with the usual six-month Oracle-updates window, ending when JDK 28 arrives. For long-lived apps, sit on an LTS: JDK 25 (to September 2030) or JDK 21 (to September 2028). These dates are for Oracle’s builds specifically — other OpenJDK distributions have their own.

Still ahead on the board

• 17 September: the Azure Maps Render v1 API retirement.
• 24 September: OpenAI’s Sora 2 video API shutdown.
• 30 September: a cluster including Amazon Mechanical Turk and the Azure Automation Python/PowerShell runtimes.
• 2 October: Gemini 2.5 Flash Image, then Exchange Web Services on 1 October and the OpenAI 23 October API removals.

Further out: .NET 8 and 9 end of support (10 November), PostgreSQL 14 end-of-life (12 November), then MariaDB 13.0 and Pulley in December. The full board with live countdowns is on the calendar.