Catalyst-Q is the virtual quantum computer and SDK. Start with the Catalyst-Q platform, then choose the first application worth testing. Every run should leave a Quantum Execution Record instead of an unexplained result.
Catalyst-Q Quantum Studio + SDK
Build circuits. Run jobs. Keep the proof.
Catalyst-Q is the virtual quantum computer and SDK. Catalyst-Q turns expensive, hard-to-check answers into proof your team can review. Catalyst-Q is the execution and proof layer behind the Studio and SDK. Use the visual Studio for first runs or the Catalyst-Q SDK for code-first workloads. The reviewable proof is the output of a Catalyst-Q run, not the product category. Build a circuit, choose a Catalyst-Q backend, run the job, and get a signed Quantum Execution Record with the .rain footprint, confidence signals, replay id, and rationale attached.
Use the visual Studio for a first run, then move the same workflow into Catalyst-Q SDK calls when a developer wants automation.
Catalyst-Q pairs virtual quantum workloads, .rain replay, rationale, and signed evidence so users can inspect why a result deserves trust.
RouteOps for freight and logistics is the first application proof room. Start where ROI is visible: routes, capacity, lateness, fuel, emissions proxy, and dispatcher approval. Run Catalyst-Q first; choose an MVP room when a workload deserves a pilot. We are also looking for design partners, feedback, and paid pilots across chemistry, agent review, FinOps, and edge operations. MVP applications remain available as focused rooms, not separate products.
3PLs, carriers, brokers, retail & CPG, private fleet, R&D, AI governance, and operations teams. 14.4% CAGR from 2024 to 2030. Large enterprises led market revenue share in 2023. Typical pilot results target 8-15% total cost reduction. Source: Grand View Research, June 2024.
Preview workflow: This page uses public example data. Catalyst-Q first proves the platform loop: run a workload, compare the result, explain why it changed, and keep the signed record. A paid pilot replaces assumptions with your route file, baseline costs, constraints, and approval owners before any production change. Run a sample proof, see the dollars at stake, and hand your team an audit trail they can defend. Verify the decision before you act. One route file. One proof packet. One approval decision.
SDK-firstUse Studio for discovery, then run the same Catalyst-Q workflow through API and SDK calls.
Proof by defaultSigned Quantum Execution Record, Route Decision Record, replay id, and audit trail instead of a black box.
MVP roomsMVP rooms / applications give design partners a concrete place to test value before a larger rollout.
How to use Catalyst-Q
When the answer is expensive, do not let it disappear into a black box.
The first useful action is simple: run one circuit, route file, cloud bill, agent claim, or sensor event and get a record your team can inspect.
01
Build or bring one workload.
Start with a Bell state, OpenQASM snippet, Python SDK call, route CSV, cloud spend question, or agent action your team already understands.
02
Run it in Studio or SDK.
Catalyst-Q runs the candidate path, compares it against the baseline when one exists, and attaches the .rain replay footprint.
03
Share the proof.
Send a Quantum Execution Record, Route Decision Record, or pilot packet to the person who has to approve the next step.
Fewer black-box arguments.
The conversation moves from "do we believe it?" to "does the record prove enough to try it?"
A first run in minutes, not a migration.
Open Studio, run a sample, or use the Catalyst-Q SDK before you connect a production system.
Proof that travels with the decision.
The evidence, rationale, replay id, and approval state stay together when the work moves from builder to buyer.
First Proof Room Chooser / MVP Rooms / Applications
Choose the first decision to prove.
Start with the workflow your team already owns. These are not separate products. They are application rooms built on Catalyst-Q. Choose the first decision to prove, then help shape the MVP application with feedback, design-partner review, or a focused paid pilot.
Freight and field routing
Our clearest first MVP application. Upload yesterday's stops, vehicles, time windows, and dispatcher baseline. Catalyst-Q returns an approval-ready Route Decision Record with savings, constraints, replay, and approval state.
Preview route fileField Service & Last-Mile
MVP room for teams with jobs, technicians, visit windows, priorities, missed appointments, and route churn. Use the same proof workflow for daily field schedules and last-mile exceptions.
Open workbenchAI Cost / FinOps
MVP room for cloud bills, model spend, GPU queues, cache choices, and workload moves. Compare cost/performance options before rollout and tell us what evidence a finance owner needs.
Open proof pathAgent Governance
MVP room for teams deploying AI Workers or agent systems. Turn an action, remediation proposal, or executive claim into evidence, confidence, rollback, and human approval before production.
Review agent claimIoT & Edge Operations
MVP room for sensor events, asset states, depot alerts, maintenance risk, and field dispatch decisions. Make the action reviewable with replay and approval.
Map sensor eventExact Chemistry verification
MVP room for technical teams with chemistry and materials questions where approximation, cost, or timing needs review before lab or diligence spend.
Open chemistry proof
One workflow, one proof record
Upload one CSV, bill, incident, or sensor event
Replay the current baseline
Run Catalyst-Q candidate proof
Explain tradeoffs and constraints
Approve with a signed Decision Record
Catalyst-Q product story
Know what Catalyst-Q does in 30 seconds.
Catalyst-Q is a quantum execution and proof platform: Studio for visual experiments, SDK/API for developers, and signed records for teams that need evidence before they trust a result.
What Catalyst-Q gives you.
A Quantum Studio and Catalyst-Q SDK for running virtual quantum workloads, comparing candidate answers, and packaging the result as a signed proof artifact. In the RouteOps MVP application, that artifact becomes a Route Decision Record.
- Open Studio for a first run or call the Catalyst-Q SDK from your own workflow.
- Leave with a Quantum Execution Record, signed Route Decision Record, or application-specific proof packet your buyer can inspect.
How it fits your stack.
Start in the browser, then wire the same run through API and SDK calls beside your TMS, agent system, cloud ledger, research workflow, or enterprise data stack. Your team keeps control while Catalyst-Q prepares the evidence for approval.
- Start beside existing systems before a larger rollout or integration project.
- Keep decisions in review until the approval record is accepted by the owner.
Why it compounds.
Each accepted or rejected Quantum Execution Record or Decision Record adds reusable context: baseline behavior, constraints, owner preferences, replay ids, and outcome history.
- Catalyst-Q SDK verifies candidate choices at scale.
- Catalyst Brain and AI Workers preserve the review trail across teams.
Buyer path
Check pilot fit
>
Open Studio or SDK
>
Generate sample Route Decision Record
Built for high-stakes decisions.
Start with Freight RouteOps when route decisions touch cost, service, compliance, and approval. The same proof workflow can extend to field service, cloud cost, agent review, and scientific verification once the first pilot is measurable. Treat every vertical here as an MVP application built on Catalyst-Q: one narrow proof room, one measurable outcome, and one design-partner loop before broader rollout.
Operations leaders
Compare the current plan against a safer candidate before freight, field, grid, or flight operations change.
See freight exampleFinance leaders
Turn a recommendation into cost exposure, conservative savings, payback period, and confidence discount.
Build ROI packetDispatch and route planners
See why a route changed, which constraints stayed hard, and what a dispatcher can approve or reject.
Open intakeR&D leaders
Screen materials, chemistry, and drug-candidate claims before spending lab time or partner diligence budget.
Open chemistry pathSecurity leaders
Ask whether an AI remediation or risk claim actually reduced measurable exposure before expanding access.
Review claim pathTechnical reviewers
Open the evidence room when you want benchmark detail, APIs, replay ids, and solver-specific records.
Inspect evidenceFrom claim to proof in four steps.
A simple path from familiar input to approval-ready evidence. Start with a circuit, route file, cloud bill, sensor event, or agent claim; the details stay available for reviewers without getting in the way of the first decision.
Connect data
Bring a circuit, sample CSV, cloud bill, sensor event, deck claim, dashboard metric, or agent recommendation. The page starts with a familiar input.
Run shadow comparison
Compare options while Catalyst-Q measures the current choice against a candidate path and the human team keeps control.
Explain the recommendation
Show the constraints, drivers, confidence, .rain replay footprint, and tradeoffs that made the candidate worth reviewing.
Approve with audit trail
Catalyst Brain preserves scoped context, approval state, and replay continuity so the proof can be reconstructed later.
Your first 7 days of proof.
In a week, your team can preview intake, baseline replay, candidate comparison, ROI packet, and approval path on one selected workflow. Start in Studio or SDK, then move the strongest proof into an MVP application pilot.
Upload & connect
Upload a route file, circuit, bill, claim, or event. We auto-detect structure, cleanse, and map data for Baseline replay.
Baseline & constraints
Set business rules, circuit parameters, or service constraints. We validate feasibility before running Shadow proof.
Catalyst-Q optimization
Run Catalyst-Q through Studio or SDK. Compare current plan vs Catalyst-Q plan against the metrics that decide value.
Review & explain
Explain impacts with confidence insights and translate results into the ROI packet or technical review packet.
Proof packet generated
Generate a signed, auditable proof packet with full lineage, assumptions, replay id, and .rain footprint.
Approve & act
Give the decision owner assumptions, rollback, replay id, and an Approval path for the measured pilot window.
Interactive proof demo.
Adjust a sample scenario and watch the Decision Record update.
Scenario controls
Data readiness
Route fileValidated
Dispatcher baselineLoaded
ConstraintsReady
Approval ownerAssigned
Live result
$18.4KSavings case
92%Confidence
7/7Constraints passed
Route Decision Record preview
Ready for reviewRecord IDrdr-demo-freight-42-180-92
Objective delta$18.4K savings case
Risk deltaCapacity and lateness inside review bounds
Replay IDrouteops-demo-replay-821
Signaturesig-demo-6f68
Human approvalVP Operations review
Decision rationale
- Savings rise when late-delivery cost is high and capacity stays inside the safe band.
- Decision owner sees what changed before approving the pilot.
- Technical reviewers can open the Evidence Room for benchmark and replay detail.
Approval brief
Explore the Evidence Room.
Every decision is traceable. Every claim is provable. Review benchmark status, APIs, replay ids, and signed artifacts when your technical team is ready.
Benchmark evidenceSigned benchmark packet, deterministic replay, and artifact status.Open
Challenge RoomTechnical review path for packet replay, signatures, and targeted verification artifacts.Open
RouteOps Proof RoomDecision record, solver comparison, connector readiness, and structured discovery files.Open
Pilot Conversion RoomScore pilot fit, price the first 4-6 weeks, and identify the next account action.Open
Freight proofView proof packet: route comparison, ROI, constraints, and paid-pilot evidence.Open
Exact chemistryScoped verification path for materials and scientific candidates.Open
APIStructured routes for teams wiring proof into their own stack.Open
Customer context
Decision owner
Replay trail
Approval state
Catalyst Brain context
Proof paths by market
Catalyst Brain context keeps the proof alive.
Catalyst Brain is the memory, context, orchestration, and runtime-ops layer. Catalyst-Q is the verification and optimization engine. Together they make each MVP application explainable now and reconstructable later.
Freight RouteOps
Design-partner MVP for visible ROI: routes, capacity, lateness, fuel, emissions proxy, and dispatcher approval.
Open route proofExact Chemistry
Design-partner MVP for R&D teams that need scoped verification before expensive wet-lab or partner diligence spend.
Open chemistry proofAI Validation Layer
For platform and security teams, convert agent claims into evidence, controls, and review paths. Use it when an agent recommendation needs proof before access, remediation, or spend expands.
Open validation pathStart with one proof.
Start with one Catalyst-Q proof. Open Studio, run a sample circuit, then choose an MVP application if you want to test Catalyst-Q on a real workflow. Bring one expensive decision: a freight run, circuit, chemistry question, agent claim, cloud-cost move, or sensor event. Start paid pilot after the sample proof shows the current path, the better candidate, why it changed, and what evidence your team can inspect before action.