Everything, asked plainly.

Desk-wide options risk and trading on one screen. Your clearing firms' positions, your brokers' executions and the whole desk's risk — live, in one place, and run for you.

A desk runs the same loop all day: work an order, see the position, see the risk, trade again. Most desks run that loop across three or four systems with a spreadsheet holding them together, and every handoff between systems costs time and adds error. Lavender is the whole loop on one screen. More about Lavender Desk →

From your clearing firms. Each firm's start-of-day positions build the book, and a real-time drop copy of every fill keeps it current through the session.

A fill confirmed by the clearing firm shows once, marked cleared, and a panel shows each link and each firm's latest file — so you can see the state of the connection rather than assume it. Positions from several clearing firms sit in one book.

Yes. Orders go from the risk screen to your own executing brokers, through their algorithms, as single or multi-leg complex orders. The book's risk and margin before and after the trade are on the ticket, and every order is checked against the broker's specification before it leaves.

No. A trader confirms every order, hedges included. Nothing is sent or resent on its own.

Hedging algorithms from our execution partners are available — a vol hedge, for one, keeps an option's delta hedged within a band — and the trader confirms the order and its band. Size and notional limits per account stop a fat finger from any screen, and an unknown outcome shows as unknown, never assumed filled or failed.

We support a number of executing brokers and clearing firms. Tell us who you clear and execute through and we will tell you where we stand — and if your preferred partners are not connected yet, reach out and we will look at onboarding them.

Not for risk. The risk features in Lavender require no outside market data. Live trading and intraday P&L do require market data, from one of our supported market data vendors.

Lavender Desk is sold through a conversation rather than a checkout, and there is no published price. Tell us how your desk is set up — how you clear, how you execute, how many traders — and we will give you a number that reflects it. Book a demo →

Yes, and we would rather you did. Send us yesterday's start-of-day file — the one your clearing firm already produces — and see your whole desk's risk before you sign. Nothing to install, nothing to connect, and no change to how the desk runs today. How moving works →

Start with your own start-of-day file, so the first thing you see is your book rather than a demo account. Then run Lavender in parallel with your current system, on the same book, for as long as it takes to trust the numbers. The book is built from your clearing firms' own start-of-day files, so both systems are reading the same positions.

Moving from another risk system →

Each trader sees and trades only the accounts you give them. A risk manager sees everything and trades nothing. Every order and action is on the audit trail, with who and when.

Reg T and haircut margin, with headroom, before and after any trade; and portfolio margin, estimated for the accounts you name. Risk limits raise an alert when one is crossed. Margin in detail →

No. Lavender is the risk and trading screen; your brokers and clearing firms stay exactly who they are. Orders go to the brokers you already execute through, under your own agreements with them, and they fill them. Lavender does not execute and never reaches the market itself.

We run it for you. We connect your clearing firms and executing brokers and host your FIX sessions, for execution and drop copy — always on, redundant, with a secondary standing by, and each release proven on the secondary first. Upgrades happen when you choose, never under you mid-session.

Each trader sees and trades only the accounts you give them; a risk manager sees everything and trades nothing, and every order and action is on the audit trail.

Yes.

On a desk, with your own book. A desk sends us yesterday's start-of-day file and runs Lavender beside its current system, on the same book. Where the two differ, the difference is a potential risk or opportunity — near an ex-dividend date, deep in the money, in a hard-to-borrow name, two systems that model American options differently should differ.

On Terminal and Gateway, input by input. Every input behind a number — dividends, forward, borrow — is shown, to compare with your own source. Our documentation carries the worked derivation.

Or just try it. Terminal opens on a sample book with no data feed or broker to configure, on a 7-day trial. Lavender Discord is free, with no card, on any listed ticker.

Most desks move for one of two reasons: the platform they rely on is being retired, or it has stopped being developed and the gap between what it does and what the desk needs has widened year after year. Either way the anxiety is the same — not whether a replacement exists, but whether it covers the work you actually do, and how long it takes to find out.

You can answer that yourself in about a week. Terminal opens on a sample book with no data feed, no broker connection and no implementation call. Put your own structures in front of it, connect your live account read-only when you are ready, and see whether the risk reads the way you expect. There is no professional-services engagement to sit through first.

What a desk should check during the overlap: that whole-book exposure totals the way it does on your current screen; that scenario and stress results are recognizable; that P&L attribution ties out, residual included; and — the one people skip — that where the two systems disagree, the disagreement has a reason you can name. Near an ex-dividend date, deep in the money or in a hard-to-borrow name, two systems that model American options differently should differ. A migration is the one moment you get to re-examine assumptions you inherited.

If you are used to overriding inputs, see the question above — many overrides exist to compensate for weak dividends or a crude curve underneath, and the reason for them often disappears. If your firm's own forecasts have to drive the numbers, that is Enterprise.

On commitment: month-to-month, no implementation fee, no minimum term. Run both systems side by side for as long as you want to. Being locked in is how desks end up stranded on software that stopped moving.

