RelativityOne Sandbox

Note: This functionality is not currently available for FedRAMP customers / government entities.

RelativityOne Sandbox refers to a dedicated RelativityOne environment intended for functional testing of custom apps, and early access to upcoming breaking changes to Relativity. You can test SQL scripts, event handlers, API based applications, custom pages, and custom agents on the same architecture and infrastructure as production RelativityOne.

You should never put confidential data into Sandbox environments

Note:
  • Sandbox is a service that you must subscribe to. Please contact your Account Manager for more details.
  • You should never put confidential data into Sandbox environments.

Accessing Sandbox environments

Instance URLs for the Sandbox environment will be formatted as follows:

  • <customer name>-development.relativity.one

Managing user access to your Sandbox

Sandboxes have the same authentication methods as production RelativityOne environments. You can use the same methods to grant and remove access in Production and Sandboxes.

Upgrades of your Sandbox environments

Breaking changes and updates to the services that make up RelativityOne will be made available in Sandbox environments before production. Most services will deploy changes continuously throughout the month, while some services will only deploy changes during the monthly downtime window.

  • Notification window - you will be notified via Message of the Day (MOTD) only (not by email) prior to the upgrade with proactive steps on how to ensure a successful upgrade.
  • Application errors - if an error occurs during the upgrade of applications, or if you cannot troubleshoot your application or detect a problem with the Relativity APIs after the upgrade, please contact Relativity Support.
  • Workspace errors - if a Workspace cannot be upgraded due to custom application errors, you are given options on how to proceed:
    • Troubleshooting the issue independently using DevHelp forums
    • Open a ticket with Relativity Support (reference the workspace error and that it happened during a Sandbox upgrade)
    • Deleting or disabling the workspace for future upgrades.

Note: If there is a new Windows update available to apply, your system will automatically reboot and apply the updates outside of local business hours (2AM US Central Time).

Sandbox extended downtime windows

RelativityOne Sandbox environments undergo updates and/or version release upgrades during the weeks listed in the following table.

Estimated Date Type Release Name / Version
Week of 2023-11-13 RelativityOne Feature Release 14.10 (December)
Week of 2024-01-22 RelativityOne Feature Release 24.2 (February)
Week of 2024-02-19 RelativityOne Feature Release 24.3 (March)
Week of 2024-03-18 RelativityOne Feature Release 24.4 (April)
Week of 2024-04-15 RelativityOne Feature Release 24.5 (May)
Week of 2024-05-13 RelativityOne Feature Release 24.6 (June)
Week of 2024-06-17 RelativityOne Feature Release 24.7 (July)
Week of 2024-07-22 RelativityOne Feature Release 24.8 (August)
Week of 2024-08-19 RelativityOne Feature Release 24.9 (September)
Week of 2024-09-16 RelativityOne Feature Release 24.10 (October)
Week of 2024-10-21 RelativityOne Feature Release 24.11 (November)
Week of 2024-11-18 RelativityOne Feature Release 24.12 (December)

Using Sandboxes to troubleshoot custom applications

Sandboxes can be very useful for performing tests and reproducing issues with custom applications. If you encounter issues with your custom development, first reproduce the error in a Sandbox and use the available EDDS logging (legacy Sandboxes) or Log Extractor (new Sandboxes) to understand the root cause. The topic Debugging custom applications and support for custom applications provides guidance for how to troubleshoot and verify your custom code.

Differences between production and Sandbox environments

Infrastructure

Sandbox environments are based on the same architecture as production RelativityOne environments. Sandboxes are intended for functional testing and not performance testing, and include service limits that are not present in production RelativityOne environments, such as:

  • 10,000 documents per workspace, and 128GB total file storage
  • 32GB SQL storage, and limited SQL query throughput
  • No backups or redundancy for any data stored in a Sandbox
  • Reduced Agent start rate
  • Reduced Processing throughput
  • No Disaster Recovery

The table below lists technical specification differences between Production, Sandboxes and the prior, legacy Sandbox environments.

Infrastructure Production Sandbox Legacy Sandbox
Web Servers 2-8 1 1
Agent Servers Deprecated Deprecated Same as Web Server
Invariant/Processing Dynamic Workers Dynamic Workers Legacy Processing living on ‘web server’
File ADLS ADLS ADLS
SQL 1x EDDS / 1+ W / 1x INV / 1x Analytics 1x EDDS / 1+ W / 1x INV / 1x Analytics
(increased stacking density)
1x EDDS / 1+ W / 1x INV / 1x Analytics
(increased stacking density)
Network Internal App Gateway/External app gateway/Kong/firewall Internal App Gateway/External app gateway/Kong/firewall Internal App Gateway
Agents

Cloud Compute

Limits per agent GUID: 64 running concurrently, 10 starts per minute

Default Size: 1 CPU and 1 GB

Cloud Compute

Limits per agent GUID: 2 running concurrently, 1 start per minute

Default Size: 0.5 CPU and 0.5 GB

In-tenant Agents

Limits per agent GUID: 64 running concurrently, 10 starts per minute

Other Kubernetes Services No Applicable Limits Limited to <= 2 CPU and 4 GB No Applicable Limits
Authentication Relativity Identity Services Relativity Identity Services Custom configuration for Legacy Sandbox
Application Logging Data Internal observability tool Internal observability tool EDDSlogging (SQL)
Developer Logging Data Access N/A - indirect access to logging data is provided through Log Extractor Log Extractor (with EDDSLogging available by request) EDDSlogging (SQL)
    Notes:
  • RelativityOne Sandbox is a functional test environment and not intended for performance testing.
  • Sandbox environments do not support client domains.
  • The region your Sandbox instance is deployed in may not match your RelativityOne deployment region. Please reach out to Support if you have questions.
  • Utility Server is not available in Sandboxes

  • Visual Studio Remote Debugging is not currently supported in Sandbox environments

Note: Visual Studio Remote Debugging is not currently allowed in Sandbox environments.

Sandbox Support policies

Sandbox environments do not have the same service level agreements as RelativityOne production instances.

Sandbox environments are considered testing environments. Issues with your primary RelativityOne production instances will always take precedence over a similar issue in a Sandbox environment. Furthermore, there is no such thing as a catastrophic or NIA incident for these environments. Response speed will be based on the relevant Relativity team handling the issue and their availability. Additionally, Relativity does not offer performance support for Sandbox environments (as noted in the Infrastructure section).