Halffield — Interoperability & connectivity

A discovery platform can’t be an island. Halffield speaks out to the public scientific web, your instruments, and your data cloud; in as a tool your other systems and agents can call; and across your automation stack via webhooks and an event bus. Instruments land data through a vendor-adapter framework — a new vendor is one adapter. And heavy compute runs on your own cloud, so your IP never leaves.

The connector hub

What Halffield connects to.

Lab instruments

Data lands as a run and flows through the extractor pipeline to results. Any instrument that exports CSV/JSON over HTTP works today; deeper vendor integrations are one adapter each.

Plate readersHPLCLC-MSMass specqPCRFlow cytometersLiquid handlersSpectrophotometersSequencersMicroscopesCentrifugesIncubators

Lab & enterprise software

Connect live or migrate from — via embedded UI, API mirror, or federated modes.

ELNLIMSCDSCompound registriesInstrument DBsMES/ERPProtocol repositoriesSpreadsheetsPM tools

Automation & orchestration

Trigger runs and receive callbacks through a per-tenant signed-webhook registry, with an outbound event bus.

n8nZapierMakeApache AirflowArgoTemporalSigned webhooksKafka event bus

Cloud & compute (all-GCP, in-VPC)

Your IP stays in your cloud.

Google Cloud StorageVertex AIDocument AICloud Run GPUDatabricksSageMakerHPC federation

Public scientific data

Unified behind one interface for dossiers, structures, literature, and vocabularies.

UniProtChEMBLOpen TargetsClinicalTrials.govPubMedKEGGReactomePDBSTRINGPubChem

Agent interoperability (MCP)

Both directions.

Halffield-as-a-tool (MCP server)Scoped per-tenant API keysBring-your-own declarative toolsAdmin-approved staging

Safe by construction

Every operator-supplied outbound URL is fetched through an SSRF-hardened egress guard — blocks internal/metadata addresses, re-verifies every redirect.

Heavy compute runs all-GCP, in-VPC — private structures and IP never leave your cloud or touch a public CDN.

A note on maturity. Live today: the instrument connector framework (CSV/HTTP + adapters), the 10 public bio databases, the MCP tool server, GCS, Vertex AI, Document AI, Cloud Run GPU, and the federation callback. Framework built (best read as “built for / works with”): the inbound automation webhooks and the Kafka publisher. We present integration logos as “works with,” not “certified.”

← PreviousBuild any experiment. The design drives the rest. Next →Bring your lab’s history with you.

Explore the platform

Meet the agents

A workforce, not a chatbot.

Data model & knowledge graph

A platform that knows its own science.

Modularity

Build any experiment. The design drives the rest.

The migration engine

Bring your lab’s history with you.

Target discovery

Find the right target — on evidence, not instinct.