Manage tenanted deployments how it best suits you. Deploy to one tenant, some, or all at once, or specific release rings, based on defined tenant tags.
See environments in the demo project)
Scale deployments quickly, reliably, and securely for all locations without duplicating your effort.
Managing deployments to hundreds or thousands of locations is complex when each location has its own needs. Regional, system, or timing differences can slow you down and cause duplication.
Complex deployments like these are simpler with Octopus Deploy's built-in Tenants feature. Octopus helps you deploy easily to any number of stores, hospitals, banks, or branches and manage those needs with one deployment process.
Imagine you're deploying software to thousands of retail stores around the world. Each will have unique requirements. Time zones alone mean they'll have different opening hours and outage windows. Stores may also use different Point of Sale (PoS) systems or hardware.
You can manage these unique needs with a tenanted deployment strategy. Manual tenanted deployments (and those done in other CI/CD solutions) mean using a separate deployment process for every location.
That's manageable if you only deliver software to a handful of locations. Start scaling to dozens or hundreds and you can run into problems.
A lack of flexibility makes adding new locations to your processes even harder.
You must duplicate deployments and change the configuration for each new location. This is time-consuming and increases the likelihood of mistakes, which you might iterate on.
It's difficult to see what release deployed where, causing project-management problems.
Before Octopus, we had no visibility of our deployments. Now, we have a single-pane view of all our deployments and tenants in one place across all our environments. It has really helped us to cross the boundary between non-production and production within our organization.
In Octopus, each physical location becomes a tenant. You define a deployment process once and use it for all tenants.
Simplifying the deployment process - Define the deployment process once and use it to deploy all configurations.
Grouping similar locations - Group locations with tenant tags to manage deployments at scale. Tenant tags reduce the time it takes to add new locations to the deployment process and reduce risk.
Making deployment processes flexible - Use variables to customize the deployment process to suit the needs of each location. Make changes to any tenant without straying off from your defined process.
Offering complete visibility for all locations - See what release deployed where at a glance, any time.
Since having Octopus, we’ve been able to break out some of our services using tenants, and this means that we can deploy more frequently and easily. We’ve gone from a single, monolithic deployment per quarter to more ad hoc deployments, which means more frequent upgrades for customers.
With Octopus, you can use one process to deploy to hundreds or thousands of tenants, stores, hospitals, or branches.
Manage tenanted deployments how it best suits you. Deploy to one tenant, some, or all at once, or specific release rings, based on defined tenant tags.
See environments in the demo projectDefine one deployment process, seamlessly connect it to either side of your deployment pipeline, and use it for as many customers or locations as you need. Manage each tenant's unique processes, customizations, and features using tenant tags and variables.
See a deployment process in the demo projectDefine variable values, like database connection strings or API keys, that are different for each tenant in your project.
See tenant variables in the demo projectUse Octopus's Runbooks feature to automate tenants and infrastructure provisioning whenever needed. Manage backups, database maintenance, and service failover and restoration with one click.
See a runbook process in the demo projectKnow where your releases are, regardless of your multi-tenancy strategy. See key information about your tenants at a glance, like the projects they belong to, assigned tags, and environments for each tenant.
See the tenant dashboard in the demo projectOlo's software enables restaurants, convenience stores, and supermarkets to scale online ordering and delivery. It also lets them make data-driven business decisions and personalize the guest experience on and off-premises.
Read their storyGuestline reduced manual work, saved thousands of hours, and delivered a world-class customer and developer experience.
Read their storyKinderSystems needed to support cloud and on-premises deployments and reduce manual work.
Read their storyReduce the complexity of tenanted deployments. Define your process once and scale across your customers.
All fields are required.
We'll never share your email or spam you.
Start your free 30-day trial and get access to all Octopus Professional features.
Have questions about how tenanted deployments will work for you, or want to see a live demo?
Read our guides to get started with tenanted deployments in Octopus. You can also access our sample tenant projects in the Octopus samples instance.
Learn how to use the Tenants feature to support multiple teams developing the same application.
Read moreLearn how to use geographic locations as tenants for an application and different upgrade rings.
Read moreLearn how to set up Software as a Service (SaaS) tenanted deployments in Octopus.
Read more