Staged environments
Separate estates for development, staging, and production, all provisioned from the same baseline image. Behaviour in staging reliably predicts behaviour in production because the builds are identical.
Platform and Application Servers
The server layer your platform runs on.
Dedicated infrastructure for long-running, stateful workloads that need to behave the same way every time, across every region, through every change event.
What are platform and application servers?
Platform and application servers are the persistent compute layer that sits beneath your product. The backends, processing engines, session managers, databases, and application logic your platform depends on continuously.
Unlike end-user compute, where each instance is provisioned for an individual, this layer serves your platform itself. The workloads are long-lived, stateful, and need to remain stable through upgrades, scaling events, and maintenance windows.
Level-up your business with smarter solutions
Deployment models
How this layer is deployed
Multi-region
Servers across multiple regions using the same build, same configuration, and same operational procedures. A server in London is identical to one in Tokyo.
Dedicated estates
Every component is exclusively yours. Compute, storage, network, and management plane are fully separated from any other customer’s infrastructure.
Hybrid estates
Shared physical infrastructure with strict resource guarantees and logical isolation at the hypervisor, network, and storage levels. Same performance behaviour as dedicated, with cost efficiency as the trade-off against absolute physical separation.
Single-region
All servers within a single data centre or metro region. For platforms where proximity to a specific system or user base is the priority.
Configuration and compliance
How every server is built and maintained
Every server is provisioned from a standardised, security-hardened OS image. Version-controlled, identical across every deployment, with no manual builds or undocumented modifications.
Isolation and failure domains
How failures are contained
Compute
Dedicated CPU and memory per server. Reserved, not shared. One server’s workload cannot contend with another’s.
Storage
Dedicated per server with independent I/O paths. Encrypted at rest with per-server keys. Cryptographically wiped on deprovisioning.
Network
Isolated network paths with policy enforcement at the infrastructure layer. Cannot be modified from within the guest.
Failure domain segmentation
Compute, storage, and network operate as independent failure domains. A problem in one stays in one. Impact boundaries are architectural, not accidental.
Lifecycle
Full lifecycle control
Provision
Define region, resource profile, OS baseline, and network configuration. Built from the controlled image and added to your estate.
Scale
New servers use the same baseline and configuration as existing instances. New capacity is identical to what is already running.
Upgrade
Scheduled, tested, and executed with rollback paths defined before work begins.
Maintain
Documented procedures within agreed windows. Services drained, connections closed gracefully, restarts sequenced to your workload’s requirements.
Decommission
Storage cryptographically wiped. Resources released. Network paths and access credentials revoked.
Hardware profiles
Compute-optimised
High clock speed, dedicated cores, lower memory. For CPU-bound, latency-sensitive workloads.
Memory-optimised
High memory relative to CPU. For large in-memory datasets, caches, and state tables.
Balanced
Even distribution across CPU, memory, and storage. General-purpose.
Storage-optimised
High-throughput local NVMe with elevated IOPS. For heavy read/write workloads such as databases and logging.
- Argentina
- Australia
- Austria
- Belgium
- Brazil
- Bulgaria
- Canada
- Chile
- Colombia
- Croatia
- Czech Republic
- Denmark
- France
- Germany
- Greece
- Hungary
- India
- Ireland
- Israel
- Italy
- Japan
- Latvia
- Lithuania
- Luxembourg
- Mexico
- Netherlands
- Norway
- Poland
- Portugal
- Romania
- Singapore
- Slovakia
- Slovenia
- South Africa
- South Korea
- Spain
- Sweden
- Switzerland
- Turkey
- Ukraine
- United Kingdom
- United States
Global network
Consistent builds across 60+ locations
Every region uses the same build process, the same configuration controls, and the same operational procedures. There is no per-region onboarding. Region is a parameter in your deployment, not a separate project.
Integration boundaries
Where this layer sits
Connects to
Orchestration and fabric layers for placement, scaling, and lifecycle automation. Low-latency systems where deterministic network paths are required. Monitoring, audit, and disaster recovery for observability and continuity. End-user compute, where per-user instances depend on the backend services running in this layer.
Does not replace
Application logic or platform-specific configuration. Orchestration control planes. Upstream data feeds, API gateways, or application-layer services.
Cross-links
See how platforms use platform and application servers
End-user computeIsolated, dedicated compute for each of your usersLink 1Trader VPSAlways-on environments for algorithmic tradersLink 2Player-hosted serversDedicated servers for playersLink 3Inference hostingPer-user inference environmentsLink 4Transaction processing infrastructureIsolated per-client processingLink 5Orchestration and fabric layersOrchestration and lifecycle automationLink 6Monitoring, audit and disaster recoveryObservability, forensics, and continuityLink 7
