Here’s what we were up to in the last two months of the year — the theme was tidying up and laying groundwork for exciting features in 2026 ahead!
Straight from the engine room — we’ve added persistent queuing to everything we do asynchronously. This ensures that all background tasks continue to run smoothly even when we deploy updates to the platform. The new queuing system also provides more robust error handling, which means better reliability for your deployments and operations.
This infrastructure improvement might not be visible on the surface, but it’s a critical foundation for the platform’s stability and future scalability.
In order to further advance our multi-region support, we refactored significant portions of our internal code. While there’s never a perfect time for large refactoring work, we chose this period to make these important changes. The result - thanks to our robust queuing system - will support our journey toward offering multiple regions and BYOC (Bring Your Own Cluster) down the road.
During this work, we discovered numerous areas that needed region-specific adjustments — for example, DNS settings that vary per region. You can already see the first results of this work in the runway region ls command:
runway region ls -o json
[
{
"id": "ber1",
"name": "Berlin",
"live_status": true,
"country_code": "de",
"country": "Germany",
"continent": "eu",
"dns": {
"a_record": "5.57.43.177",
"cname_record": "paas-prod-ip.runway.horse",
"base_domain": "pqapp.dev"
}
}
]
Our API documentation is now available at https://runway.horse/api-docs.
Everything you and we use when interacting with Runway is powered by this API — whether you’re using the web UI in the browser, or the CLI in your terminal.
Our API is a truly a first-class citizen in our platform architecture, and we’re excited to see what developers build with it. The comprehensive documentation includes endpoint details, request/response examples, and authentication guidance to help you integrate Runway into your workflows.
We’ve updated our buildpack stack several times over the past months and released automated documentation that catalogs everything included in our platform. While most of our buildpacks come from the excellent Paketo project, we’ve carefully customized the included buildpacks to work optimally with Runway’s infrastructure. We’ve also excluded certain buildpacks that don’t align with our platform model — for example, watchexec, the PHP built-in web server, and others.
Over the past weeks, we’ve made several improvements to our builder to proactively block configurations that wouldn’t work on Runway, helping you catch issues earlier in the development process. Since we believe in transparency around how we build your applications, we’re planning to add Software Bill of Materials (SBOM) support next year and provide detailed instructions for using the buildpacks on your own machine or other environments.
This will give you complete flexibility in how you develop and deploy your applications.
Looking back at 2025, we shipped several major features that significantly enhanced the Runway platform:
These are just the highlights — check out all our updates from 2025 to see everything we’ve built throughout the year.
And that’s all we have for November and the little bit of December of 2025. We wish you a wonderful time — happy holidays 🎄 if you celebrate, plenty of rest, good food, and time with friends and family. Here’s to a great start in 2026!
We’re excited about how Runway shaped up in 2025 and what’s to come in the year ahead.