Service & Dependability
Your Needs Are Our Mission
Check Your YAML Before It Checks You 
The Long Road Ahead 
Python Support Has Arrived 
Picture a typical software project. A developer finishes a new feature or fixes a bug and opens a pull request. Now what? A code reviewer looks at the diff - lines of text on a screen - and tries to imagine what the changes will look like in a browser. A QA tester waits for someone to update a shared staging server. A project manager asks “is it ready to look at yet?” for the third time this week. A client waits days to see a change that took hours to build.
At every stage, someone is waiting on someone else. The shared staging environment gets overwritten before the client signs off. A bug slips through because nobody had a clean environment to test against. The feedback comes too late, after the code is already merged.
This is the coordination tax that almost every development team pays - and it compounds across every feature, every sprint, every project.
Probo.CI takes a simple but powerful idea: every pull request should have its own environment.
The moment a developer opens a pull request, Probo.CI automatically spins up a complete, working version of the application - built from that developer’s exact code. It posts a link directly back to the pull request. Anyone on the team - or anyone the team wants to share it with - can click that link and interact with a real, running version of the application.
No waiting for a staging server update. No pulling down to your local environment, no over-writing your IDE work to look at changes, no imagining what the diff looks like in a browser, and no coordinating schedules to get everyone looking at the same environment.
Every pull request gets its own shareable preview environment - automatically, in minutes.
When the pull request is updated, the build updates too. When the PR is merged or closed, the environment is cleaned up. The whole process runs without anyone having to manage it.
Most CI tools are built around one idea: run your automated tests and tell you if they pass. That’s valuable, but it’s only part of the picture. For database-driven web applications - Drupal sites, WordPress platforms, Laravel apps, .NET webapps, anything where content and configuration live in a database - automated tests alone aren’t enough.
Probo.CI is built for exactly these kinds of applications. You can load your sanitized production database backup into every build environment, so every reviewer is looking at a version of the site that matches your real content. No more “it works in the test environment but looks broken with real data.” You can also pull your production or staging database directly from providers such as Pantheon, Acquia or Upsun – providing you with real-time tests against your latest working data.
Probo connects to GitHub, GitLab, and Bitbucket. If your team is already using pull requests - and you almost certainly are - Probo.CI fits directly into that workflow. There’s nothing new for developers to learn; the build link just appears in the pull request.
One of Probo’s core beliefs is that there’s more to software quality than passing tests. Real people need to see and approve changes before they ship.
Every build gives you a working environment you can use our web-based SSH into directly. Debug issues the way you actually work - not by reading logs and guessing. Build-specific SSH access means you can poke around inside a running environment without affecting anyone else.
Instead of waiting for a staging deploy, you get a link for every pull request. Environments stay up for as long as you need - Probo.CI doesn’t tear them down the moment the build finishes. Take your time. Test edge cases. Sign off when you’re confident.
Get real visibility into the state of every feature in development, not just a status update. Share a build link with a client and let them review changes before code is ever merged. Catch misunderstandings between what was requested and what was built early - when fixing them is fast and cheap.
No more waiting for a scheduled demo. No more trying to describe feedback on a screenshot. Click the link, interact with the actual site, and leave feedback on what you actually see.
Probo.CI isn’t locked to a single language or framework. It works with:
All it takes to configure Probo.CI for your project is a single .probo.yaml file in the root of your repository. This file tells Probo how to build, configure, and set up your application. We provide starter templates and examples for every supported platform to get you up and running quickly.
Probo.CI keeps your build environments running until your team is done with them. If there’s a build you need to preserve - a milestone release, a build a client is actively reviewing - you can pin it so it isn’t automatically removed.
Storage is managed intelligently in the background. When your organization approaches its storage limit, Probo automatically cleans up older builds - always keeping the most recent build on each branch, and never touching anything you’ve pinned.
Probo.CI was created to solve a real problem: popular CI tools like CircleCI and Travis couldn’t handle the complexity of database-driven Drupal applications. Once the tool took shape, it became clear it wasn’t just solving a testing problem - it was solving a collaboration problem.
Probo is built on Docker and written in Node.js, and its foundations are open source. It’s been battle-tested on complex, high-stakes web projects and refined over years of real-world use. Today it’s owned and operated by FlyingFlip Studios, LLC with the mission of making continuous collaboration available to every developer, regardless of stack or size.
If your team ships software with pull requests, Probo.CI makes the space between “code written” and “code approved” shorter, smoother, and less stressful - for everyone involved.
The question isn’t whether your team needs a better review process. It’s how much longer you want to wait before having one.
Get started free - new organizations get a two-week trial with no payment required. Or compare our plans to find the right fit for you or your team.
When you sign up for a Probo.CI registration code, you will get a two week trial of the plan of your choosing. For more information on how to get started, click here .
LEARN MORE ABOUT PROBO.CI'S PRICING