Built for precision · Engineered for trust

The platform behind every QuantMint number is designed to be checked.

In options, a bad estimate becomes a funded loss. So every number we publish is cross-validated, calibrated against outcomes, and gated by guardrails that refuse suspect output. Here's how.

≤1%
Pricing-model agreement gate
5
Volatility regimes gating strategy admission
4
No-arbitrage checks per chain
1,000+
Regression tests on the math
Pillars of Robustness

Six disciplines that keep our output honest

Constraints, not features. Every recommendation passes all six.

Multi-model pricing cross-validation

Every American-style price is computed by two independent models — a closed-form analytical engine and a binomial-tree validator. Within 1%, we publish. Up to 5%, the conservative model wins. Beyond 5%, the candidate is dropped.

No-arbitrage chain validation

Every chain is checked against four classical invariants before any strategy logic runs. Violations become a data-quality warning on the trade card — never silently used.

Composite probability + Greeks transparency

Held positions: live chain delta — the market's own estimate. Scored candidates: a four-factor composite (path sim, early-exercise, dividend, event), surfaced with a transparent model spread. Per-leg delta, gamma, vega, theta on every card — in calendar-day convention, so theta matches your broker's Friday-to-Monday tape.

Volatility regime gating

Five live regimes, classified from spot vol, term structure, skew, and realized vol. Strategies that don't belong in the current regime are blocked — selling premium in a crisis takes an explicit override.

Continuous calibration

Every published probability is scored against the realized outcome. Rolling Brier and Expected Calibration Error, broken down by strategy and DTE. Drift is visible; persistent drift triggers a re-tune.

Daily P&L attribution

Day-over-day P&L is decomposed into delta, gamma, vega, theta, and a residual. A growing residual means the model has stopped explaining reality — and we treat it as a flag, not a footnote.

Recommendation Lifecycle

From raw quote to scored idea — five gates, each with a veto

Nothing is ranked before it has passed every stage.

01 Ingest normalize · timestamp 02 No-arb 4 invariant checks 03 Cross-check 2 pricers · ≤1% gate 04 Admit liquidity · regime · EV 05 Score rank · explain veto veto veto veto
Each stage can reject — nothing reaches the next without passing the previous.
STAGE 01

Ingest & clean

Quotes and chains normalized, time-stamped, structurally validated.

STAGE 02

No-arb & quality gates

Monotonicity, butterfly, calendar, put-call parity. Failures tagged, not used.

STAGE 03

Price & cross-check

Two independent models per leg. Disagreement measured; outliers dropped.

STAGE 04

Strategy admission

Liquidity, regime, and expected-value tests gate what's even rankable.

STAGE 05

Score & explain

Multi-factor score with risk-style overlay. Rationale and warnings attached.

Hard rule

Fail any gate, you don't appear — not even with caveats. A quiet screen beats a confident recommendation built on a stale or mis-priced quote.

Capital & Execution Discipline

Three disciplines applied before any strategy reaches your screen

Concentration, tax efficiency, and data freshness — built into the engine, not optional settings.

Concentration limits

Per-trade caps, a 30% sector ceiling, and per-strategy limits are enforced on every candidate. In stressed markets, a volatility-regime multiplier scales position size down automatically.

Tax-aware lot selection

Closing a position triggers lot ranking by short- vs long-term gain impact. FIFO, HIFO, and specific-ID methods are supported; the wash-sale window is respected.

Data freshness by design

Live feed during market hours, explicit TTLs per data type, automatic fallback when an upstream fails. Every number on screen has a known maximum age.

AI Philosophy

A deterministic core. AI for narrative, never for decisions.

Pull the AI layer out tomorrow and every number on the platform is unchanged.

What the deterministic engine does

  • Every price. Theoretical value, Greeks, IV, expected move — classical math with guardrails.
  • Every probability. Assignment, breakeven, expected value — code we wrote, regression-tested on every release.
  • Every gate. Liquidity, regime, no-arb, EV. Same inputs, same decision, every time.
  • Every score. Rule-based ranking, inspectable — not a black box.

Where AI is allowed

  • Plain-English explanations. Turning a setup into a paragraph a human can read.
  • Event narrative. Summarizing earnings, supply-chain, and qualitative context around a trade.
  • On-demand commentary. Explaining what the engine computed — not computing it.
  • What AI never does. Picks strategies. Scores trades. Touches Greeks, prices, probabilities, or risk numbers.
Data & Infrastructure

Per-customer isolation, encrypted in flight and at rest, audited end-to-end

Isolation, encryption, observability — the boring parts where most platforms quietly fail.

Tenant isolation by design

  • Every read scoped to your account. Cross-account leakage prevented at the query layer, not just the API layer.
  • Managed identity provider. JWT-based, short-lived tokens with rotating refresh, verified against cached JWKS on every request. We never store your password.
  • One database engine. A single managed PostgreSQL instance — chosen for ACID, rejected the moment anything weaker tries to creep in.
  • Encryption end-to-end. TLS in flight, encryption at rest, secrets in a managed vault. Never in code, tickets, or logs.

Operational rigor

  • Data ages out. Quotes, chains, and derived analytics carry tight TTLs — you never see numbers older than they should be.
  • Background jobs survive your tab. Persisted with progress; close the browser, come back, you see exactly where they are. We get paged when one fails silently.
  • Health, readiness, tracing on every call. Independent endpoints; structured logs; per-request IDs.
  • Versioned migrations. Every schema change is reviewed, scripted, and reversible. Production is never edited by hand.
Test Discipline

1,000+ regression tests — written to ask “what could go wrong?”

Not whether the code runs. Whether the financial math holds.

Math invariants

Probabilities outside [0, 1]. Annualized returns exploding at 1 DTE. Spread payoffs going imaginary at the extremes. Each has a test — usually written the day we caught it.

Strategy-by-strategy

Every supported strategy has dedicated tests asserting its financial properties hold under adversarial inputs.

Brokerage import

Each statement format has its own regression suite. A change to one parser cannot silently break another.

Pre-deploy gate

Tests run against a real database before any release. Math-touching releases require a clean run on production-shaped data.

Operating Principles

The standard we hold ourselves to

Enforced on every change — not aspirational.

No silent failure

If a model can't price, fit, or fetch — the trade card says so. Silent fallbacks erode trust.

Show the disagreement

When two models disagree, we show the spread. We don't pick a winner and pretend the other never ran.

Fewer trades, higher quality

Biased toward rejecting candidates. A blank screen is an acceptable outcome; a confident wrong recommendation is not.

Every order placed by you

Decision support, not auto-execution. Every order is yours to review and submit. We never move money on your behalf.

Things we will never do

  • ×Auto-fit a model to your portfolio. Calibration is against realized outcomes, not your holdings.
  • ×Use scraped chain data. Quotes come from authorized broker / exchange feeds, timestamps included.
  • ×Aggregate other users' trades into yours. No piggybacking on flow, sentiment, or social signal.
  • ×Publish a number we can't reproduce. Same inputs, same output — every score, probability, and Greek.

Built for precision. Engineered for trust.

Robustness is the result of disciplined choices, repeated on every release.

Request Beta Access → Back to home