SpinForgeA Garmo Labs CompanyDiscuss a workload
Synthesis / Layer 1 / BSPINFORGE / A GARMO LABS COMPANY

AMDE + ALCHEMI

Physics-grounded drug-discovery scoring through GPU molecular dynamics.

Conceptual product artwork for AMDE + ALCHEMI, not physical hardware
Conceptual product artworkDrag to explore ↔
Customer outcomeDesign and discover

THE PRODUCT, IN PRACTICE

Evaluate the candidate.
Bring physics into view.

Candidate generation and candidate evaluation are different responsibilities. AMDE + ALCHEMI brings GPU molecular dynamics into drug-discovery scoring. AMDE is powered by SpinForge Discovery Core; the combined family entry is counted once in the eleven-product synthesis family.

BUILT FOR
Computational drug-discovery teams evaluating candidates with physics-based models.
CHALLENGES → PRODUCT RESPONSE

The problem you face.
What the product changes.

YOUR CHALLENGEWITH AMDE + ALCHEMI
01

A candidate list needs evaluation

A proposed candidate is not yet a measured biological outcome.

AMDE + ALCHEMI supplies physics-grounded scoring through GPU molecular dynamics for the defined discovery workflow.

02

The model determines the score’s meaning

A numerical score is only interpretable with its target, simulation assumptions and evaluation conditions.

Scope the modeled system and scoring comparison so the result can be evaluated alongside other candidate evidence.

03

Shared technology can become invisible

Separate application names can hide the computational foundation they share.

AMDE’s named engine is SpinForge Discovery Core, also used by SpinForge Bio. Application-specific evaluation remains separate.

WHAT YOU GET

A defined capability.
A useful result.

01

Physics-grounded scoring

GPU molecular-dynamics-based scoring for drug-discovery work.

02

A candidate-evaluation role

A distinct contribution from merely generating candidate sequences.

03

Shared Discovery Core

AMDE uses the same named foundation as SpinForge Bio.

04

An agreed research workflow

Define inputs, modeled conditions, outputs and acceptance before the engagement.

EXPLICIT DEPENDENCY

AMDE uses Discovery Core.

AMDE + ALCHEMI remains one Layer 1 family entry. The owner’s clarified dependency is AMDE → SpinForge Discovery Core.

Explore the shared engine
EXAMPLE CUSTOMER WORKFLOW

Evaluate a computational candidate set

A research team wants to compare candidate behavior under an agreed physical model.

Illustrative customer use—not a new benchmark or completed customer deployment.
  1. 01→

    Provide the modeled system, candidates and evaluation objective.

  2. 02→

    Use the supported GPU molecular-dynamics scoring workflow.

  3. 03→

    Review the computational scores with their assumptions and downstream validation plan.

FIT & ACCEPTANCE

Start with the task.
Agree the useful outcome.

What you bring
The target/system representation, candidate inputs, modeled conditions and scoring objective.
What a useful evaluation measures
  • +Numerical and model consistency
  • +Repeatability under the agreed conditions
  • +Relevance to the downstream research question
Delivery
License the selected capability, commission an implementation, or agree an operated service. Infrastructure and additional engineering are specified separately.
QUESTIONS BEFORE BUYING

A clear scope.
A clear relationship.

What is the important boundary?−

Computational scoring is not evidence of experimental binding, efficacy, toxicity or clinical suitability. Discovery Core is explicitly the engine behind AMDE; no separate unprovided ALCHEMI dependency is invented.

How is it priced?+

No new standalone price is supplied for this product; request a scoped proposal. The platform plans buy qualified workflows and capacity, not a second charge every time a compatible method is selected. Existing bundle inclusions do not expand automatically.

How do we get access?+

An existing product in the SpinForge portfolio. Request the release, available invocation interfaces and setup for your selected workflow; this publication does not invent executable commands or MCP tool names.

PUT THE PRODUCT TO WORK

Tell us what needs to improve.

Bring a task, an accepted outcome and the environment in which the product needs to work.

Discuss this workflow ↗
PRODUCT RELATIONSHIPS

Related, not interchangeable.

ONE PLATFORM

Choose a qualified workflow.

Select the capability you need directly or include its compatible role in a qualified platform workflow. Production scope identifies release, environment, capacity and support; a product count is not an entitlement.

Explore monthly plans See the system connections
START WITH THIS PRODUCT

Use the software directly or ask us to scope the implementation.

YOUR NEXT MOVELET’S MAKE IT COUNT

Put it
to work.

One capability. A connected workflow.
A team to put it into practice.

patrick@garmolabs.com

FIND YOUR CAPABILITY