<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Should I run multiple environments in different tenants or different instances?]]></title><description><![CDATA[<p dir="auto">When evaluating and developing against FusionAuth, I have set up different tenants for development and staging and production. This is also outlined here: <a href="https://fusionauth.io/blog/2018/09/24/multi-tenancy-in-a-single-tenant-architecture/" rel="nofollow ugc">https://fusionauth.io/blog/2018/09/24/multi-tenancy-in-a-single-tenant-architecture/</a></p>
<p dir="auto">Is this the way you would recommend, or should we run three instances?</p>
]]></description><link>https://fusionauth.io/community/forum/topic/1065/should-i-run-multiple-environments-in-different-tenants-or-different-instances</link><generator>RSS for Node</generator><lastBuildDate>Thu, 10 Sep 2026 16:11:53 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/topic/1065.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 03 Jun 2021 13:56:35 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Should I run multiple environments in different tenants or different instances? on Thu, 03 Jun 2021 17:01:54 GMT]]></title><description><![CDATA[<p dir="auto">I'm a former consultant, so the answer is, as always, "it depends".</p>
<p dir="auto">Strengths of running in different tenants:</p>
<ul>
<li>easier to manage (only one instance to run and upgrade)</li>
<li>configuration, such as lambda or identity provider config, can be shared across tenants</li>
<li>cheaper to run (again, only one instance and database to pay for)</li>
</ul>
<p dir="auto">Strengths of running in different instances:</p>
<ul>
<li>true isolation when running</li>
<li>you can allow developers access to the admin ui of the instance</li>
<li>a misconfiguration in development isn't going to affect production</li>
<li>you can have a true IaC approach, where you deploy config changes across environments one at a time</li>
</ul>
<p dir="auto">In general, it makes sense to be careful about production environments, as if any configuration changes are made in error, it can impact the customer experience.</p>
<p dir="auto">It really depends on what works best for you.</p>
]]></description><link>https://fusionauth.io/community/forum/post/3148</link><guid isPermaLink="true">https://fusionauth.io/community/forum/post/3148</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Thu, 03 Jun 2021 17:01:54 GMT</pubDate></item></channel></rss>