See which controls your algorithm really has, before it touches a live account.

No. It means the checks found the controls they look for in the code you submitted. Compliance is a property of your whole operation (governance, records, oversight, the people responsible), not of one file. Treat GREEN as “this code isn't the thing standing in your way”.

No. Aurelia Spes Limited is not authorised or regulated by the FCA. We sell analysis software and don't carry on any regulated activity. When the site names a rule, it's naming published regulatory material that the checks are based on, not claiming any link with the regulator.

Your first check is free once you've confirmed your email, no card needed. It's per person, not per account: a second account on the same inbox shares it. After that, top up with extra credits or choose a plan. Consumers also have a 14-day right to cancel a new subscription or a top-up (see § 10).

One credit pays for one compliance check or one backtest; they are interchangeable. Solo Trader (Tier I) has 2 credits, Professional (Tier II) 5, Institutional (Tier III) 10, Broker Lite 5, Prime / Hedge Fund 12 and HFT Enterprise 20. When they run out they refill in full 48 hours later, not on a fixed day; unused plan credits don't roll over. To keep going before then, top up with extra credits (2 for £7, then £3.50 each, up to 100 at a time in the web app) or move up a plan. If you move up part-way through, the credits you have already used in that 48 hours still count: moving up gives you the difference straight away.

Yes, from Professional (Tier II) and on every business plan. After a backtest, Generate code writes the strategy you tested, with exactly the parameters and risk limits you set, as Python or Pine Script (TradingView). Every file carries the same risk layer: a stop on every order, loss limits that close the position and keep trading halted until you re-arm it, a leverage cap, order-rate limits, error handling and an audit log. Generating code uses no credit; Check compliance on it uses one, and the report is linked to the backtest. Settings that could never protect anything (no stop, a 100% drawdown limit) or that would be prohibited for a retail client (a crypto derivative) are refused with the setting to change. Generated code is a starting point you paper trade first: it isn't investment advice, and it isn't a statement that the strategy is lawful, compliant or suitable.

We use your code only to produce your report, and we keep the report, not the code. Reports are visible only to you: asking for someone else's report gets the same “not found” answer as asking for one that doesn't exist. The one exception is a firm's team, and only if you accept an invitation to it: the plan owner can then see the checks you run while you are a member, never the ones from before you joined or after you leave. Don't paste live API keys or passwords. The checker flags hard-coded credentials, but the safest key is one that never leaves your machine.

Python, MQL4 and MQL5 (MetaTrader), Pine Script (TradingView) and C# (cTrader, NinjaTrader) are read directly: the checks know what a stop loss, a kill switch and a lot-sizing function look like in each of them, and the suggested fixes come back in the language you submitted. Anything else is analysed too: the report says which language it read, so you can see what it assumed.

Yes. Drag a whole folder onto the terminal in your browser, or attach up to 12 files, and they are checked as one strategy, so a control in your risk module counts for the file that calls it. From a folder, dependency and build folders are left out, files that look like keys or secrets stay on your computer, and the files most likely to hold trading and risk logic are chosen first; you're told what was left out and why. The limit is 60,000 characters of code in total, and the report lists the files it read.

Every check you run is kept on your account. Past reports in the terminal lists them (what you named it, when you ran it, the language, the files and the verdict) and opens any of them again in full. They're visible only to you (or, if you accept an invitation to a firm's team, also to its plan owner for the checks you run while a member), and deleting your account deletes them, except checks you ran on a firm's plan, which stay on the firm's record.

The full analysis uses an AI model (Anthropic's Claude) to read what your code does. A built-in rule scanner matches control patterns in the code (stop losses, sizing, kill switches, audit logs) and steps in if the AI is unavailable. Either way, the RED / YELLOW / GREEN rules are enforced on our server afterwards, and the report says which engine produced it. Your code is never run.

We measure it on strategies the checks have never seen, written and labelled by independent reviewers who never saw the rules. On the latest such test (60 verdicts, October 2026) the rule-based scan agreed with the reviewers on 80% of verdicts; most of its misses were on the cautious side. The AI engine has not been measured that way yet, so we don't quote a figure for it. Every report says it can make mistakes. Check each finding against your own code.

It shouldn't. Your code is treated as data to analyse, never as instructions, and the verdict rules are enforced on our server afterwards, so a comment claiming a control exists doesn't put one there. Automated tests check this. But an AI model can still be misled in ways nobody has thought of yet, which is one reason the rule scanner cross-checks every AI report and every report says it can make mistakes.

The iPhone, Android and desktop apps are built but not released yet. Join the list in § 08 and we'll email you when each one is out. The web terminal works on phones in the meantime.

Yes, on Institutional, Prime / Hedge Fund and HFT Enterprise. Ask for an invoice in the terminal under Your account: give us the company name, VAT number, purchase-order reference and the number of seats, and we email an itemised invoice with our bank details and 14 days to pay. Your plan starts the day the payment clears. On every plan, paying by card also produces a proper itemised invoice: checkout asks for your billing address and VAT number, and business plans ask for the company name and PO number so they print on the invoice and on every renewal.

Yes. Professional and above, and every business plan, come with seats: Broker Lite 3, Professional 5, Institutional and Prime / Hedge 25, HFT Enterprise 50, each counting the person who owns the plan. Invite a colleague by email in Your team; they create their own account with that address and join automatically, with their own password. The plan's credits are shared, and the person who owns the plan can see every check the desk has run and who ran it, which is the record the firm has to keep, and is written into our Privacy Policy.

Every check produces an evidence record you can download as a PDF: the report reference, the strategy name, when it ran and who ran it, the client categorisation and asset class, the language and the files read, a SHA-256 checksum of the code that was submitted, the rule-set version that produced the verdict, the engine and model used, a SHA-256 checksum of the report itself, and the verdict rules that were applied. That answers “which version of your checks produced this?” years later. The report checksum is computed from the report as stored, so the copy in your file can be shown to be the copy that was issued.

Self-hosted deployment is on our roadmap and marked SOON on the plans. For a data processing agreement or a security review, use the form and tell us what you need.

Anyone aged 18 or over. The checks are built around UK rules, so they're most useful for strategies traded through UK-regulated brokers.