Houston, the Self-Service Mesh

Connect, configure, and collaborate across teams

Don’t get hung up on arcane configuration or high-risk migrations.

Houston is a service mesh that’s easy to roll out, easy to operate, and easy to use for every developer in your organization.

A dialog box with a slider indicating what percentage of service traffic should be routed to a new version that is being released.

Connect

Houston plugs into your existing infrastructure to create an out-of-the box service mesh. Easily integrate service discovery and generate service-level dashboards in both Houston’s UI and your own metrics system.

Already have Envoy in place? Houston can configure your pre-existing proxies with just a few additional lines of configuration.

A configuration screen with fields to edit how a particular route is mapped to a particular service.

Configure

Define routing rules and load balancer strategies for any service and shift traffic across the entire mesh in seconds. Replicate sophisticated resilience techniques from your most battle-tested services using circuit breakers, retries, rate limiting, and more.

Houston is ready for the enterprise, with built-in support for multiple regions (zones) and organizational tools for complex routing topologies

A set of lines on a chart showing behavior of the different endpoints within a single software service.

Collaborate

Track and manage your SLOs, and see the impact of your service on other teams. Houston’s traffic shifting makes it easy to test in production, including metrics to compare versions. Slowly release new code with canary support, blue/green releases, and one-click rollbacks. Want to test without impacting customers? Download our Chrome extension and switch between deployed versions right in your browser.

With a comprehensive audit log, you can see exactly what happened, whether it was manual or automated.

Turbine Labs logo

Plays Well With Others

Houston leverages your existing service discovery registry to make sure requests are load balanced correctly, even as auto-scaling groups create hosts or as orchestrators reschedule containers across the cluster.

Houston’s advanced routing rules are defined by the labels that already exist on your services, whether they’re version tags in Consul, application names in Kubernetes labels, or auto-generated tags on EC2 instances.

DC/OS logo
Kubernetes logo
Amazon Web Services logo
Docker logo
Consul logo
Google Cloud Platform logo
Turbine Labs logo

Tutorial: Kubernetes Install

Walk through launching Houston on Kubernetes in 5 minutes with our CEO Mark McBride.

Try It Now

Get your free 30-day trial of Houston today.