Applications can appear unrelated
Separate scientific products can hide their common computational foundation.
Discovery Core is explicitly identified as the engine behind AMDE and SpinForge Bio.
DiscoverySPINFORGE / A GARMO LABS COMPANY
SpinForge Discovery Core
The shared computational engine behind AMDE and SpinForge Bio.
Customer outcomeDesign and discover ↗
THE PRODUCT, IN PRACTICE
One discovery engine.
Two distinct applications.
Discovery Core is a named engine, not a hidden implementation detail or another alias for Recursive Engine. It powers AMDE and SpinForge Bio. Customers can understand the shared foundation while buying the application outcome appropriate to scoring or binder design.
- BUILT FOR
- Discovery-platform teams and buyers evaluating AMDE or SpinForge Bio.
CHALLENGES → PRODUCT RESPONSEThe problem you face.
The problem you face.
What the product changes.
YOUR CHALLENGEWITH SPINFORGE DISCOVERY CORE
The outcome matters more than the engine name
A buyer may need scoring or candidate design rather than a broad engine agreement.
Use the appropriate application while retaining the shared-core relationship in the scope.
Shared technology does not equal shared validation
A benchmark in one application cannot establish a result in another domain.
Evaluate AMDE scoring and Bio candidate design against their own requirements.
WHAT YOU GETA defined capability.
A defined capability.
A useful result.
Shared engine identity
The computational foundation explicitly named for AMDE and Bio.
AMDE relationship
AMDE uses Discovery Core for its discovery application.
Bio relationship
SpinForge Bio uses Discovery Core for binder design.
Defined licensing scope
Application and standalone engine rights are specified without charging twice for an included dependency.
OWNER-CONFIRMED DEPENDENCYA shared engine.
A shared engine.
Distinct discovery outcomes.
Bench has no asserted Discovery Core dependency. Recursive Engine is the synthesis meta-system, not another name for this engine.
EXAMPLE CUSTOMER WORKFLOW
Choose a discovery application
A buyer needs a scientific output and wants to understand its underlying technology.
Illustrative customer use—not a new benchmark or completed customer deployment.- 01→
Identify whether the task is candidate design, scoring or another admitted engine use.
- 02→
Select the application or explicitly scoped engine agreement.
- 03→
Evaluate the application result in its own domain.
FIT & ACCEPTANCEStart with the task.
Start with the task.
Agree the useful outcome.
- What you bring
- The discovery task, selected application, input expectations and deployment requirements.
- What a useful evaluation measures
- +Fit to the application task
- +Consistency of the shared-engine integration
- +Application-specific acceptance
- Delivery
- License the selected capability, commission an implementation, or agree an operated service. Infrastructure and additional engineering are specified separately.
QUESTIONS BEFORE BUYINGA clear scope.
A clear scope.
A clear relationship.
What is the important boundary?−
The supplied clarification establishes dependencies on AMDE and SpinForge Bio. It does not establish a Bench dependency or a separate ALCHEMI engine link. A shared computational engine does not establish experimental biological validation.
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.
PRODUCT RELATIONSHIPS
Related, not interchangeable.
AMDE + ALCHEMI
Physics-grounded drug-discovery scoring through GPU molecular dynamics.
SpinForge Bio
Protein binder design producing a ranked candidate panel for downstream synthesis and evaluation.
Recursive Engine
The synthesis meta-system through which its eleven products improve one another.
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 connectionsSTART WITH THIS PRODUCT
Use the software directly or ask us to scope the implementation.