Yes, you can use your own database! Probo.CI gives you the ability to upload copies of your production database (though you may want to sanitize and shrink it first) to use in your build. You can upload your database nightly and always be testing against recent data from production.

Using our command line utility, you can schedule your databases to upload on a schedule using cron or Jenkins. This removes the manual step of uploading your databses on a daily basis. Keep in mind you have 10 gigabytes of asset storage per project - so be sure to manage your assets responsibly.

Probo.CI will over-write assets with the same filename. So if you are uploading your daily database with the same filename, then you won’t fill up your allocated asset space as quickly.

Absolutely. That’s how you use your actual database. We allow you to upload any build asset that you want and then use it from within your build steps.

You can also pull your database from other hosting services such as Pantheon, Acquia or Upsun by leveraging their API and/or command line utilities which can be installed inside any of our application containers. For examples on how to get databases from your live or staging environment into Probo.CI, click here.

Yes! You can run your test suite on Probo.CI. If you already have a CI pipeline and just want to add QA environments you can run Probo.CI alongside another test runner like Jenkins or Travis.CI in order to provide QA environments.

Probo.CI is not a hosting solution. We provide environments for quality assurance and testing but they are not optimized nor intended for production use.

When your build is finished, the environment where your build ran does not go away. Instead, you receive a link where you can go see the result before changes are merged into the master branch, and share it with your stakeholders. That way, your stakeholders are brought in much earlier in the process, saving the whole company huge amounts of time, money and aggravation.

If your build contains command line utilities or applications, you can test them in a more manual way by connecting to the build via the web-based SSH utility. This includes bash, perl, .NET (Powershell is included as well), javascript and many others.

While there is no specific limit to the number of builds you can have on Probo.CI at the same time. That said, the number of testable builds you can have at one time will be dictated by the available storage space of the pricing plan that you select.

You’ll get the best feeling for it after you run a build or two and see the results. You can keep your disc space down by proxying your media assets and by truncating database data irrelevant to testing. If you think space is an issue, please contact us and we would love to help.

Probo.CI is hosted on our own bare meta servers. In this way we completely control the environment, specifications and privacy of the data stored on that server. It also allows us to provide fast builds without any abstraction or virtualization overhead.

Long term plans are to migrate to dedicated environments inside of Azure Cloud for the purposes of better scalability and management of services that will be dedicated to the growth and longevity of the platform and its services

Probo.CI can run multiple kinds of applications. Everything is run inside of an Ubuntu Linux container which can be tailored for your application - allowing you to install and run applications in a wide variety of technologies.

Out of the box, Probo.CI supports standard LAMP stack applications as well as .NET, Javascript (Node.JS and other Javascript frameworks), and installable technologies such as Ruby, Python and Java.

Each build can be configured to run a compatible database and different versions of Apache Solr with your own cores based on need. Additional container side technologies include Redis and Memcached.

The Probo.CI logo is a rhombic triacontahedron. This is a convex polyhedron with 30 rhombic faces, 60 edges and 32 vertices of two types.

Our asset uploading service is a write only service to the outside world. Assets written can only be downloaded from within our infrastructure, and even then the appropriate credentials are required. If someone compromised your version control provider account (GitHub, GitLab or Bitbucket) then yes, they could move the asset directly into the download path on the web server. For that reason, we recommend requiring two factor authentication on these services and carefully guarding write access to your build repositories.

Yes we do. If your test instance needs access to the data, it needs to be in the clear (at least in memory), and that will give us access to it when it’s running on our servers. We don’t want access to your private data any more than you want to send it to us, which is why we recommend that you sanitize your database and remove any sensitive user information before you upload it.

If your data is super sensitive, and you don’t want to host it on a shared environment, then email us to talk about Enterprise Probo.

You can also pull your database from other hosting services such as Pantheon, Acquia or Upsun by leveraging their API and/or command line utilities which can be installed inside any of our application containers. For examples on how to get databases from your live or staging environment into Probo.CI, click here.

As part of that step, you can also introduce scripts to sanitize your data of sensitive information and other data as part of our build steps.

The isolation is provided by what is commonly referred to as Linux containers (the security portion is comprised of Linux namespaces and capabilities) so the isolation is exactly as good as these kernel features. Please see the article from Docker’s documentation on security. If that’s not good enough for you, contact us because we are capable of running all of your data on dedicated virtual machines or even dedicated hardware if you opt for our enterprise plans.

For more information our Enterprise Plans checkout our pricing comparison pages for more information.

Yes! You can either run the open source version yourself or contact us about our enterprise plans under which we can run Probo.CI on your hardware inside your datacenter or on dedicated hardware in our infrastructure that no other users have access to. If you’d like to learn more about Probo Enterprise, please send us an email.