Orchestry provides you with the ability to self host your Insights and Lifecycle Data that is gathered by Orchestry. This means that you are in full control of your data and can revoke access to Orchestry at any time

Orchestry Self-Hosting Technical Documentation

Please see the following document for configuration information:  Orchestry Self-Hosting Guide v1.5

A Warning about Self-Hosting Orchestry Data

While it is possible to move from Orchestry-hosted to self-hosted storage databases while in-flight (i.e.: a tenant that has had Orchestry running for a period of time with the existing storage model), it is not recommended unless the repercussions are well understood as it may result in important data loss.

Impacts

• By moving Orchestry-hosted to self-hosted, the majority of Orchestry's historical data will be lost (i.e.: audit trails, archived workspace history, workspace statistics, etc.)

• By moving to self-hosted (or vice versa), data will begin being captured fresh in blank tables (net new).

• Data IS NOT migrated from one storage DB to another (i.e.: Orchestry Cosmos > Customer Cosmos).

We encourage you to contact the Orchestry support team prior to migrating your data.

Questions and Answers

Can I Choose Where My Orchestry Data is Stored?

When self-hosting Orchestry data, it's critical that your Orchestry region matches the region you provision your Azure Storage in. 

For the lowest latency and best experience, we strongly recommend using the following Primary regions, based on your Orchestry region:

Should the PRIMARY Azure region not be feasible for your organization, the next best option is to use the SECONDARY Azure region that has an alternative location in a nearby geography with low latency. 

Using alternative PRIMARY Azure regions can impact the performance and stability of Orchestry.