# Platform updates, July 2026

Source: https://blog.fortrabbit.com/platform-updates-july-2026
Created: 2026-07-28
Author: Frank Lämmer
Tags: changelog

> A command palette for the dashboard, logs in the browser, MySQL timezone support, and a public API taking shape.


Another month, another round toward general availability. We try to ship frontend features early and rough, then iterate on them as your feedback comes in. Most of the rest of our day to day work stays quiet: plumbing, cleanup, the boring parts that make the platform feel finished. As before, we keep the new and the old platform apart, since both still run side by side.

## Search from anywhere

The actions menu we reworked last month grew up. It is now a proper command palette: hit `⌘K` (or `Ctrl-K`), start typing, and one box takes you anywhere. It searches across your apps, environments, teams, and people — and lists the actions you can run right there next to them. Find an app and jump to it, or trigger a task on it, without clicking through the navigation.

:ContentClip{src="/images/filter-and-search.mp4" poster="/images/filter-and-search.png"}

This is the shape we always wanted for the dashboard: less pointing and clicking, more typing what you mean. We will keep feeding more objects and actions into it.

## Logs in the browser

![Logs in the browser](/images/logs-poster.png)

The big one. You can now read PHP, access, Apache, and Jobs logs straight in the dashboard — filter them, follow them live, download an archive. No SSH, no tailing files by hand. Nobody picks a web host for its log viewer. But observability is where the new platform was thin, and we wanted to close that gap before release. There is a whole post on it: [Logs now available in the browser](/logs-in-the-browser).

Deploy logs got the same care. They now render ANSI colors, so the output reads like it does in your terminal, with clickable links where a tool prints them — plus a copy button to grab the whole log in one click.

## Platform and infra

A batch of smaller infra work landed, mostly on the new platform.

### MySQL timezone support

MySQL now ships with the timezone tables populated. Craft CMS lists this as a server requirement, and until now it was missing — so date and time handling that relies on named timezones works instead of throwing.

### Old platform: MySQL 8.4

The MySQL 8.4 migration on the old platform is finished. This month brought foreign key fixes and a `mysql-client` upgrade to match the server.

### Backup sizes

The single-backup view already breaks down what a backup holds — files, database, general info. Now it also shows the sizes: the measured web and MySQL storage plus the compressed size of the archive itself. Not down to the byte, but close enough to know what you are about to restore.

### Coming soon

- **More temp space** — `/tmp` is tight for some workloads. We are working on giving apps more room there.

## Docs and website

- **Extended hosting guide** — the hosting overview now covers serverless PHP options alongside the classic setups, so the guide reflects the wider landscape and not just our own lane.
- **Use cases** — the website now has a :ContentLink{href="/use-cases" text="use cases" prefix="www"} section, with related cases surfaced on the software and solutions pages, so it is easier to find the setup that matches what you are building.
- **A more readable pricing specs page** — the :ContentLink{href="/pricing/details" text="pricing details" prefix="www"} page is now wired to the same specs we use everywhere, with a currency switch and a copy/AI button, and a machine-readable export underneath for the bots that read before they buy.
- **Global docs review** — we read the docs end to end and fixed what drifted.
- **Deep links that land** — anchor links on logged-in docs pages used to scroll to the wrong spot. Fixed.

## Smaller improvements

- **Job limits, explained up front** — the new-job page now tells you when an app is at its plan's job limit, instead of letting the save fail.
- **Environment names from your branch** — creating an environment now suggests a name based on the Git branch it deploys.
- **Better stack detection** — new apps recognize Laravel 13, now the default in the picker, and detect Craft 6 as Craft rather than Laravel.

## From the blog

We published a piece on the state of PHP application performance monitoring: [APM for PHP landscape in 2026](/apm-for-php). A take on what these tools do, where they help, and the meta-observability angle.

## Thanks to our clients

We started collecting :ContentLink{href="/testimonials" text="testimonials" prefix="www"} on the website — real quotes from people running real apps with us, with links back to where they said it. Some of you have been with us for years and said kind things along the way. It means a lot, and it is nice to finally give those words a home. Thank you.

## About green hosting

A heads-up for the environmentally minded. Many green-hosting checkers now show red for sites on fortrabbit — and for a big slice of the web along with us. Our electricity did not change. The dataset behind those badges did.

The Green Web Foundation, which most of those checkers read from, archived AWS — our upstream — as a verified green provider, because it could not get anyone at AWS to keep the listing current. So anything running on AWS, us included, now comes back as "no evidence found". [They wrote it up here](https://www.thegreenwebfoundation.org/news/an-update-on-finding-representatives-for-large-hosting-providers/).

As a downstream provider we can carry the proof ourselves — the upstream sustainability paperwork plus evidence that we run on that infrastructure — and get re-listed. We are on it.

## Outlook

**Public API and a CLI.** The public API is no longer just a plan — it is being built, with real endpoints, filters, and its own docs. A command line tool to drive it is on the same track. Together they are the path to configuring apps from your terminal and your repository instead of only the dashboard. Early days, but moving.

**Performance.** We are running the new platform through extensive performance testing — real CMS apps, synthetic concurrency, PHP scaling experiments — and tuning as we go. Some of it confirmed what we hoped, some of it sent us digging. This is ongoing work, and one of the last big things standing between here and general availability.

A lot of what shipped this month — features and bug fixes alike — traces back to feedback. A few power users in particular keep sending sharp bug reports and pushing for changes; you know who you are, and it shapes the roadmap more than you might think. As always, feedback is welcome.
