A page for every model, matchup and feature

Portail v2.6.28 shipped on 2026-10-15 as a patch release focused on a page for every model, matchup and feature. Portail now has public pages for the questions people actually type into a search box: which AI is better, where to use a given model without its own subscription, and what one chat can do with your PDFs, inbox and calendar. Every model family gets a page with its full lineup read straight from the live catalog, so the numbers on it are never older than the catalog itself. Comparisons like ChatGPT vs Claude stay honest. They describe what each family tends to be good at, show the live counts side by side, and then point at the only test that settles it: your own prompt, asked of both, in one thread. Everything is in English and Russian, and it all lives one click from the footer. 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: new /models hub with a page for each of 15 families: gpt, claude, gemini, deepseek, qwen, grok, llama, mistral, glm, kimi, minimax, nemotron, sonar, nova and command. each lists every model portail serves in that family, with context size, image input, reasoning and cost band, pulled from the live catalog, new /compare hub with six head-to-heads (chatgpt vs claude, chatgpt vs gemini, claude vs gemini, chatgpt vs deepseek, chatgpt vs grok, claude vs deepseek) and five alternatives pages (chatgpt, claude, gemini, poe, perplexity), new /features hub covering chat with pdf, the canvas image generator, memory, comparing models with council, scheduled tasks, gmail and calendar connectors, and portail in telegram, every new page carries faq and breadcrumb structured data and is listed in the sitemap, and the footer links to all three hubs, the llms.txt summary for ai search engines now shows the current free, pro, plus and ultra pricing instead of the old lineup, and ratchet's site now says hand-offs work on pro, plus and ultra, which is what the server has allowed since plus launched. 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.6.28 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.