Skip to content
Genesis Ark

Deployment

Self-hosted vs SaaS trading infrastructure: how to choose

Hosted platforms are faster to start. Self-hosted systems give you control over data, change and cost over time. A dedicated managed instance sits between them. This is a practical comparison across regulation, operations, security, cost and exit, with the questions that decide it for your firm.

Author
Genesis Ark Engineering
Published
Reading time
7 min read

Most institutional crypto trading platforms are sold as hosted services. You sign up, connect your venue accounts and trade through the vendor's cloud. For many firms that is the right choice. For others, particularly banks, regulated brokers and firms in markets with strict data rules, it is not an option at all.

The choice is not binary. There are three common deployment models, and the right one depends on your regulator, your team and how central the system is to your business.

The three models

Shared SaaS. The vendor runs one platform for many clients, in its own cloud. Each client's data is separated logically, within shared infrastructure. The vendor operates everything and upgrades everyone at the same time.

Dedicated managed instance. The vendor runs a separate installation for each client, either in the vendor's cloud account or in the client's. The client gets its own databases and services, and the vendor operates them.

Self-hosted. The client runs the software in its own data center or cloud account, and its own team operates it. The vendor ships releases, documentation and support.

Where SaaS wins

Hosted platforms have real advantages, and it is worth being clear about them.

Speed to start. There is nothing to install. If the vendor already connects to your venues, you can be trading in days rather than weeks.

No operations burden. Monitoring, upgrades, backups, scaling and incident response are the vendor's job. For a small desk without an infrastructure team, this matters more than anything else.

Shared improvements. Every client gets every fix and feature as soon as it ships.

Network features. Some platforms connect their clients to each other, for example to request quotes from dealers on the same network. That only works when everyone is on one platform.

If you are a small fund or desk, your regulator has no objection, and you have no one to run a trading system at 3 a.m., a hosted service is often the sensible answer.

Where self-hosting wins

Data residency and confidentiality. Your orders, positions and client records never leave your environment. For banks, and for firms in jurisdictions that require client data to stay in the country, this can settle the question by itself. It also means your trading activity, your strategies and your client list are never stored in a third party's database.

Regulatory and outsourcing treatment. Many regulators treat a critical system run by a third party as outsourcing, with requirements for due diligence, contractual rights of access and audit, exit plans and ongoing oversight. Running the system yourself changes that conversation. You still need to manage the software vendor, but the operation of the system sits inside your own control environment.

Change control. With SaaS, the vendor decides when you are upgraded. With self-hosting, your change board decides. You can test a release in your own environment against your own integrations before it goes live, and you can schedule upgrades around your business.

Security architecture. A self-hosted system sits behind your firewall, authenticates through your identity provider and stores venue credentials encrypted with your own key management. You decide which outbound connections exist. For a security team, that is much easier to approve than a new external platform holding the keys to your venue accounts.

Network placement. You can run the system close to the venues you trade on, or inside the same environment as your other trading systems, and measure its performance in your own setup.

Cost shape. SaaS is usually an annual subscription that never ends. A self-hosted license, particularly a perpetual one with annual maintenance, has a different cost profile: a larger initial payment and lower ongoing fees. Which is cheaper depends on how long you use the system, but the self-hosted model is typically easier to predict over several years.

Customization. With source access, your own engineers can adapt the system to your workflow. With SaaS, you wait for the vendor's roadmap.

What self-hosting costs you

Self-hosting is not free control. It moves work onto your team.

  • Operations. Someone has to monitor the system, respond to alerts, run upgrades and test backups. Crypto trades every hour of every day, so this means on-call coverage.
  • Infrastructure. Compute, storage, network and a second site for disaster recovery are yours to provide and pay for.
  • Expertise. Your team needs to understand the system well enough to tell a venue problem from an application problem, which takes time.
  • Upgrade discipline. Falling several releases behind is easy and makes every later upgrade harder.

A vendor serious about self-hosting reduces this burden with clean packaging, clear runbooks, dashboards and alert rules that work out of the box, upgrade tooling, and a support tier that covers the hours you trade. Ask to see them.

The middle option: a dedicated managed instance

A dedicated managed instance gives you a separate installation with your own databases, operated by the vendor. You get much of the isolation of self-hosting without staffing a trading operations team.

It suits firms that:

  • want their data in a dedicated environment, in a region they choose
  • do not have, or do not want to build, round-the-clock operations for a trading system
  • want the option to move to self-hosting later without changing software

When the instance runs in the client's own cloud account, the client keeps ownership of the infrastructure and the data, and the vendor operates through controlled access. That arrangement can satisfy residency requirements while removing most of the operational load.

Fig. 1. A dedicated instance inside the client's own network boundary, with outbound connections to venues only. Illustrative composition with sample data.

A comparison by question

Shared SaaS, dedicated managed and self-hosted deployment compared
QuestionSaaSDedicated managedSelf-hosted
Where does our data live?In the vendor's environment, shared infrastructureIn a dedicated environment, in the vendor's account or yoursIn your environment only
Who decides when we upgrade?The vendorAgreed between youYou
Who is on call when a venue disconnects at night?The vendorThe vendor, with your team informedYour team, backed by vendor support
Who holds our venue credentials?The vendor's platformYour dedicated instance, encrypted with keys you or the vendor manageYour system, encrypted with your keys
How long does it take to start?FastestProvisioning plus configurationDepends on your infrastructure and change process
What happens if we leave the vendor?You export what the vendor allows and rebuild elsewhereYou can often take over the instance or its dataWith a perpetual license, the system keeps running; you lose updates and support

The exit question

Ask every vendor what happens at the end of the relationship, because it reveals more about the model than any feature list.

With a subscription SaaS platform, your trading stops when the contract ends. You need a replacement in place and your historical records exported beforehand. With a perpetual self-hosted license, the software keeps working. You lose new releases and support, but your records and your ability to trade remain in your hands. Source escrow arrangements can add further protection if the vendor ceases trading.

Regulators increasingly ask firms to show credible exit plans for critical technology. The deployment model largely determines how credible yours is.

How to decide

Work through these questions in order. The first one that gives a firm answer usually decides it.

  1. Does a regulator, a client contract or your own policy require the system or the data to run inside your environment or your country? If yes, self-hosted or a dedicated instance in your own account.
  2. Do you have, or will you build, a team that can operate a trading system around the clock? If no, a dedicated managed instance or SaaS.
  3. Do you need control over when changes reach production? If yes, self-hosted or dedicated.
  4. Will your engineers want to customize the system? If yes, look for source access, which in practice means self-hosted.
  5. Do you need network features that exist only on a shared platform? If yes, SaaS has an advantage.
  6. Over a three to five year horizon, which cost profile fits your budget? Compare subscription totals against license plus maintenance plus your own infrastructure and staff.

A note on starting small

The decision is less risky if you begin with modules that do not place orders. A portfolio view across venues, reconciliation or TCA can be self-hosted with read-only venue keys and little operational burden. Running them for a few months shows your team what operating the system involves before anything critical depends on it, and shows the vendor's support in practice.

Whatever you choose, make sure the model is written into your contract: where the system runs, who operates it, who holds the keys, how upgrades happen and what happens at exit. Those answers matter more than the label on the pricing page.

See it on your own workflow.

A scoping call with an engineer, then a demo on sample data that mirrors your venues, desks and limits.