Phaseo Team30 June 20265 min read
ICYMI: What We Shipped in June 2026
June sharpened model discovery, lifecycle signals, monitoring, onboarding, and provider coverage.
June was about keeping Phaseo useful while the model market moved quickly. The month had a lot of catalog work, but the bigger story was reliability: better discovery, clearer lifecycle signals, stronger monitor pages, and more provider coverage.
This recap covers the work that shipped from 1 June 2026 through 30 June 2026, based on the release history, commit history, and catalog data for the month.
What Shipped
Model discovery became more reliable
June included a lot of work on model discovery, provider checks, and catalog imports. Discovery moved to scheduled Cloudflare jobs, recovery improved, issue sync was re-enabled, and stale model notices started being cleaned up during import.
That made the catalog less dependent on manual checks and helped provider updates move through the system more consistently.
This is not just internal housekeeping. If a provider adds a model, changes pricing, retires an alias, or changes availability, users need Phaseo to notice. June reduced the chance that those changes would sit unseen until someone manually checked them.
Model pages got clearer lifecycle information
We added model page notices, relative-time cards for model lifecycle dates, cleaner date ordering, and fixes for model-detail scroll behaviour. We also improved quickstart model selection and condensed model quickstart flows.
The goal was to make each model page easier to trust at a glance: what is available, what changed, what is retired, and what to use next.
This matters because model pages are not static landing pages. They are living records. A model can move from rumoured to preview, from preview to active, from active to deprecated, or from one provider to several. June made those transitions easier to explain in the product.
Monitor and usage views improved
The monitor history feed moved to Supabase, monitor cards were polished, and status dates and links became more visible. Settings observability was also upgraded, and the gateway gained more API routes and usage metrics.