DFTDealerFlow TerminalInstitutional Platform Request access Client login
Institutional overview

Methodology, governance, and controls — for diligence.

DealerFlow Terminal is the analytics and execution infrastructure behind emerging funds and managed-account desks. This overview covers how the intelligence is produced, how model risk is governed, how your data is isolated, and how the platform is deployed and operated.

Audience: PMs, risk & operations, diligence Segment: $25M–$250M AUM Posture: Technology & analytics — not an adviser
01

What the platform is — and is not.

DealerFlow Terminal is a financial-technology platform. It reads market structure, order and dealer flow, volatility, and positioning; resolves them into a calibrated, directional read per symbol; and executes the rules you configure, at the level of automation you choose. Your firm defines the strategy and owns every investment decision.

It is not a registered investment adviser, broker-dealer, or financial planner. It does not manage money, exercise discretion over your accounts, or issue recommendations. The analytics are descriptive decision-support; the execution engine acts only on rulebooks you author and arm.

The operating principle

You are the fiduciary. The platform is the infrastructure. Every read is an input to your process, and every order originates from your own versioned rules under your own risk controls.

02

Methodology — the Diamond.

Every symbol, on every horizon, resolves to a single object we call the Diamond: a calibrated win-probability with a confidence interval, an effective sample size, the prevailing market regime, and a conviction tier. It is designed to be sized against, not blindly followed — thin evidence is labelled INSUFFICIENT DATA rather than presented as a false precision.

Six analytical families

Each family contributes an independent long and short sub-score. They combine under adaptive weights into the composite that anchors the Diamond.

Dealer positioning — the gamma map many desks buy as standalone research — is a single lens here, informing families B and F. It is an input to the Diamond; it is not the Diamond.

Conviction tiers

Reads are graded so position sizing keys off calibrated edge, and low-conviction reads are excluded rather than merely discouraged.

T1Highest calibrated edge — full sizing eligibility.
T2Moderate edge — reduced sizing.
T3Marginal edge — watch / scale-in only.
No-trade / InsufficientBelow floor or too little evidence to score honestly.
03

Continuous calibration & model governance.

Indicators drift and regimes rotate, so the composite does not trust a fixed formula. It measures its own realized hit-rate and re-weights each family on a nightly cycle — bounded, shrunk toward priors, and fully recorded, the way a model-risk function would require.

Measure & update

Nightly recalibration

Resolved outcomes feed a calibration pass; family weights move toward what is working, within tight, governed bounds so nothing lurches.

Priors & guardrails

Statistical discipline

Thin-evidence estimates are pulled toward conservative priors, and guardrails keep any single family from dominating or vanishing.

Evidence

Walk-forward & backtest

Reads are validated out-of-sample. A reliability curve tracks predicted vs. realized probability across thousands of resolved reads.

Traceability

Model cards & prediction log

Every weight set, calibration curve, and anomaly override is versioned. Each prediction and its outcome is logged for audit.

Where a fund's model-risk policy references frameworks such as SR 11-7, this design maps cleanly: documented methodology, independent validation evidence, bounded change control, and an auditable record of every model update.

04

Multi-timeframe & regime conditioning.

The same math runs across eight horizons, from minutes to a month. The Diamond Ribbon aligns them into one view; where horizons disagree, the disagreement is surfaced explicitly — a trader-horizon long against a keeper-horizon short is shown, never silently averaged into a misleading middle.

Every read is conditioned on the prevailing dealer-positioning and volatility regime. The same setup carries different odds in positive-gamma tape than in negative-gamma tape, and the calibration reflects that.

05

Execution & risk controls.

Execution runs at three levels, chosen per strategy and per account: manual (decision support), semi-automated (staged or shadow), and fully automated (armed). Nothing is armed that you did not configure.

Three systematic engines

The same rulebook and risk desk feed three engines, so a strategy can be expressed directionally, structurally, or as an overlay — without stitching together separate vendors.

The engines are execution surfaces for the rules you configure. They do not originate discretion — direction, structure, and eligibility are governed by your Trade Profiles and the read.

06

Security & tenant isolation.

Each fund runs in its own dedicated instance — dedicated compute and an isolated, encrypted database. Within that instance, private account data is enforced at the row level and scoped to the owning tenant; nothing crosses between clients.

IsolationDedicated instance per fund; row-level tenant enforcement (RLS), asserted at runtime.
IdentitySSO (Okta / Azure AD); named users with role-based access.
RolesPortfolio Manager, Trader (assigned books), Risk Officer (limits & kill), Compliance (read & export), Analyst (read-only).
AuditImmutable, timestamped, exportable record of every order, override, arming action, and config change.
DataMarket data licensed for professional use; broker and market-data credentials held by you.
EncryptionEncryption in transit and at rest; secrets isolated per instance.
07

Deployment, connectivity & posture.

We operate and update the platform centrally; you control where it runs and who reaches it. Deploy inside your own AWS VPC or in our managed environment.