Terminal is built around three questions a desk asks all day.

What am I holding right now? Whole-book exposure across every position, with live dollar-Greeks, regrouped along whatever axis the question needs and totaled. Positions read back as the structures you actually put on rather than as a list of loose legs. A suggested hedge to close a gap against a policy band, worked into a paper account so you can see the book you would be left with.

What happens if? Scenario analysis across spot and volatility where every cell is a true reprice of the whole book rather than a sensitivity estimate. Crisis-scale stress applied to the book you hold right now. Monte Carlo across correlated paths, reporting probability of loss and tail risk. Payoff priced with real dividends, rates and early exercise. Pin risk and expiry, so Friday afternoon is not a surprise.

Can I trust the numbers? P&L attribution split by Greek with the residual shown rather than absorbed. A volatility surface you can inspect. Risk as it stood 1, 5 or 30 days ago. And every input behind every number exposed, so a difference against another source has a named reason.

Scope, stated plainly: US equity, ETF and index options. Windows. One live broker account per seat, connected read-only. No futures or options on futures. No live order entry in Terminal — a trade you work there goes to a paper account. Live trading to your own executing brokers is Lavender Desk.

It comes down to how your book is cleared and whose numbers the risk runs on — not how many of you there are.

Lavender Desk if your desk clears and executes somewhere of its own. Start-of-day positions and real-time drop copy from your clearing firms build the book, orders go out through your own executing brokers, and we run the whole thing for you. This is the one most desks want. Lavender Desk →

Lavender Terminal if you are one trader on your own retail brokerage account — one trader per seat, the broker connection read-only, and any trade you work goes to a paper account. Three traders at a small firm is simply three seats. Terminal →

Lavender Gateway if you want the same numbers in your own code, over a local REST API, for pipelines, models and backtests. Gateway →

Lavender Enterprise when your firm's own inputs and methodology have to drive the risk, in an arrangement built around how you already work. Bespoke, scoped per engagement. Enterprise →

Not sure? Tell us how your desk is set up and we will tell you which one fits.

Lavender provides independently computed option Greeks — dividend-aware, early-exercise-aware, with calibrated forward prices — ticking continuously across ~6,000 underlyings — equities, ETFs and index options.

One analytics engine powers three products: free, on-demand volatility analytics in Discord; a locally-running REST API in Gateway; and a professional desktop workstation in Terminal. Whatever you use, you are working from the same numbers, computed the same way, every time.

Lavender was founded by Jonathan K. Weedon, a technologist and market architect with more than two decades of experience building professional-grade options systems. He founded Derivix in the mid-2000s — writing every core component himself, from pricing models and volatility engines to risk systems and the full execution stack — before its acquisition by FlexTrade.

Read the founder's letter →

Options and volatility traders, quantitative researchers, and developers whose P&L depends on the accuracy of their Greeks — and who know that one source isn't enough.

It is especially relevant for anyone working with American options, dividend-paying underlyings, or strategies where early exercise is a real consideration.

Most platforms compute Greeks using Black-Scholes or simplified models with continuous dividend yield assumptions. Those are exact for European options and an approximation for the American ones you trade — they work reasonably well in normal conditions but produce materially wrong hedge ratios near ex-dates, deep in the money, and for short-dated American options where early exercise is a real consideration.

Lavender uses discrete dividend modeling, explicit early exercise handling, and calibrates the implied borrow rate per expiry — enforcing put-call parity and producing consistent call and put Greeks even in hard-to-borrow names.

If your current provider already handles these correctly, running Lavender gives you an independent second source. Where two good models agree, you have confirmation. Where they diverge, you have a signal worth investigating.

No. Lavender is an analytics and decision-support system designed to work alongside your existing brokers and execution relationships. It provides independent Greeks and risk analytics — it does not execute trades or act as a broker in any capacity.

No. Lavender provides analytics, models and tools so you can make better-informed decisions yourself. It does not provide trade signals, investment advice, or recommendations of any kind.

All three products are available today.

• Lavender Terminal — 7-day free trial, then $390 / seat / month, on Windows.
• Lavender Gateway — 7-day free trial, then $450 / instance / month, up to 3 users.
• Lavender Discord — free, on-demand analytics, open to use today.

A locally-running analytics server that computes implied volatility and Greeks and delivers them via REST API. It runs on your own machine. It includes nine vendor-compatible endpoints, so your existing code works with a one-line host change.

$450 / instance / month, Up to 3 users per instance, after a 7-day free trial. Runs on Windows 10+, macOS 12+, Linux (x64).

View the documentation →

No. Gateway does not deliver bid/ask, volume, open interest or trade data. It computes and delivers independently calculated Greeks and implied volatility. Market data fields in vendor-compatible responses exist only for wire compatibility — they are zeroed or null. Gateway is an analytics engine, not a data feed.

Core: delta, gamma, vega, theta, rho and decay.

Second order: vanna, volga, charm, veta and vera.

Third order: speed, zomma, color and ultima.

