Store
Buy a standard deployment without a sales cycle
Most brokerage software is sold through a long cycle because most deployments are genuinely bespoke. A standard one is not, and pretending it needs six calls wastes everybody’s time.
What you get
A working console from day one
Every plan starts from the same deployed stack — you are configuring a live console, not waiting on a build.
Plans
Five plans, sized by deployment
Every plan is the same stack with a different ceiling. What moves between them is how many brands and entities it carries, how much of it you drive through an API, and how much of the deposit flow we take.
Billed each month, minimum term applies
Starter
One entity, one live environment
- Client portal and back office
- Fiat and crypto wallets
- Localization Module included
Advanced
One entity, partner network included
- Everything in Starter
- Partner and IB tooling
- Assisted onboarding and migration
Growth
PopularLive and staging environments
- Everything in Advanced
- Back-office API
- RiskDesk included
Pro
Several brands on one account model
- Everything in Growth
- Multi-brand and additional domains
- Named account manager
Enterprise
Multi-entity, prioritised delivery
- Everything in Pro
- Multiple entities and environments
- Prioritised delivery queue
Branded mobile apps
Native builds for both mobile app stores, carrying your brand and published under your own developer accounts. Charged once per app rather than monthly.
One-off setup on a standard deployment
Minimum term, indicative
Discount for annual prepayment, indicative
Branded mobile app setup, one-off
The figures on this page are sample values used while the commercial model is finalised. They are registered as placeholders and are not a quote.
What a standard deployment covers
The products in a standard build
How it runs
Four steps, and the last one is not ours
Pick a plan
Sized by how many products and environments you need rather than by client count.
Pay
Card or bank transfer. The commercial terms are the ones shown, not a starting position.
Configure
Instruments, account groups, fees and onboarding rules, with an engineer on the call.
Go live
Once your licence and payment approvals are in place, which is usually the longer half.
When to talk to us instead
Three cases where buying from a page is the wrong move
Multi-entity or unusual jurisdictions
Several entities with different rules is a different deployment shape and should be quoted rather than bought from a page.
Heavy third-party integration
If a platform, provider or internal system has to be connected, the work is real and needs scoping before a price means anything.
You want us to operate it
Managed operation is a white label arrangement rather than a plan, because what is being sold is people's time as much as software.
FAQ
Store: common questions
8 short answers to what teams ask before a demo.
They are sample values while the commercial model is finalised, and they are registered as placeholders rather than published terms. The pricing page carries the same figures and the same caveat.
A standard deployment of the products in that plan, configured for one entity in one jurisdiction, with onboarding and support. The comparison table lists what steps up between plans; anything beyond it is a quote.
Yes, on every plan. Configuration and onboarding for a standard deployment sit inside the monthly figure. A migration from an existing stack is not standard and is quoted separately.
Three months minimum on any plan. Prepaying twelve months takes fifteen per cent off the monthly figure, which is the gap between the two columns on the billing toggle.
A percentage of the deposits routed through PayVault, charged alongside the subscription and stepping down as plans go up. Fees charged by your own payment providers are theirs and sit outside it.
You can buy and configure. You cannot take live client business without the permission your jurisdiction requires, and that timeline is usually longer than the technical one.
Configuration can begin as soon as payment clears. Going live depends on your licence and payment-provider approvals rather than on us.
Yes. Because the products share one account model, moving up is configuration rather than redeployment, and what you have already set up carries over.
Still have a question?
A specialist will answer it directly, with your set-up in mind.
Ask a specialistIf in doubt, ask for a quote
A plan that does not fit is worse than a slightly longer conversation. Describe the deployment and we will say which route is right.