The knowledge network
MicroMap by default, other knowledge graphs alongside it, and your own Company Graph. Every association links to its sources.
Learn more →Graphomics builds the verified data layer for biological AI. Operon gives your team a private research platform grounded in curated knowledge graphs. MapForge builds those graphs, including your own. Every result carries a record of the data, method and version that produced it.
An agent writing software has somewhere to stand: it can run the code, read the trace, watch the test fail, and correct itself. Biology gives an agent none of that. There is no executable, inspectable record to check against, so it guesses.
Ask a question grounded in curated biology, run the analysis that answers it, then write the result back with its provenance, so the next question starts from it.
MicroMap by default, other knowledge graphs alongside it, and your own Company Graph. Every association links to its sources.
Learn more →A research agent that cites what it used, analysis steps and validated Nextflow pipelines, approved before costly runs.
Learn more →Validated results are written into your own private graph with their provenance and a trust label, so the next question builds on them.
Learn more →↻ MapForge builds and extends every graph in the loop. Nothing is written until a reviewer approves it.
Built on open standards. Your own agents (Claude Code, Cursor, or something you built) query the knowledge graphs over MCP or a REST API, alongside Operon's own agent.
Every organization gets its own knowledge graph inside its Operon deployment: your data, assays, experiments and validated findings, linked to the curated biology in MicroMap. It is private to you, and it grows with every result.
MicroMap is connected by default. Reference and domain graphs are designed to federate alongside.
Operon is where your team works. MapForge builds the graphs it works on.
Your team's private research workspace, deployed for your organization alone.
Builds knowledge graphs, including your Company Graph, from your data and public sources.
Every Operon deployment is connected to it. Every association is linked to its sources, with a declared confidence calibration.
Counts as of October 2026.
Pick the relationship that fits how your team works today. Each one runs on the same graphs and the same record.
Your own Operon deployment: your Company Graph, a grounded research agent and validated pipelines, for your whole team.
About Operon →MapForge builds and maintains a knowledge graph from your data and the public sources for your field. Or license the engine and run it yourself.
About MapForge →Your engineers query MicroMap from their own tools, Claude Code, Cursor or their own agents, over MCP or a REST API.
About the graphs →The questions that matter to your team, and the data you already hold.
Hosted by us or in your own cloud, connected to your data.
Your Company Graph, built with MapForge from your data and the public sources for your domain.
Answers, analyses and pipelines, with the evidence and lineage behind every result.
Your data, your Company Graph and your results stay yours. They live in your deployment and are never pooled with other clients.
Reasoning got good, and cheap. Frontier models can plan an experiment and read an analysis.
MCP made pipelines and data sources something any agent can call.
A hallucinated pathway can cost a lab months at the bench.
Frontier models can plan an analysis. They can't tell you which microbe–disease link has several studies behind it and which has none. MicroMap can.
You can, and for a first look it helps. What it lacks is somewhere to check its answers. Public sources disagree, use different names for the same microbe, and rarely say how strong a link is. An agent reading them cold has to guess which to believe.
MicroMap has done that work already: 63,136 microbe–disease associations, with names reconciled to standard identifiers and each association linked to the studies behind it. Your Company Graph adds what only your team knows. Operon keeps the record of what was asked, what was used and what was decided.
Bring a question from your own work. We'll walk you through how Operon would answer it.