Skip to content

How to choose Cloud or Studio

Cloud is hosted by Omseek and fits fast start and continuous upgrades. Studio is customer-controlled and fits data residency and private networks. Migration needs a Portable Archive and explicit rebinding. Unconditional move is not promised.

Applies to:Public product description as of 2026-09-28 · Updated 2026-09-28 · Maintained by Omseek documentation

How to choose

Cloud and Studio share one product core. They differ in where they run, where data stays by default, who upgrades the system and which network conditions apply. They do not fork business meaning.

TopicCloudStudio
EnvironmentOmseek-hosted multi-tenant serviceCustomer-controlled deployment
Default data locationStored under the hosted agreementBusiness content and raw evidence stay in the customer environment by default
UpgradesContinuous product upgradesUpgrades follow entitlement and the version catalog
Cloud assistPlatform capabilities follow entitlementBusiness content is not uploaded by default; cloud assist needs explicit authorization
MaintenanceInfrastructure is hostedThe customer operates the environment; after maintenance ends the current version can keep running within the license

When Cloud fits

Choose Cloud when the organization needs to start diagnosis, content and publishing quickly and can accept hosted deployment. Cloud is purchased by capability domain and connects existing sites and sources.

When Studio fits

Choose Studio when the organization requires data residency, a private network or independent brand control. Studio supports offline and restricted-network operations. Business content is not uploaded to Omseek Cloud by default.

Migration conditions

Cloud can move to Studio through a Portable Archive. The archive carries business objects, content, evidence indexes and configuration inventories. Credentials and external connections must be rebound. Secrets are not copied.

  1. Confirm tenant, entitlements and data scope.
  2. Export archive objects and check completeness.
  3. Deploy Studio in the target environment and complete license activation.
  4. Rebind connections and secrets.
  5. Check consistency before switching traffic, and keep a rollback window.

Sources

Related

Contact