Roadmap

What we’ve shipped, and what’s next.

An honest view of where Batchrite is today and where it could go. What’s shipped is real and running with the pilot cohort. What’s in progress lands this quarter. Everything past that is a post-pilot candidate — the roadmap only extends as far as the pilot does. We’d rather tell you that up front than dress it up.

v0.4 · last updated may 2026
Shipped In progress Candidate Out of scope
Shipped · in production now

Running with the pilot cohort today.

The core batch-record loop — design, run, review, lock — plus the audit and access controls a PD group needs to defend its numbers. All live with pilot members.

Shipped

Graph-based process designer

Draft any process as a graph, not a step-list. Branch, parallelize, and version without rewriting the record.

Shipped

AI-assisted authoring

Describe a process in plain language and the assistant drafts it as a graph — for your review, over your own data only.

Shipped

Auto-generated batch records

Protocols and batch records generated from your modality-aware templates — no rebuilding the document by hand.

Shipped

AI vision for bench capture

Extract numeric readings from gauges and displays, and flag anomalies across run images automatically.

Shipped

Review & lock flow

A lightweight scientist → process lead → head of PD review, with hand-drawn e-signatures bound to every event.

Shipped

Immutable audit trail

Every change logged with actor, timestamp, and before/after. Append-only and tamper-evident, so memory survives turnover.

Shipped

Reason-for-change capture

Post-lock edits require a typed justification and a fresh signature. Locked records can’t be silently mutated.

Shipped

Lot-traceable run history

Every lot, reagent, instrument, and operator threaded into a queryable history you can answer CMC’s questions from.

Shipped

Role-based access controls

Organizations, teams, and fine-grained roles and permissions, scoped per project.

Shipped

Full data export · no lock-in

One-click archive of an entire project in open formats (Excel, CSV, PDF), or connect Batchrite to your own systems.

Q3 2026 · in progress

Being built with design partners.

In active development and rolling out to design partners this quarter. These are the requests that came up most across pilot conversations.

In progressFUT-0005

Process intelligence & DoE analysis

Ask the assistant to analyze a set of runs and surface the factors driving your critical quality attributes — the 80% case for JMP / Design-Expert.

In progress

SSO & SAML / SCIM

SAML single sign-on and SCIM provisioning with Okta, Entra, and Google Workspace.

In progress

Bring-your-own encryption keys

Data is encrypted at rest today; the option to bring your own AWS or GCP keys is rolling out to design partners.

Post-pilot · candidates

Candidates for after the pilot.

Not dated, not committed. These are the directions we’re most convinced by — the future tasks we’d take on once the pilot proves out and enough PD groups are on board. Pilot members rank them; the rest stays honest.

CandidateFUT-0011

CDMO export & tech-transfer packs

Turn a locked process into a tech-transfer package mapped to your CDMO’s format — or your own SOP / batch-record template.

CandidateFUT-0016

MCP server for local agents

Connect Batchrite to the AI agents you already run — query runs, draft processes, and log results without opening the UI.

Candidate

SOC 2 Type II

Sequenced after GA so the controls we attest to are the ones actually in production — if the company gets that far.

Candidate

Native instrument integrations

Adapters for the two or three instruments our pilot members actually live on — built once we know which those are.

Candidate

Expansion beyond process development

Adjacent science-driven industries — specialty chemicals, vitamins, medical devices — but only if the core proves out here first.

Out of scope · by design

What we’re deliberately not building.

Batchrite is built for pre-GMP process development. These are out of bounds on purpose — and we’ll tell your QA group as much in writing.

Out of scope

21 CFR Part 11 / GxP claims

We don’t claim Part 11 compliance, GLP validation, or commercial-GMP fitness. The PD floor is enough traceability to defend a process, without the GxP overhead.

Out of scope

Validated commercial MES

When your process leaves PD, we hand off cleanly to a validated MES (Tulip, MasterControl, Veeva) with a full export of the development history.

How we decide

Three rules for what gets built.

We’re small on purpose, and the roadmap stays short on purpose. Every item earns its place against the same three questions.

01

The customer in front of us

Every decision starts with one question we can name: which PD group is this for, and what does it unblock for them this quarter? If we can’t answer that, we don’t build it.

02

Founding partners vote

Pilot members rank what jumps the queue. The order above is theirs, not ours — and it shifts as we learn what actually slows a process development group down.

03

Honest about scope

Saying no is part of the roadmap. We name what’s out of bounds so you can plan the handoff to a validated MES when your process leaves PD.

Pilot · the roadmap extends as far as you do

Make the rest of this roadmap real.

Everything past Q3 depends on enough process development groups joining the pilot. If Batchrite would help yours, a 30-minute call is how it gets built — and how your requests go to the top of the list.