AWS Healthcare United States

Nimbus Therapeutics

Application Refactoring · IT Operations Automation · Real-time Analytics · System Migration

Modern ML offers a complementary approach to predicting costly experimental outcomes and biasing molecular design toward more drug-like properties by learning historic experimental trends, which are published in scientific literature, patent applications, and proprietary datasets. “It’s expensive and time-consuming to synthesize and test compounds,” says Dan Price, vice president of Computational Chemistry and Struct

Reported impact

Business outcome

Nimbus has successfully automated a suite of ML models to predict different aspects of drug exposure and safety, which are actively influencing design across all discovery projects. The predictions provided through LiveDesign democratize the technology across all Nimbus scientists, regardless of discipline or technical background. However, the infrastructure isn’t specific to LiveDesign.

  • Productivity Improvement
  • Scalability
  • Speed to Market

Solution

With established expertise in computational chemistry and machine learning (ML), Nimbus Therapeutics (Nimbus) sought to further accelerate its drug discovery engine by automating the operational aspects of ML (MLOps). Minimizing manual intervention in model training and deployment would help its scientists to focus on Nimbus’s core mission: the design of breakthrough medicines. Learn how computational chemists at Nimbus Therapeutics built an agile and effective ML pipeline using Amazon SageMaker. Nimbus turned to Amazon Web Services (AWS) to use Amazon SageMaker , which lets organizations build, train, and deploy ML models for any use case with fully managed infrastructure, tools, and workflows. To orchestrate communication with LiveDesign, the team used Amazon API Gateway , a fully managed service that makes it easy for developers to create, publish, maintain, monitor, and secure APIs at any scale. Amazon API Gateway used the serverless

Data flow

processing runs on Amazon SageMaker, AWS Lambda; and outputs are exposed through Amazon API Gateway for the cloud migration workload.

Solution architecture

3 components · 2 layers
  1. Compute
    • Amazon SageMaker Runs core compute or model execution for the cloud migration workload.
    • AWS Lambda Runs core compute or model execution for the cloud migration workload.
  2. Serving
    • Amazon API Gateway Provides the delivery or user-facing interface for the cloud migration workload.

Architecture clues

  • Amazon API Gateway used the serverless functionality of AWS Lambda , which lets organizations run code without thinking about servers or clusters, to provide near real-time inference from Amazon SageMaker endpoints.
  • Nimbus turned to Amazon Web Services (AWS) to use Amazon SageMaker , which lets organizations build, train, and deploy ML models for any use case with fully managed infrastructure, tools, and workflows.
  • To orchestrate communication with LiveDesign, the team used Amazon API Gateway , a fully managed service that makes it easy for developers to create, publish, maintain, monitor, and secure APIs at any scale.
  • Working with their own IT team and with AWS specialists, Nimbus scientists built on this foundation by automating the pilot with Amazon SageMaker Pipelines , a serverless workflow orchestration service purpose built for MLOps automation.

Evidence from the source

Many data sources in the pharmaceutical domain are small, inherently heterogenous, and missing key structured metadata.
Modern ML offers a complementary approach to predicting costly experimental outcomes and biasing molecular design toward more drug-like properties by learning historic experimental trends, which are published in scientific literature, patent applications, and proprietary datasets. “It’s expensive and time-consuming to synthesize and test compounds,” says Dan Price, vice president of Computational Chemistry and Struct
Nimbus considered it critical to codify domain-expert rules for metadata extraction and criteria for inclusion and exclusion to sustainably deliver performant models.
The pipeline would provide near real-time predictions through Schrödinger’s LiveDesign, an application where new molecular designs are captured and evaluated.
The team at Nimbus imagined an automated pipeline that would regularly curate data from a variety of sources and retrain and redeploy ML models.
The team needed to quickly demonstrate whether the available data, combined with its curation and modeling strategies, could meaningfully impact programs and warrant a larger investment in time and resources.
Transparency Evidence & methodology 66/100 reference value · 91% confidence · 4 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 value66/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth20/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity16/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact0/25
    0 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence91%
  • 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 transparency10/10
    4 source references document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity8/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

    Nimbus Therapeutics customer story

    First-party
    https://aws.amazon.com/solutions/case-studies/nimbus-therapeutics/
    Source type
    Vendor-published customer story
    Published
    Dec 13, 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. Nimbus Therapeutics

    Homepage - Nimbus Therapeutics

    First-party
    https://www.nimbustx.com/

    The official website footer lists '22 Boston Wharf Road, Floor 9, Boston, MA 02210 USA,' supporting a United States headquarters.

    Source type
    Official company website
    Supports
    • Region
  3. Nimbus Therapeutics

    Contact

    First-party
    https://www.nimbustx.com/contact/

    The official contact page lists "22 Boston Wharf Road, Floor 9 Boston, MA 02210 USA."

    Source type
    Official contact page
    Supports
    • Region
  4. LinkedIn

    Nimbus Therapeutics | LinkedIn

    Independent secondary
    https://www.linkedin.com/company/nimbus-therapeutics/

    LinkedIn's Organization JSON-LD lists addressLocality "Boston", addressCountry "US", and numberOfEmployees value 103.

    Source type
    Structured company profile
    Supports
    • Region
    • Company size

Date evidence

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