Developer Environment(Tenant)
J
JR Dawkins
A dedicated dev tenant that is assigned/uses it's own credits with the ability to share/push Workflows/Apps/Agents to any tenant under the master tenant.
Currently our master tenant is the same tenant our employees are in and this makes things complicated when it comes to dev work.
- As we are testing workflows for our clients (sub-tenants) we're burning through the credits for our employees.
- If models are turned off to restrict employee use (nano banana) it's not available for development since it's a global on or off.
I propose a dev.hatz.ai (or something like that) be available for the master tenant so that there's a better structure around building solutions for both our team and our clients.
P
Prabhat
I support this feature. furthermore, there should be a way to deploy[export/import] the work from Dev tenant Prod[targeted] tenant so that the sharing is easier and no copy pasting errors are there. currently, whatever we are doing is all in prod, consuming prod credits and there is no segregation of the Dev and production deployed work.