INTRODUCING // REFLEX Fine-tuning-as-runtime for production LLM agents — from rented prompts to owned weights. Read the thesis →
PLATFORM // REFLEX

Fine-tuning as a runtime, not a research project.

Reflex separates execution into two strict operational loops joined by a single choke point — the Adapter & Model Registry. Online serving never triggers training; offline training never serves live traffic without a promotion pass.

Two loops. One choke point.
Zero ungated promotions.

Scroll to traverse the full pipeline — from instrumentation to serving.

OFFLINE 01

Instrumentation SDK

Emits structured trajectory events — messages, tool calls, outcomes, tokens — from your existing agent harness.

≤5 lines integration • zero behavioral impact
OFFLINE 02

Trajectory Store & PII Redaction

Versioned, customer-owned storage. Configured PII categories masked before any dataset eligibility.

≥1M traces/month • build blocked if redaction fails
OFFLINE 03

Dataset Builder

Success filtering, near-duplicate clustering, and stratified sampling across rare task slices.

Auditable manifest per build
OFFLINE 04

QLoRA & SLM Training

One-command training producing versioned QLoRA adapters or standalone vertical SLMs.

Single 48 GB GPU • full lineage recorded
OFFLINE 05

Golden Set Harness

Candidates evaluated on frozen production-derived traces with deterministic checks and pass-k reliability.

Emits PASS / REVIEW / FAIL
BOTH LOOPS 06

Adapter & Model Registry

Version lineage and lifecycle state. The sole path to production — activation refused without a passing comparative report.

THE CHOKE POINT
ONLINE 07

Multi-LoRA Runtime

OpenAI-compatible endpoint serving a shared base plus adapters or standalone SLMs with continuous batching.

≤5% p95 latency overhead
ONLINE 08

Router & Rollback

Confidence-threshold routing strips baked stable prompt segments and monitors live metrics.

Automatic reversion in <60 seconds

No unproven weights in production.

A hard six-step promotion protocol against a frozen production Golden Set. Only a PASS verdict permits activation.

  1. 1

    Lineage Registration

    Candidate adapter or SLM registered with exact dataset hash, base model ID, and hyperparameters.

  2. 2

    Deterministic Harness Execution

    The candidate runs against the frozen golden set. Infrastructure failure defaults to “inconclusive” with zero state change.

  3. 3

    Dual-Comparator Scoring

    Per-slice report compares the candidate against both the prompted baseline and the currently active model version.

  4. 4

    Hard Gate Enforcement

    Only a PASS verdict permits activation. REVIEW or FAIL verdicts are blocked absent an explicit, audited human override.

  5. 5

    Hot-Loading & Threshold Arming

    Passing artifacts hot-load into the serving runtime while arming the rollback monitor with the report’s regression thresholds.

  6. 6

    Sub-Minute Automatic Reversion

    If live metrics breach thresholds, traffic reverts to the prior version in under 60 seconds — or to the terminal frontier-model fallback.

Adoption is an arithmetic decision.

The Prompt Slimming Engine removes stable segments at runtime. Compute your break-even volume directly from your existing API invoices — before a single training job.

≥0% – 70% Input-token reduction on covered tool-heavy traffic
≤0% p95 latency overhead on routed multi-adapter serving
<0s Automatic rollback when live metrics breach thresholds
0 GB Single-accelerator train-evaluate cycle. No GPU farm.

Adapters are disposable artifacts regenerated via one-command retrain loops. Your durable, compounding asset is your proprietary trajectory corpus — and it stays yours.

We host it. Or you do.

The customer-owned data plane is a hard design goal: trajectories, datasets, and weights never leave customer infrastructure.

VPC •

Your VPC

Training and serving deploy into your cloud project. Trajectory stores, PII-redacted datasets, and model registries stay in your storage buckets.

AIR •

Air-Gapped

Fully disconnected operation for regulated environments. No external API calls, no telemetry, no egress — ever.

GPU •

Dedicated GPU

Reserve single 48 GB-class accelerators for predictable throughput without managing hardware or sharing capacity.

STACK // Open-weights Gemma-class foundations fine-tuned as standalone vertical SLMs or served as frozen bases in the multi-LoRA runtime • frontier API operates as the initial prompted baseline and terminal fallback • single 48 GB-class GPU instances handle both the training pipeline and continuous-batching serving, in-region.

Run the arithmetic on your own invoices.

A brief shadow deployment of the SDK answers break-even before any training job.