AWS Software / SaaS United States

Remote Legal

Document Processing

Remote Legal needed a reliable and cost-efficient way to run remote depositions, deliver accurate real-time transcription, and keep legal proceedings stable enough that sessions could start and finish on the platform without costly failures.

1 week migration to Amazon Transcribe
10 months to build a remote deposition solution
85% cost savings
98% success rate

Reported impact

Business outcome

Remote Legal built the solution in 10 months, migrated to Amazon Transcribe in 1 week, virtually removed transcription errors, achieved a 98 percent deposition success rate, and cut testing and demo costs by 85 percent through automation on AWS.

  • Cost Reduction
  • Customer Experience
  • Scalability
  • Speed to Market

Solution

Remote Legal built its remote deposition platform on AWS using ASP.NET Core SignalR containers on AWS Fargate and an Application Load Balancer to support near-real-time courtroom-style collaboration over the web. Deposition session state and application data are stored in Amazon RDS, while audio from live sessions is sent to Amazon Transcribe to generate accurate text with seamless integration into the rest of the stack. The team manages the entire environment as infrastructure as code, which lets it recreate identical testing, proof-of-concept, or disaster-recovery environments in new regions quickly. This combination gives Remote Legal a scalable legal-technology platform that can support live depositions, simplify transcription, and keep reliability high without managing servers.

Data flow

Deposition participants connect through the web application running on AWS Fargate behind an Application Load Balancer, deposition data is stored in Amazon RDS, and live speech is sent to Amazon Transcribe so the platform can return accurate text during proceedings.

Solution architecture

4 components · 3 layers
  1. Compute
    • AWS Fargate Runs the containerized ASP.NET Core SignalR application without server management.
    • Amazon Transcribe Converts live deposition speech to text as part of the platform workflow.
  2. Storage
    • Amazon RDS Stores Remote Legal's application and deposition data.
  3. Serving
    • Application Load Balancer Routes deposition traffic to the application based on request content.

Architecture clues

  • Can recreate identical environments in new regions for disaster recovery.
  • Entire architecture is managed as infrastructure as code.
  • Runs ASP.NET Core SignalR on Linux for cost and performance.

Evidence from the source

In 1 week, the team completed the migration ... and virtually removed transcription errors.
Remote Legal built its solution in 10 months using ASP.NET Core SignalR for near-real-time web functionality in addition to managed services on AWS.
Remote Legal used AWS Fargate ... and Application Load Balancer.
The Remote Legal team chose Amazon Transcribe ... to replace its previous transcription service.
This reduced Remote Legal’s costs by 85 percent compared with the cost of the production environment.
the solution reached a 98 percent success rate
Transparency Evidence & methodology 100/100 reference value · 92% confidence · 3 sources

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value100/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    3 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence92%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability25/25
    12 of 12 key fields link to a named source.
  • Direct evidence20/20
    6 direct source quotes retained.
  • Date provenance8/10
    The publication date comes from publisher-controlled metadata.
  • Source transparency9/10
    3 source references document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. AWS

    Remote Legal customer story

    First-party
    https://aws.amazon.com/solutions/case-studies/remote-legal-case-study/
    Source type
    Vendor-published customer story
    Published
    Jan 9, 2024
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date
  2. Remote Legal

    Contact Remote Legal | Remote Legal

    First-party
    https://remotelegal.com/contact-us/

    The contact page lists "11 Broadway, Suite 468 New York, NY 10004," placing Remote Legal in the United States.

    Source type
    Official company website
    Supports
    • Region
  3. LeadIQ

    Remote Legal Court Reporting Employee Directory, Headcount & Staff | LeadIQ

    Independent secondary
    https://leadiq.com/c/remote-legal-court-reporting/610d8098799f6532db4da3b2/employee-directory

    LeadIQ says Remote Legal Court Reporting has approximately 82 employees as of August 2026, and the Organization JSON-LD lists numberOfEmployees value 82.

    Source type
    Structured company profile
    Supports
    • Company size

Date evidence

Not separately sourced Industry. Treat these normalized attributes as lower-confidence until a dedicated source is added.