How we engage
What this costs depends on what you are running.
We do not publish a price list, because a licence for a two-person prop desk and a licence for a multi-entity brokerage are not the same product. What we can publish is exactly what drives the number, and what happens at each stage — so you can judge the shape of it before you talk to anyone.
- What it is
- A licensing engagement: the platform modules you need, configured to your instruments and policies, on infrastructure we operate or you do.
- Who it is for
- Brokers, institutions and professional desks. We are not set up to license to individual retail traders — you would reach Raptor through a brokerage running it.
- Why it matters
- Publishing a single figure would be misleading in both directions: too high for a small desk, and far too low for a firm needing multi-entity support and its own connectivity.
- How it connects
- Scope is modular. Most firms start with the platform and portal, then add CRM, risk and the intelligence layer as they need them.
- What happens next
- Send us your requirements and we will come back with a written scope and a number. info@777raptor.com
What drives the number
Which modules
Terminal, client portal, CRM, back office, risk engine, IB management, API access and the intelligence layer are licensed separately. You are not obliged to take all of it.
How many accounts
Client count and account count are the main scaling factor, because they drive infrastructure, support load and data volume.
Instruments and venues
The number of asset classes and the number of liquidity relationships to connect and monitor affect both setup and ongoing work.
Entities and brands
One brand under one licence is simpler than several brands across several jurisdictions with separate reporting.
Who operates it
We can run the infrastructure, or you can run it in your own environment. That choice changes the commercial shape substantially.
What you migrate
Bringing existing clients, balances and history across is real work, and it is scoped explicitly rather than assumed.
Ask for a written scope
Tell us the modules, the client count, the instruments and who operates it. You get a written scope and a number, not a discovery call that leads to another discovery call.