
A request for 2 TB of RelativityOne hosting can look straightforward until the matter includes mobile collections, Microsoft 365 data, multiple custodians, rolling productions, and a review team spread across several firms. That is why the question, “how much does it cost for RelativityOne per month?” rarely has a single public-dollar answer.
RelativityOne pricing is generally quote-based and depends on the commercial agreement, data profile, required capabilities, and level of service behind the workspace. For legal teams, the more useful question is not simply the monthly platform rate. It is: what will this matter cost from collection through defensible production, and which choices will change that cost?
Why RelativityOne monthly pricing is not a fixed number
RelativityOne is an enterprise eDiscovery platform delivered through authorized providers and service partners. Pricing is commonly structured around data volume, platform use, and matter-specific services rather than a simple published per-user subscription.
A monthly invoice may include hosted data, active workspaces, user access, and optional technology features. It may also reflect work performed before review begins, such as forensic collection, data transfer, processing, quality control, load-file preparation, and production support. A low hosting rate can be misleading if those adjacent steps create unpredictable charges or force the legal team to engage separate vendors.
Commercial terms also matter. Some organizations negotiate annual commitments, minimum monthly volumes, enterprise arrangements, or bundled managed-service packages. Others need a workspace for one investigation or litigation matter. The same number of gigabytes can produce very different costs depending on whether the data is raw, processed, actively reviewed, archived, or awaiting production.
What drives the cost of RelativityOne per month?
The largest driver is usually the volume and state of data. Raw source data is not the same as processed, searchable, review-ready data. A compressed email archive, for example, can expand substantially during extraction and processing. Native files, extracted text, metadata, duplicates, family relationships, and analytics indexes all affect the amount of information maintained in a matter.
Data type also affects effort. Standard office documents may process predictably, while encrypted files, scanned PDFs, mobile-device data, chat exports, cloud collaboration content, and unusual file types can require additional handling. When a case involves modern data sources, the cost question must account for defensible collection and normalization, not just the destination platform.
The second major driver is the review workflow. A small team performing straightforward responsiveness review will use the platform differently than a large, multi-party case with second-level review, privilege logs, redactions, translated documents, rolling productions, and complex permissions. Features such as email threading, near-duplicate identification, conceptual analytics, and active learning can add cost, but they can also reduce the number of documents requiring attorney review. The right comparison is total matter spend, not the price of one feature in isolation.
Third, user administration and support requirements can affect the monthly total. Some teams are equipped to configure fields, permissions, searches, batches, and productions internally. Others benefit from dedicated project management, review support, or after-hours response during a critical filing deadline. Managed support is an additional service, but it can prevent costly workflow errors and reduce the burden on internal legal operations staff.
Finally, timing changes the economics. A matter with steady monthly data volume is easier to budget than a subpoena response requiring immediate collection, expedited processing, and a production in ten days. Rush work, frequent data reloads, late custodian additions, and shifting review protocols can all create charges that are not visible in an initial storage estimate.
Separate platform costs from matter costs
For a useful budget, separate recurring platform costs from one-time or variable matter costs. This makes it easier to compare proposals and identify which expenses will increase if the case expands.
Recurring charges may include active hosted data, user access, workspace availability, and contracted platform services. Variable charges often include data collection, processing, exception handling, image conversion, production creation, project management, and specialized analytics or review services.
That distinction is especially important when evaluating a quote based on a per-gigabyte amount. Ask what the gigabyte measurement represents. Is it collected source data, processed data, active hosted data, or another defined metric? Ask whether de-duplication occurs before hosting charges are calculated, how deleted or archived data is treated, and whether minimums apply.
A transparent estimate should also identify what happens when a matter changes. If the data doubles, does the rate change? If documents are moved to archive, does the monthly cost fall? Are productions, exports, or data transfers billed separately? These are practical operational questions, not procurement technicalities. They determine whether the monthly number remains predictable after the first invoice.
How to build a defensible RelativityOne budget
Start with a short data assessment. Identify likely custodians, source systems, estimated raw volume, date ranges, file types, and expected collection methods. Do not rely solely on mailbox quotas or drive capacity. Those figures often overstate or understate what will ultimately be collected and processed.
Next, define the review design before requesting pricing. Estimate the number of reviewers, expected duration, production cadence, security groups, and whether the matter requires redaction, privilege logging, foreign-language review, or advanced analytics. A provider can price more accurately when the legal team identifies how the workspace will actually be used.
Then ask for a scope-based estimate with assumptions stated in writing. The estimate should make clear which services are included, which are optional, and what event triggers an additional charge. It should account for both the initial data load and the likely pattern of rolling collections. For investigations and regulatory matters, include preservation and collection requirements early. A later decision to collect phones, cloud accounts, or departing-employee devices can materially change the cost profile.
It is also wise to model two scenarios: an expected case and a high-volume case. The expected case may assume a defined custodian set and ordinary review timeline. The high-volume case should account for expanded date ranges, additional custodians, duplicate data sources, or a compressed deadline. This approach gives counsel and legal operations a credible range without treating an early estimate as a guarantee.
Cost control without compromising defensibility
The least expensive gigabyte is often the one that never reaches review. Targeted collection, defensible culling, date restrictions, negotiated search terms, and early duplicate reduction can reduce data before it creates recurring hosting and review costs. These decisions must be documented and appropriate to the legal obligation, but they are central to proportional discovery.
Processing choices matter as well. Deduplicating across custodians can reduce review volume, though the team must preserve enough information to understand who possessed a document. Email threading can focus reviewers on inclusive messages. Near-duplicate analysis can surface document families that may be reviewed consistently. Applied thoughtfully, these workflows reduce repetitive attorney time while maintaining an auditable process.
Avoid treating low-cost hosting as the only purchasing criterion. Fragmenting collection, processing, hosting, and production across disconnected providers may create handoffs, data movement, and accountability gaps that cost more than they save. An integrated workflow also gives the project team a clearer view of chain of custody, processing decisions, and production history.
For many matters, the best value comes from combining the right platform configuration with experienced human guidance. ViewDox helps teams evaluate the entire workflow, from secure forensic collection through processing, review, and production, so cost controls do not create avoidable risk.
Questions to ask before approving a quote
Before committing to a RelativityOne arrangement, ask the provider to explain the billing unit, included data services, minimum commitments, archive options, user and workspace assumptions, support model, and charges associated with productions or exports. Request a clear explanation of how processed volume is calculated and whether analytics, imaging, OCR, redactions, or project management are included.
Also ask who will own the day-to-day matter configuration. A platform can be powerful, but someone must manage permissions, troubleshoot data exceptions, monitor processing, create batches, and validate productions. Knowing whether that responsibility sits with your internal team, outside counsel, or a managed-services partner is essential to a realistic monthly budget.
The most reliable cost estimate begins with a conversation about the evidence, the legal timeline, and the review strategy. When those facts are defined early, RelativityOne can be priced as part of a controlled, defensible eDiscovery workflow rather than as an isolated monthly line item.
