What we will publish,
including the parts that cost us.
6 commitments with triggers and deadlines, made while all 6 are empty and therefore free — which is the only honest time to make them. Every record on this page is currently empty. No payouts, no refusals, no incidents, 6 rulebook versions and not one account bound to any of them. The commitments are published now precisely because there is nothing in them yet.
6 things. Each with a trigger and a deadline.
Because a commitment without a deadline is a preference.
All 6 are trivial to honour today, because all 6 are empty. That is the point of writing them down now. They were made when there was nothing awkward in them, and they can be held against whatever ends up in them.
Fewer claims, each of them checkable
This category has a specific credibility problem, and it is not that the claims are loud. It is that the claims that matter most cannot be checked by anyone outside the firm making them. Payout totals are self-reported and, with one exception in filed accounts, unaudited. Pass rates are self-reported or missing. Our research found no firm publishing a change log, a version history, or the share of payout requests it declines.
The answer to that is not a louder claim. It is fewer claims, each of them checkable, made before there is any commercial reason to shade one.
Every figure on this site is either zero, a published rule, or something you can verify without our permission. There is no third category, and there is no number here that we would have to be trusted about.
This is also why there is no incident log below with three tidy resolved incidents in it, no uptime percentage, and no count of disputes upheld in traders’ favour. Those numbers would be flattering, and we do not have them.
Every version, at its own address
This is the commitment we expect to be tested on first, so it is stated as a mechanism rather than as an intention:
- Every account records the rulebook version it opened under, and is governed by that version for its entire life.
- A new version binds only accounts opened after it — including when the change is in the trader’s favour. Selective retroactivity is how a policy becomes discretionary.
- Every version stays published at its own permanent address — the 5 superseded versions are archived below.
The current version and its changelog are on the rulebook page. The mechanism has already run 5 times, every one of them before any paid challenge existed — v0.10 added the account-multiplication rule and v0.11 revised its review clause, both dated 2026-08-02, so the policy on running multiple accounts is public before there is a single account it could apply to.
Who decides when an outage counts
Any breach recorded during a declared outage is void, and open positions during an outage are closed at the pre-outage price where that is better for the trader. The weak point in that sentence is the word “declared”. So:
- An outage is declared by us, in public, with start and end timestamps, within one hour of it ending — not when a trader reports it and not when it becomes convenient.
- If a trader can demonstrate a platform failure we did not declare, the breach is void anyway and the incident is added to the log retroactively with a note saying we missed it.
- The log records incidents nobody complained about. An outage at 03:00 UTC with no open positions still gets a row.
Incidents recorded: none. There is no platform yet, so there is nothing to record. The first entry will appear here, dated, whether or not it cost anyone anything.
Dated, with the previous wording
If something on this site is wrong — a figure, a description of someone else’s published terms, a broken commitment — write to hello@upme.com. Corrections are made with a dated line saying what changed, and the previous wording stays visible. Pages are not silently edited.
This applies to the research library as well. Anything we write about another firm is drawn from that firm’s own published terms or from a primary document, and if a term has changed since we read it we would rather be told than be stale.
Who runs this, and under what
- Entity
- upme is operated by UpMe Ltd., registered in Anguilla. Who we are →
- Regulation
- UpMe Ltd. runs a simulated-account trading evaluation. We are not a broker, exchange, custodian, financial institution, fiduciary or a regulated financial-services provider, and none of the protections that attach to a regulated financial product apply to this service.
- Authorisation
- Per legal advice obtained by the company, operating this simulated evaluation does not require financial-services authorisation; a future brokerage phase would open only with authorisation. The service is not available where prohibited by sanctions or local law. Every rule, limit and policy is versioned and dated; changes are published, never made quietly. Full status on the legal page.
- Contact
- hello@upme.com — the correction address above.