--- title: "Why We Built Tugboat.QA" url: "/articles/why-we-built-tugboatqa" type: article date: 2016-05-06 updated: 2016-05-06 --- # Why We Built Tugboat.QA # Why We Built Tugboat.QA Tugboat lets you see every change fully integrated into your larger site the moment it’s ready for review. No more waiting to see the work. No more waiting for feedback. By [ Matt Westgate ](/about/matt-westgate) May 6, 2016 [Embedded Video](http://www.lullabot.com/media/oembed?url=https%3A//vimeo.com/165022680&max_width=0&max_height=0&hash=WiN1kVSzfQywuhXUQ0dS6fWBlcER5FzQWlCFynFqzMc) [Three years ago](https://www.lullabot.com/articles/github-pull-request-builder-for-drupal), Lullabot started a [project](https://www.tugboatqa.com/) to bring visibility to the web development process. Asking our clients to wait to see work in progress is not only an embarrassing ask, it’s an alienating one for stakeholders. Waiting two weeks until the end of a sprint cycle for a demo was not only nerve-wracking, it also slowed potential progress, and meant that feedback was often delayed until too late. The truth was that building these demo sites was a lot of work: work that was taking time away from creating the actual website. How would you feel if your general contractor said you could only see the house they were building for you twice a month? Unacceptable. Time and time again, through client interviews and [market research](https://www.geneca.com/why-up-to-75-of-software-projects-will-fail/) we found this pain was widespread and in need of resolution. The lack of visibility and thus engagement was leading to out-of-sync stakeholders and expensive rework. We knew we could work smarter and with lower costs. For stakeholders and non-technical team members, the barrier to collaboration in web development is nearly insurmountable. Stakeholders need to know how to setup a local working copy of the project and they need to know how to continuously keep that local instance working—which is its own sisyphean task. With Tugboat, we’re able to eliminate the technical barriers and share work as it happens with everyone, anywhere. Tugboat does this by automatically building a complete working website whenever a new pull request is generated. The entire team can see every change, every feature, every bug fix fully integrated into the larger site the moment it’s ready for review. No more waiting to see the work. No more waiting for feedback. Tugboat is hosting agnostic. You don’t host your website with us in order to use it. But we do take platform architecture seriously, so every account is its own silo of dedicated resources and each project begins with a custom setup to ensure you’re ready to set sail. Tugboat can even run inside your own hosting environment (on premise) if you need to keep your data behind your firewall. We can also run custom Docker containers if you’re already using Docker as part of your production workflow. We hope you get a chance to check out Tugboat. Stop by the Lullabot booth at [Drupalcon](https://events.drupal.org/neworleans2016) and say hello. Meanwhile, if you’re a developer we’ve built a [sandbox version](https://www.tugboatqa.com/demo.html) of the platform for you to explore. Fork the public repository of our website, create a pull request and voilà ! You can watch Tugboat chug chug chug its way into action. Be sure to check out some of the cool features while you’re there: built-in command-line access, visual regression tests, and real-time logging. But don’t take our word for it. Head on over to the [demo](https://www.tugboatqa.com/demo.html) to take Tugboat for a cruise! Published in: - [ Business ](/topics/business) - [ Deployment ](/topics/deployment) - [ Technical Project Management ](/topics/project-management) You must have JavaScript enabled to use this form. ## Get in touch with us ### Tell us about your project. We'd love to hear from you! First Name Last Name Your email address Your organization How you heard about us Tell us more Leave this field blank