The priciest models are now Ultra-only
Plus still unlocks the flagship models, but now stops at models priced above $25 per million tokens (input and output combined). Those, such as Claude Opus 5 and GPT-5.5, are available on Ultra. Plus members keep every other flagship, including Claude Opus 5.5, and the picker shows which models need Ultra.
417 words
Models above $25 per million tokens need Ultra.
The model picker marks them with an Ultra lock on Free, Pro and Plus.
Auto and Telegram stay within what your plan can use.
Portail v2.7.5 shipped on 2026-10-24 as a patch release focused on the priciest models are now ultra-only. Plus still unlocks the flagship models, but now stops at models priced above $25 per million tokens (input and output combined). Those, such as Claude Opus 5 and GPT-5.5, are available on Ultra. Plus members keep every other flagship, including Claude Opus 5.5, and the picker shows which models need Ultra. The work is recorded here because small releases are still product history. They change how people sign in, read responses, pay for access, share conversations, open files, or trust the system when something goes wrong.
The main changes were direct: models above $25 per million tokens need ultra, the model picker marks them with an ultra lock on free, pro and plus, and auto and telegram stay within what your plan can use. That list is intentionally plain. It names what changed without turning the release into theatre. When a release fixes a build, a redirect, a storage path, or a UI edge case, the value is often that users stop noticing the problem. The archive keeps that invisible work visible enough for future debugging and for anyone checking whether Portail has cared about the details over time.
This version also fits into the wider Portail contract. One account, one chat history, and one model picker only work if the smaller pieces keep their promises. Authentication has to fail clearly. Billing has to count honestly. Uploads have to arrive in a form models can read. Admin tools have to show the operator what happened instead of hiding it behind a blank screen. v2.7.5 moved that contract forward in its own narrow lane.
The screenshots attached to this entry show the public release record as it now appears on portail.cc. For older releases, this archive was rebuilt from the git history, package version changes, release modal text, and commit subjects. That means the page is honest about its source: it documents the shipped change and preserves the record going forward, even when the exact old production screen cannot be recreated from a single saved image.
The practical result is simple. Someone landing on this page can see the version number, date, release tier, headline, highlights, and a real rendered screenshot of the archive page. Search engines can index the post through the canonical URL, sitemap entry, and structured data. Future releases now have a standard to meet before deploy, so the history should get cleaner from here instead of fuzzier.