Plotting our direction for more options and more support.
The Roadmap For Probo.CI
Check Your YAML Before It Checks You 
The Long Road Ahead 
Python Support Has Arrived 
Last Updated: July 14, 2026
It has been a busy year at FlyingFlip Studios with Probo.CI. We have shipped .NET, NodeJS and Python support, manageable secrets, build-specific databases, YAML syntax checking, and a proper build queue to say nothing of our completely revisited and re-written documentation. Today we want to share where we are headed next.
A quick note before we dive in: this is a roadmap, not a release schedule. The items below are listed in no particular order, but priorities can shift based on what we hear from you. If something on this list matters to your team, tell us - it genuinely influences what we build first.
Today, watching a build in progress can be frustrating with lags and timeouts. Log output for build steps can lag behind what is actually happening in the container, which makes it harder to spot a problem early and cancel a build that has already gone sideways.
We are reworking how build step logs stream to the portal so that output appears as it happens. When a step starts producing output, you will see it in near real time - no refreshing, no waiting for a step to finish before its logs appear.
The build queue we’re shipping in the August 2026 release runs strictly first-in, first-out, and visibility is limited to the number of builds waiting. That was the right foundation, but we can proide more.
We are exploring enhancements like seeing which builds are in the queue and in what order, reordering or prioritizing queued builds, and smarter handling of superseded builds when a pull request is updated. If you have opinions on which of these matters most, we would love to hear them.
When a build does fail, figuring out why should not require detective work. Today that can mean scrolling through long step logs looking for the line that actually mattered.
We are improving error reporting across the board: surfacing the failing step and the relevant error prominently in the build results, making error messages more specific and actionable, and reporting richer failure detail back to your pull request so you can often see what went wrong without leaving your repository.
Perl is still quietly powering an enormous amount of the web, and teams maintaining Perl applications deserve modern CI tooling too. We are adding first-class Perl support to Probo.CI, joining our existing support for PHP, Node.js, Ruby, Python, and .NET. If you have a Perl application you would like to test with us early, get in touch.
Build environments currently live on Probo.CI-generated URLs. That works fine for internal review, but it is less than ideal when you are sharing a build with a client or testing functionality that depends on a specific hostname.
We are adding support for custom domain names, so your build environments can live on a domain your team controls. Share a preview with a stakeholder on a URL that has your branding and not ours.
Catching visual breakage is one of the most valuable things a preview environment can do, but today it requires wiring up third-party tools yourself. We are building visual regression testing directly into Probo.CI: automatic screenshot comparisons between your builds, with differences flagged right in the build results. No external services, no extra configuration gymnastics.
Probo.CI currently integrates with GitHub, GitLab, and Bitbucket. Azure DevOps is the most requested addition to that list, and it is on the roadmap. Teams using Azure Repos and pull requests will get the same experience our other integrations provide - builds triggered automatically from pull requests, with status reported back to your repository.
For teams working with U.S. federal agencies, compliance requirements decide which tools you can use at all. We are pursuing a FedRAMP-authorized hosting option for Probo.CI so that government teams and their contractors can bring continuous integration and preview environments into their workflow without leaving their compliance boundary. This is a longer journey than the other items on this list, but we believe it is worth the investment.
This roadmap belongs to you as much as it does to us. Every item on this list started as feedback from a team using Probo.CI, and the order we build things in is shaped by what we hear.
If one of these features would change how your team works - or if there is something missing from this list entirely - reach out to us at hello@probo.ci. We read everything, and we are happy to talk through what is coming and when.
When you sign up for a Probo.CI registration code, you will get a two week trial on our Freelancer or Partnership plan. For more information on how to get started, click here.
LEARN MORE ABOUT PROBO.CI'S PRICING