Multimodal foundation model for oncology. M-Optimus-1 turns a routine H&E slide into ~6,000-gene spatial expression readouts. Pre-trained on millions of proprietary H&E whole-slide images (50+ tissues) plus paired patient cohorts with aligned H&E, bulk RNA-seq, and spatial transcriptomics.
Use M-Optimus-1 to build oncology models from H&E whole-slide images, optionally paired with bulk RNA-seq. Generate multimodal embeddings and reconstruct spatial gene expression across a curated panel of 6,000+ genes.
M-Optimus-1 is a multimodal foundation model for oncology, learning cross-modal representations across H&E, bulk RNA-seq, and spatial transcriptomics. Pre-trained using a unique proprietary dataset comprising millions of H&E whole slide images from more than 50 organ tissues, and thousands of patient records where H&E, bulk and spatial transcriptomics are paired and aligned.
Deploy M-Optimus-1 as an Amazon SageMaker model package inside your AWS account. Run real-time inference via SageMaker endpoints or batch inference on S3. Your data stays private, and is never accessed by Bioptimus.
Highlights
M-Optimus-1 is a multimodal, multiscale foundation model for oncology that integrates information across H&E, bulk RNA-seq and spatial transcriptomics (10x Genomics Visium) to produce tile-, slide, and patient-level outputs.
M-Optimus-1 can perform direct prediction from H&E (with optional bulk RNA-seq) to spatial expression across a curated pan-tissue panel of over 6,000 genes - tumor and immune cell biomarkers, cell-cell interactions, ligands and receptors, biological pathways, and drug candidates.
M-Optimus-1 is multimodal by design, flexible in deployment. H&E-only inference still outperforms unimodal baselines when sequencing data is unavailable.
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
You pay based on usage, with three pricing dimensions. Two are host-hour charges for running batch inference on the model. One covers the ml.g5.xlarge instance type, and the other covers the larger ml.g5.2xlarge instance type. You pick the instance size that fits your workload, and you pay for each hour the host runs. The third dimension charges per inference request, so cost scales with the number of predictions you make. There is no upfront commitment; charges accrue as you use each option.
Top-of-mind questions for buyers
What does one inference request cover for the request-based dimension?
Each request meters one prediction run through the model. The model reads a routine H&E slide, and optionally adds bulk RNA-seq when available, then predicts spatial gene activity across thousands of genes. One submitted prediction task counts as one billable request.
Am I charged when the batch inference host sits idle between jobs?
The host-hour dimensions meter each hour the ml.g5.xlarge or ml.g5.2xlarge instance runs. Charges accrue while the host is active. If you stop the host, software host-hour charges stop, though underlying AWS storage fees may still apply separately.
How do the host-hour charges combine with the per-request charge on my bill?
The two charge types bill independently and appear together. You pay host-hours for the time your chosen instance runs batch inference, plus a separate charge per inference request. Longer-running batch jobs push host-hour cost up, while request volume drives the per-request cost.
bioptimus.com
Helpful?
Vendor refund policy
Non-refundable
How can we make this page better?
Tell us how we can improve this page, or report an issue with this product.
Give us feedbackReport a problem with this product or seller
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA).
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
An Amazon SageMaker model package is a pre-trained machine learning model ready to use without additional training. Use the model package to create a model on Amazon SageMaker for real-time inference or batch processing. Amazon SageMaker is a fully managed platform for building, training, and deploying machine learning models at scale.
Deploy the model on Amazon SageMaker AI using the following options:
Real-time inference
Deploy the model as an API endpoint for your applications. When you send data to the endpoint, SageMaker processes it and returns results by API response. The endpoint runs continuously until you delete it. You're billed for software and SageMaker infrastructure costs while the endpoint runs. AWS Marketplace models don't support Amazon SageMaker Asynchronous Inference. For more information, see Deploy models for real-time inference .
Batch transform
Deploy the model to process batches of data stored in Amazon Simple Storage Service (Amazon S3). SageMaker runs the job, processes your data, and returns results to Amazon S3. When complete, SageMaker stops the model. You're billed for software and SageMaker infrastructure costs only during the batch job. Duration depends on your model, instance type, and dataset size. AWS Marketplace models don't support Amazon SageMaker Asynchronous Inference. For more information, see Batch transform for inference with Amazon SageMaker AI .
Version release notes
v1.0.1
Minor stability fixes
Additional details
Inputs
Outputs
Usage instructions
Sample notebooks
Inputs
Summary
Required: H&E whole-slide images at 224×224 px tiles, 0.5 MPP. Optional: H&E tiles at 512x512 px 8 MPP for tissue segmentation model.
Optional: paired bulk RNA-seq (.csv / .tsv / .txt / .h5ad). Exact Ensembl IDs match to the supported Ensembl ID list (see sample input data for details).
All inputs should be base64 encoded json files. Inputs can contain multiple tiles at a time (jsonl format), however the total file size should not exceed 100MB for batch jobs and 6MB for real-time jobs.
Limitations for input type
Inputs must be in the specified json format with base64 encoded images. Please see sample input files for details.
**Input MIME type:** application/json
The following table describes supported input data fields for real-time inference and batch transform.
1
2
Field name
Description
Constraints
Required
image_data
Base64-encoded PNG of the tile
Type: string
Yes
slide_name
Identifier for the source slide
Type: string
Yes
x
Tile x-coordinate in the slide
Type: int
Yes
y
Tile y-coordinate in the slide
Type: int
Yes
width
Tile width in pixels
Type: int
Yes
height
Tile height in pixels
Type: int
Yes
patch_idx
Index of this tile
Type: int
Yes
model_name
Name of the model must be "m-optimus"
Type: string
Yes
mode
"prediction" (for gene expression) or "embedding"
Type: string
Yes
bulk_rna
Bulk RNA counts vector. If omitted, the server substitutes zeros. Must be in the exact gene order from the model's input_gene_set.csv. Pre-processed as log1p before passing to the model - so this should be raw counts.
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Be the first to review this product. We've partnered with PeerSpot to gather customer feedback. You can share your experience by writing or recording a review, or scheduling a call with a PeerSpot analyst.