DeploymentDedicated managed instance — your VPC or ours. Live
Broker connectivitySchwab today. Live   FIX & multi-custodian routing. Roadmap
Pre-trade complianceRestricted lists, mandate & concentration limits. Roadmap
ReconciliationStart-of-day positions vs. custodian; multi-account roll-ups. Roadmap
SOC 2 Type IIControls program underway. In progress
ReportingP&L attribution per book / family / profile version; tax-lot & wash-sale. Live

Roadmap items are scoped with design partners. We will map your custody, mandate, and reporting requirements during onboarding and are transparent about what is available today versus in build.

08

What a Diamond contains.

Each read is a structured object, not a colour or an arrow. These are the fields your team can inspect, log, and reconcile — the same payload that drives the Ribbon, the auto-trader, and the prediction log.

p_winCalibrated probability that the setup resolves in the read’s direction.
CI (95%)Confidence interval around p_win — how tightly the estimate is bounded.
n_effectiveEffective sample size of comparable historical setups behind the estimate.
direction & biasLong / short call plus a continuous net bias in [−1, +1].
tierT1 / T2 / T3 / No-trade / Insufficient — the sizing gate.
regimePrevailing dealer-positioning / volatility regime the read is conditioned on.
horizonThe timeframe the read applies to (5m through 1M).
alignmentHow many horizons agree with this direction (the Ribbon’s ALIGN).
attributionPer-family contribution to the composite, so the read is explainable.
09

Onboarding & operations.

A design-partner onboarding is scoped, hands-on, and reversible at every step — you reach live only when your team is satisfied with what it has seen in shadow.

We operate, monitor, and update the platform centrally. New families, calibration improvements, and fixes reach your instance without your team running a release process. Support and incident response are handled directly by the team building the platform.

10

Diligence questions.

Do you take discretion or place trades on our behalf?

No. The platform executes only the rules your firm authors and arms, under your risk controls. It never exercises discretion, and it can run purely as decision-support with execution disabled.

Can another client ever see our data?

No. Each fund runs in a dedicated instance with an isolated database and row-level tenant enforcement. There is no shared data plane across clients.

What happens if the models misbehave?

Bounded change control caps nightly weight moves; an anomaly override can freeze updates; and the risk desk plus kill switch sit above execution independently of the analytics. Reads with thin evidence are suppressed rather than shown.

How do we validate performance ourselves?

The prediction log records every read and its realized outcome, and the reliability curve and walk-forward evidence are available for your own inspection inside your instance.

What is genuinely available today versus roadmap?

Analytics, calibration, Schwab execution, tenant isolation, audit, and attribution are live. Institutional FIX / multi-custodian routing, pre-trade compliance, custodian reconciliation, and SOC 2 Type II are in build and scoped with design partners — we do not overstate readiness.

11

Glossary.

DiamondThe single calibrated, directional read for a symbol on a horizon.
CompositeThe 0–100 long / short score from the six families that anchors the Diamond.
Diamond RibbonThe multi-timeframe grid aligning every horizon across your symbols.
GEX / gamma mapDealer gamma exposure by strike — walls, flip, and magnet; one positioning lens.
Trade ProfileA per-ticker, versioned rulebook that governs how orders are produced.
Observe / Shadow / LiveThe three automation levels — analytics only, paper audit, and armed.
Risk deskFirm-level caps, limits, windows, and kill switch above all execution.
12

Availability, backups & continuity.

Because each fund runs in its own instance, availability and recovery are managed per client rather than shared across a multi-tenant fleet. We are explicit about what is contractual today versus maturing under the SOC 2 program.

MonitoringHealth, connectivity, and execution telemetry watched centrally, with alerting to the operating team.
BackupsEncrypted, point-in-time database backups; retention configured per client.
ContinuityDocumented restore procedure per instance; disaster-recovery targets formalised with each engagement.
Change managementPlatform updates are staged and validated before reaching your instance; model changes are bounded and versioned.
Incident responseDirect line to the team building the platform; the kill switch lets your desk halt execution independently at any time.
Formal certificationsSOC 2 Type II controls program underway. In progress

Service levels, retention windows, and recovery objectives are agreed per engagement. We would rather commit to what we can operate reliably at your scale than publish a number we cannot stand behind during diligence.

Important disclosures. DealerFlow Terminal is a financial-technology and analytics platform. It is not a registered investment adviser, broker-dealer, or financial planner, and it does not provide investment, legal, or tax advice or recommendations, nor does it exercise discretion over any account. All figures, scores, probabilities, and screens described or shown are illustrative and for informational purposes only; they do not depict any client account or actual performance, and past or hypothetical performance is not indicative of future results. Calibrated probabilities are statistical estimates, not guarantees. Trading options and securities involves substantial risk of loss, including loss of principal. Clients are solely responsible for their own investment decisions and for compliance with all applicable laws and regulations. Nothing herein is an offer or solicitation to buy or sell any security. See the Terms of Service for the governing terms.