Company
About Roaraq
The discipline layer between a trader and their broker.
Why this exists
Most trading losses that end a career are not analysis errors. They are discipline errors: the position that was three times too large, the revenge trade after a loss, the tenth entry into a symbol that already cost money four times that morning. Traders know their rules. The problem is that nothing enforces them at the moment that matters.
Roaraq is that enforcement. It is the only order-entry surface you use, so it can check every order against your own limits before the order reaches your broker, and refuse the ones that break a rule. Your broker keeps doing what brokers do: execute and hold custody. Roaraq adds one thing, and does it before the fill instead of after.
What we believe
A rule you can bypass with one click is a suggestion. Overrides are off by default. Loosening a rule waits for a delay you set. The kill switch takes time to disarm. Friction is the product.
The reason has to have numbers in it. "Blocked" is not an answer. "Buy 400 AAPL would take AAPL to 91.2% of equity; limit 10%" is. Every block, warning and override is stored with the rule version that produced it.
Money is append-only. Snapshots, fills, blocks and the audit log are never rewritten. Corrections are new rows. When something is disputed, the history is there.
Uncertainty fails closed on opens and open on closes. Stale data, a broker outage or an engine error means you can reduce risk but not add it. You can always exit, and you can always trade directly at your broker.
How we make money
A subscription. Roaraq does not route order flow, does not take payment for order flow, does not sell data and does not hold funds. If it is free for you, someone else is the customer; here you are the customer.
Principles
- Fail closed on opens, open on closes
- When anything is uncertain, you may reduce risk and may not add it. No configuration can weaken this.
- Append-only money
- Financial rows are never rewritten. Corrections are new rows. Disputes are answered from history, not memory.
- Everything auditable
- If a human could ask "why did this happen?", the answer is in a row.
- Legos, not monoliths
- Every external dependency sits behind an interface. Adding a broker is one folder.