A Sitecore Partner can purchase Content Hub Sandbox to use it for custom demos, proof of concepts, training, or any other non-commercial use. This article describes the scope of Sitecore's Content Hub Sandbox support.
Notes:
- If you need to use the Sitecore sample "Play Summit" demo with assets and workflows prebuilt, use the Demo Portal instead.
- If you register for the Content Hub mock training, a sandbox will be provided prior to the beginning of classes. Sandboxes can be used to try out different features of Content Hub (or other products available through our portal). Sitecore does not engage on any SLAs around the uptime of these sandboxes or delivery of fixes relating to their underlying infrastructure or product bugs. Sitecore provides a complete Content Hub environment in the Sandbox portal at https://siteco.re/ch-sandbox
- A credit card is required to pay for a sandbox and it will take an initial deposit hold, but will not charge the card. At the end of the first and subsequent months, you will be billed for actual usage.
- You can stop sandboxes when they are not in use or delete unnecessary sandboxes. Idle sandboxes are stopped but not deleted, and they will incur a 10% monthly fee to maintain storage and IP addresses.
- Sandboxes cannot be used as a lower-level environment for a customer's production instance. A sandbox is not a non-prod environment. Test data cannot be copied down from a production instance into the partner sandboxes. Configurations or data cannot be copied up to production environments.
- Sandboxes can be managed by partners with a valid Okta account at https://partners.sitecore.com/ There are the sandbox training materials for how to create the correct version depending on use.
- Sandboxes should not be shared concurrently. They are not built for performance, only for demo and training purposes. To take the training, each administrator or developer should have their own sandbox. If you wish to add extra users to your sandbox, follow the documentation.
- Sandboxes are not supported under any SLA, and any questions or issues are addressed in a best-effort manner.
- The sandbox environments have very limited resources and shall not be used for heavy activities that could result in performance degradation.
All the relevant documentation on how to use the Sandbox portal can be found under the following URL: https://create.stylelabs.io/docs
Sitecore defines support as the investigation and resolution of difficulties with using Sitecore Content Hub Sandbox. Support does not include consulting services or training of any kind.
In Scope
- Functional issues and bug confirmation around Content Hub utilization (not delivery of fixes).
- Proposal of a workaround when applicable for bugs or issues relating to the underlying infrastructure.
- Issues related to maintaining Content Hub sandboxes (for example, issues with creating, deleting, restarting, and so on) on the Sandbox Content Hub portal are investigated, but they are not supported under any SLA.
Scope of Partner Technical Advisor (PTA) team
- Changing of the ownership.
- Any changes around financial matters.
Not in scope
- Sandboxes that are running any version that is not actively supported by Sitecore.
- Any data manipulations on sandboxes (like Data movement or Data recovery).
- If sandboxes are corrupted, Sitecore cannot guarantee the possibility of restoring sandboxes. It is recommended to take intermediate snapshots on sandboxes to be able to restore to different timestamps.
- The upgrade feature is experimental and we cannot guarantee a successful upgrade of sandboxes.
- Renaming sandboxes.
- Working on cases relating to the functionality of the Import and Export package feature.
- Assistance for sandboxes used as Development or QA environment and used to feed data to a production environment.
- Performance-related issues:
- Uploading of large and heavy files that require a lot of computational power (for example, 4K movies, large images, such us 4Kpx4Kp).
- The infrastructure consumed by sandboxes is not meant for production use and Sitecore cannot engage in the delivery of Root Cause Analysis in all cases.