1,774
edits
Changes
[[Welcome_to_Veloopti_help|Home]] > [[:Category:An Overview|An Overview]] > [[:Category:Concepts|Concepts]] > [[Multitenancy |Multitenancy ]]
----
== Overview ==
Hosting multiple customers or multiple teams in Veloopti is something that was built into it from the beginning. Veloopti is flexible with managing multiple customers or having multiple monitoring administration teams. There are two ways that we primarily recommend doing this; using multiple organisations or multiple applications.
=== Multiple Organisations ===
Using multiple organisations is preferable when the management of the customers/teams are performed by multiple administration teams.
Use multiple organisations when:
# Different teams manage the Operating Systems of the nodes
# You have multiple monitoring teams
# You want Veloopti to calculate an invoice for each customers/team
=== Multiple applications ===
Using a single organisation and creating one or more applications for each customer/team is useful when the administrators for each customer are the same.
# The same team manages the Operating Systems of the nodes
# You have a single monitoring team
# You want Veloopti to calculate a single invoice
=== Multitenancy ===
By definition: multitenancy is where a single instance of the software serves multiple tenants. The tenants are logically isolated where one tenant cannot see the details of another, but physically run as a single instance of the application.
Veloopti is multitenant in that we have multiple customers (all of you) running on one (actually a few) instance of Veloopti. If we were to allow you to use a instance (we call them a hive) of Veloopti then you would be able to put many customers in that single hive and you would then be offering a Multitennancy version of Veloopti. This is something that we are looking to offer in the future. Contact us if this interests you.
----
== Overview ==
Hosting multiple customers or multiple teams in Veloopti is something that was built into it from the beginning. Veloopti is flexible with managing multiple customers or having multiple monitoring administration teams. There are two ways that we primarily recommend doing this; using multiple organisations or multiple applications.
=== Multiple Organisations ===
Using multiple organisations is preferable when the management of the customers/teams are performed by multiple administration teams.
Use multiple organisations when:
# Different teams manage the Operating Systems of the nodes
# You have multiple monitoring teams
# You want Veloopti to calculate an invoice for each customers/team
=== Multiple applications ===
Using a single organisation and creating one or more applications for each customer/team is useful when the administrators for each customer are the same.
# The same team manages the Operating Systems of the nodes
# You have a single monitoring team
# You want Veloopti to calculate a single invoice
=== Multitenancy ===
By definition: multitenancy is where a single instance of the software serves multiple tenants. The tenants are logically isolated where one tenant cannot see the details of another, but physically run as a single instance of the application.
Veloopti is multitenant in that we have multiple customers (all of you) running on one (actually a few) instance of Veloopti. If we were to allow you to use a instance (we call them a hive) of Veloopti then you would be able to put many customers in that single hive and you would then be offering a Multitennancy version of Veloopti. This is something that we are looking to offer in the future. Contact us if this interests you.