Skip to content
Apex
Research

Notes from the laboratory.

Apex is a frontier AI lab. This is the research log — what we learn while training a foundation model for the physical world. Architectures, evaluations, case studies, biosecurity methodology, and the long unglamorous middle where most progress actually happens. Reproduce the work before you bet a roadmap on it.

The model we publish on

One backbone. Every modality.

The research agenda underneath every paper on this page is the same single model. CAD, mesh, RTL, molecules, spectra, plate data, code and sensor streams all flow into shared weights — and out through discipline heads.

EVERY MODALITY THE WORK PRODUCESONE SIMULATION-NATIVE FOUNDATION MODEL · SHARED WEIGHTSDISCIPLINE HEADS · OUTPUTS△CAD geometry◇Mesh▦RTL · netlist⌬Molecule∿Spectra◉Plate data</>Code≋Sensorembed · every modalityself-attn · multi-headcross-modal fusionphysics-aware mlpself-attn · multi-headdecoder · discipline routingAether · shared backbone△EngineeringCFD · FEA · controls⌬Discoverymolecules · ADMET▦SemiconductorsRTL → GDS◉Autonomous labsprotocols · analysis</>Softwarewhole-repo edits⌑MaterialsDFT · band structureOne model · shared weights · trained on simulation, instrument and design data — not scraped textv1.0 · sparse-MoE · every modality · every discipline
What we work on

Four threads, one model.

Architecture, evaluation, safety, platform. The research agenda underneath Aether — the questions we publish on, the questions we are working on, and the ones we have not yet figured out.

Architecture

How Aether is trained, what we put in the corpus, how the latent state spans physics, chemistry, biology and silicon. Cross-domain transfer and scaling-law work.

Evaluation

Benchmarks that mean something — measured against experiment, not against other models. Reproduction kits, error bars, failure cases.

Safety

Biosecurity refusals, capability gating, the architecture of the dual-use boundary. Red-team methodology and external review.

Platform

The agent runtime — long-horizon planning, deterministic memory, eval-gated deploys. What it takes to ship autonomous science in production.

The archive

Every paper, by topic.

Six topic threads, one running archive. Each paper carries a tag, a date, an abstract, the reproduction kit and the authors. The full set is below the feature card.

Model1Methods4Platform3Benchmark6Engineering3Safety2
Methods

Scaling laws for simulation-native pretraining

Read
Methods

Long-rollout stability in autoregressive physics

Read
Methods

Cross-domain transfer: from turbulence to transcriptomics

Read
Platform

Memory for long-horizon agents — episodic, semantic, versioned

Read
Benchmark

FEP benchmark — relative binding free energies across eight targets

Read
Benchmark

ADMET endpoint calibration — to your assays, not a public split

Read
Methods

Active learning in autonomous discovery — what to make next

Read
Engineering

How Aether retired a customer's seven-figure CAE renewal

Read
Benchmark

Beating commercial CFD on impinging-jet validation

Read
Benchmark

Transonic wing-body validation — external aerodynamics at cruise

Read
Benchmark

Aether for semiconductors — timing closure on open RTL-to-GDS benchmarks

Read
Safety

Biosecurity boundaries for autonomous wet-labs

Read
Safety

How we build, version, and red-team the refusal corpus

Read
Platform

A production runtime for long-horizon agents

Read
Engineering

Hypersonic CFD — real-gas validation against measured wind-tunnel data

Read
Benchmark

Antibody developability — flag classes and ROC-AUC against measured outcomes

Read
Engineering

Polymer rheology — viscosity prediction across processing temperatures

Read
Platform

Federated active learning across multi-site wet-labs

Read
How we publish

Reproducible by default.

Three principles we hold to on every research post. They are part of the charter — if a published number stops reproducing, we treat it as an incident.

  • If it doesn't reproduce, we don't publish

    Every benchmark on this site ships with a reproduction kit — the case, the mesh, the random seed, the model version. If it stops reproducing, we treat it as a P1 bug.

  • Failure modes alongside the wins

    We publish what doesn't work as carefully as we publish what does. Sweeping the negatives makes everyone's models worse.

  • Named accountability

    Every paper has named authors with named contributions. When numbers move, we say who moved them.

Reproduce before you trust.

If you spot a number that doesn't replicate, we want to know. Reproduction reports go to research@apexworldlabs.com — we acknowledge within a business day.