We are a new startup that is about to go live with our first release in the near future.
At present we have been using 1 tenant per environment as advised here. This set up has worked well to get our application functionally ready but as go-live approaches we need to test other aspects that require our Auth0 subscription to be upgraded to the level it will need to be in production.
So far so good.
My problem/question hinges on how we can test aspects or our application, notably using custom domains and customised email templates, using a free subscription for pre-production environments.
As far as I can see, given that we (will) have 3 environments - Dev, QA and Production - we will need 3 paid-for Auth0 tenants in order to test this functionality. This essentially triples our costs on Auth0, which is something as a small startup we do not really have the resources to do.
Is there any way we can test these areas whilst still using a free tenant in the pre-production environments, or is this simply not possible?
If not I think we will have to combine our Dev and QA Auth0 tenants into a single tenant and somehow separate our environments internally using a different connection db for each one. At least that way we only need 2 paid-for tenants.
Another possibility is using a child tenant for our QA environment. I see that a child tenant is available if our monthly payments to Auth0 exceed a certain threshold - is this threshold movable? Can we request one (or more child tenants) whilst our monthly billing is below this threshold knowing that it will incur additional cost?
Thanks in advance