Additional first order: epsilon (dividend sensitivity) and lambda (leverage ratio).

Extended Greeks are available on the native Lavender API using greeks=all. All are computed robustly across the full chain — not just at the money.

Lavender computes both. Theta is the conventional partial derivative — the standard per-calendar-day rate most systems report. Decay measures the expected price change from now to the same time on the next trading day, accounting for weekends and holidays.

The two are close on a typical weekday and diverge significantly on Friday afternoons and around holidays. On a Friday, theta shows one abstract day of decay; decay shows what your position actually loses over the three-day weekend.

Theta is available on all endpoints including the vendor compatibility layers. Decay is available on the native Lavender API.

Dividends are modeled as discrete cash events, not as a continuous yield. This produces accurate Greeks near ex-dividend dates, where continuous yield assumptions create material errors in delta and other sensitivities.

The borrow rate is derived from the market rather than assumed, producing consistent call and put Greeks, even in hard-to-borrow names.

Yes. Gateway explicitly values early exercise rather than assuming it away. This produces accurate Greeks for deep in-the-money calls near ex-dividend dates — a regime where European-style models produce systematically wrong results.

As an annualized decimal. 0.25 means 25% annualized IV; 1.50 means 150%.

Nine: Alpaca, AlphaVantage, Intrinio, LiveVol, MarketData.app, Orats, Polygon.io, ThetaData and Tradier. Each layer replicates the wire format of that vendor's options endpoint — the same JSON structure your code already handles, served from localhost. ThetaData v2 and v3 are both supported.

One scaling note: eight of the nine use the same per-1% convention as the Lavender API for vega and rho. ThetaData is the exception — it returns vega, rho and epsilon per unit, 100× larger.

If you already use one of the nine compatible vendors, the change is one line — point your existing code at the local Gateway address instead of your current host. Nothing else changes.

If you are building a new integration, the native Lavender API supports JSON, CSV, NDJSON and HTML output. A basic Python integration is a few lines of code.

No. Access is configured at the gateway level when you run Gateway.exe and enter your subscription email. All REST endpoints work without authentication headers on individual calls.

If you are migrating from a vendor, your existing API keys and auth headers stay in your code exactly as they are — the gateway accepts and ignores them. Gateway runs on localhost, so your code keeps calling a local address rather than a vendor's servers.

Setup instructions appear on the success page immediately after checkout, and in the Gateway Quickstart.

Yes to both. Gateway supports Excel integration, and all client-facing connections use REST over HTTPS only — there are no WebSocket requirements, which matters for firewall-constrained environments.

Yes — 7 days on both Terminal and Gateway, with full access. Same analytics engine, nothing held back.

Payment method required · no charge if you cancel before it ends. Here is exactly how to cancel — it takes about a minute.

You can cancel in a few clicks, without emailing us or making a phone call. Here is exactly how:

1. 1Go to the Lavender billing portal.
2. 2Enter the email address you used when you subscribed. Stripe emails you a secure sign-in link — there is no password to remember. If it has not arrived in a minute or two, check spam.
3. 3Once you are in, click your active plan.
4. 4You will see the product you are subscribed to and a Cancel plan button. Click it and confirm.

That is it. Cancel during your free trial and you are not charged at all. Cancel later and you keep access through the end of the billing period you have already paid for.

Month-to-month means exactly that. No annual commitment, no cancellation fee, no phone call, and no retention script.

Having trouble? Email support@lavender-ts.com and a real person will cancel it for you. You will not be charged while we sort it out.

The billing portal is where you manage everything about your subscription — cancel, change your payment method, download invoices, or update billing details. It is run by Stripe, our payment processor.

You do not have a Lavender password. Access works by email: enter the address you subscribed with at the billing portal and Stripe sends you a secure sign-in link.

Two things catch people out: it must be the same email you used at checkout, and the sign-in link sometimes lands in spam. If neither is the problem, email support@lavender-ts.com.

Tell us. Email support@lavender-ts.com before day 7 and we will sort something out — we would rather you reached a real decision than an accidental one.

Whatever your firm requires — we will provide it. In practice, most people need some combination of:

• An invoice or receipt. Every payment generates one automatically, and you can download invoices any time from the billing portal. Billing details can be set to your firm's name and address rather than your own.
• Contract terms to review. There is no contract to negotiate — it is month-to-month with no minimum term and no auto-renewing annual commitment. The full terms are on our user agreement page.
• A W-9, vendor form, or security questionnaire. Email info@lavender-ts.com and we will complete it.

Two things that tend to make approval simpler: the 7-day trial means you can evaluate it before asking anyone for anything, and because you can cancel from your own portal at any time, there is no long-term commitment for anyone to weigh up.

How your firm handles software spending is your call, not ours. For multiple seats, several instances, or a firm-wide arrangement, email info@lavender-ts.com.

Email info@lavender-ts.com and tell us how your desk is set up — Terminal seats for traders, Gateway for the people building behind them, and the option to run the engine on your own inputs inside your own environment.