The paperwork behind the platformRead past
Read past
the product name.
A trading brand is one part of the story. Our briefs examine the company information, service terms and questions that sit behind it.
Find a platform brief26 briefs to explore
Find the company question.
| Platform | What the brief examines | Written by |
|---|---|---|
| Frame Pro Kapidex | A public confirmation block is not a completed application | Alan Draper |
| Instant Xp Cipro | An interface label cannot specify a product's behaviour | Goran Radanovic |
| Logic Eurax Lab | A reproducible result needs versioned inputs | Yash Majithia |
| Model Exorex 100 | The boundary between information and execution needs an interface contract | Alan Draper |
| Model Maxalt Opt | A funding prompt needs a documented account state | Goran Radanovic |
| Prompt Akpro Lab | A referral form and a trading system have different outputs | Yash Majithia |
| Sensor +Neo Codrix | A smart-link label is not a documented routing rule | Yash Majithia |
| Sensor Ai Daypro | Automatic retries need an explanation before any integration test | Alan Draper |
| Sensor Celexa Pro | A transaction receipt needs a link to the event it claims to record | Goran Radanovic |
| Sensor Codrix Neo | A connection claim needs a map of read and write access | Yash Majithia |
| Sensor Flarex Xp | A control needs an owner, a trigger and a limit | Alan Draper |
| Sensor Imitrex Nx | A callback message needs a corresponding submitted event | Goran Radanovic |
| Slide +Lab Codrix | A historical example needs its data and rule versions | Alan Draper |
| Snap Lotemax Hub | A changed response means the target system must be reidentified | Goran Radanovic |
| Snap Manerix +X | A technical feature must be linked to the same service terms | Yash Majithia |
| Spike +500 Amrix | A parameter is meaningful only inside a defined account model | Goran Radanovic |
| Spike +Nx Cipro | An event log needs documented meanings for its states | Yash Majithia |
| Spike 500 Amrix | The instrument definition comes before any risk calculation | Alan Draper |
| Spike Amrix 500 | A price comparison needs consistent units and time boundaries | Goran Radanovic |
| Spike Cipro Nx | A displayed estimate needs a documented calculation boundary | Yash Majithia |
| Spike Nx Cipro | The payment instruction needs a chain of attributable identifiers | Alan Draper |
| Stake +0.6 Manerix | A protocol claim would need an explicit system relationship | Yash Majithia |
| Stake +100 Capex | A balance field needs rules for when it changes | Alan Draper |
| Stake +2U Lotemax | An exit process needs separate request and completion records | Goran Radanovic |
| Stake Lispro Neo | A reward calculation needs a defined accounting unit | Alan Draper |
| Stake Maxalt 100 | A technical history needs an exact product identity | Goran Radanovic |
No briefs match that name. Try another spelling.
The document matters
as much as the name.
A familiar label does not establish who provides a service. Each brief explains what the available sources say and where the connection remains unverified.
How we read the evidence
Alan Draper
Goran Radanovic
Yash Majithia