Comparator
FTC vs FCA vs MiCA+DORA Regulatory Cost
Compare US (FTC), UK (FCA), and EU (MiCA + DORA) compliance cost for an AI-finance product. Snapshot data with as-of date — not legal advice.
Runs in your browser. Nothing you enter is uploaded, and no account or API key is needed.
Inputs
Multiplies recurring compliance hours by 1, 2 or 3.
Multiplies setup and recurring compliance hours.
Loaded cost of your compliance staff per hour.
Snapshot as of 2026-04-25. Hours, fees and legal rates are illustrative planning assumptions, not survey data. Not legal advice.
Lowest-cost jurisdiction
US
United States — FTC oversight: $3.5k a month, $42.4k a year recurring, plus $7.2k one-time setup ($49.6k in year one).
Cost ranking
| Jurisdiction | Setup | Monthly | Annual | Year one | Friction (1-3) |
|---|---|---|---|---|---|
| US (FTC) | $7.2k | $3.5k | $42.4k | $49.6k | 1 |
| UK (FCA) | $10.8k | $5.5k | $66.5k | $77.3k | 2 |
| EU (MiCA + DORA) | $36.0k | $14.3k | $171.1k | $207.1k | 3 |
United States — FTC oversight: what to watch
- FTC enforcement is reactive, not registration-based — but settlements (like the 2024 Rite Aid algorithmic-bias order) bite hard.
- State-level rules (CA, NY) layer on top — biggest cost driver if you serve those markets.
- Disclosure and substantiation rules apply to performance claims; backtests need disclaimers.
United Kingdom — FCA principles-based: what to watch
- Consumer Duty (in force 2023) requires demonstrable consumer-good outcomes — keep evidence.
- FCA's 2024 AI report is technology-neutral but explicitly applies operational-resilience rules.
- Financial Promotions regime applies if you market to UK retail — separate gateway approval needed.
European Union — MiCA + DORA: what to watch
- MiCA: CASP licensing required for crypto/asset-related products (≥6-month process, capital requirements).
- DORA: ICT-third-party register, threat-led penetration testing every 3 years, incident reporting in 24h.
- AI Act (2026): high-risk uses (credit scoring, insurance pricing) need conformity assessment.
Methodology
Setup = setup hours × complexity × your hourly rate. Monthly = monthly hours × complexity × volume tier × your hourly rate, plus annual registration fees ÷ 12 and external legal hours × the local legal rate ÷ 12. Annual = 12 × monthly. The per-jurisdiction hours, fees and legal rates are illustrative assumptions for a small AI-finance product; replace them with your counsel's estimates before budgeting.
How to use it
- Pick the data volume tier (early, scaling or production) and the processing complexity multiplier for your product.
- Enter your in-house compliance hourly rate.
- Read the lowest-cost jurisdiction and the table: one-time setup, recurring monthly and annual cost, and the year-one total for the US (FTC), UK (FCA) and EU (MiCA + DORA).
- Read the obligations listed under each jurisdiction; they drive the hours and fees in the model.
- Treat the figures as illustrative planning assumptions: replace them with your counsel's estimates before budgeting.
Questions people ask
What's FTC vs. NLT in this context?
The tool compares three regimes an AI-finance product may fall under: US Federal Trade Commission oversight (enforcement-based, no registration), the UK FCA's principles-based regime (Consumer Duty, financial promotions), and the EU's MiCA crypto-asset licensing plus DORA operational-resilience rules. The URL keeps an older 'NLT' label; there is no separate NLT regime in the model.
How are compliance costs estimated?
With a simple hours-based model: setup hours and monthly compliance hours per jurisdiction, scaled by your complexity multiplier, volume tier and in-house hourly rate, plus annual registration fees and external legal hours at a local legal rate. The per-jurisdiction hours, fees and rates are illustrative planning assumptions for a small product, not survey data, so replace them with your counsel's estimates before budgeting.
Why is the cost ratio not stable across firm sizes?
In this model the in-house hours scale with the volume tier and complexity, while registration fees and external legal hours stay fixed, so the fixed part weighs more at low volume. Because the EU profile has more hours per month (30 vs 8 in the US), the EU-to-US ratio is roughly 4× at typical inputs and moves only modestly as you change the tier or hourly rate.
Does the calculator account for one-time vs. ongoing cost?
Yes: it reports one-time setup separately from the recurring monthly and annual cost, plus a year-one total (setup + annual). It does not model incident costs such as responding to a regulatory inquiry or enforcement action, which are tail risks to budget for separately.
Is this a forecast or current-state estimate?
A current-state snapshot dated 2026-04-25. Rules change, for example as EU AI Act obligations for high-risk uses phase in, so re-check the headline obligations listed under each jurisdiction and update the assumptions when they move.
Guides, formulas and worked examples
- Examples AI Finance Regulatory Cost: Worked Examples
- Checklist AI in Finance Audit Trail Checklist
Related tools
- Comparators Market Data API Cost Calculator
Compute annual cost of market data across Databento, Polygon, Alpaca, Tiingo, FMP, and Alpha Vantage for your exact universe, bar resolution, and real-time needs.
- Generators Trading System Blueprinter
Pick your data source, LLM, broker, storage, risk engine, and logger. Get a Mermaid architecture diagram and a copyable starter file tree — the full stack before you write code.
- Comparators Broker API Comparator
Alpaca vs IBKR vs Tradier vs Schwab vs Robinhood — compare auth, rate limits, order types, market data, MCP, and fees before wiring a line of code.
Articles
- 12 min read The BaFin + EU Guide for Retail AI Traders (2026)
BaFin and EU rules for retail AI trading, publishing finance content, and automated strategies. Education-safe phrasing and the minimum compliance stack.
- 12 min read Compliance Audit Trails for LLM-Driven Trade
Schema, append-only log design, and reproducibility patterns for SEC/FINRA-compliant LLM trade audit trails.
- 13 min read Auditable LLM Decision-Making for Finance
Six load-bearing audit layers mapped to MiCA, MiFID II, SEC 17a-4, FINRA 4511, SR 11-7, BaFin MaRisk. Collapsing any layer destroys defensibility.
Use it from code
The same calculation as a JavaScript module you can import. It runs where you import it, with no request, key or rate limit.
import { compute } from "https://aifinhub.io/engines/ftc-vs-nlt-regulatory-cost.js";