Compute
Cloud VPS, bare metal and private infrastructure sized for predictable throughput, not just vCPU count.
Operate · Own the platform beneath the product.
Cloud & Infrastructure
Infrastructure decisions become business constraints. We design landing zones, network boundaries, storage tiers and recovery procedures before migrating workloads. Where the group’s Joy Services platform fits, we can deploy on KVM compute, bare metal, colocation and the group network with clear responsibility boundaries.
6 engineering concerns
4-stage delivery path
12 core technologies
Group delivery available
What we engineer
The concerns that decide whether it survives.
Not a feature list. The architectural obligations we design, test and hand over.
Network
BGP, RPKI-validated routing, IX peering, BYOIP, anycast DNS and DDoS mitigation across the group network.
Storage
S3-compatible object storage, NVMe-backed volumes, backup policy and lifecycle rules.
Edge delivery
CDN, reverse proxy, cache rules, TLS automation and origin protection.
Landing zones
Environment separation, identity, network policy, infrastructure as code and cost guardrails.
Operations
Monitoring, on-call runbooks, patching, capacity review and recovery testing.
Delivery architecture
A path with checkpoints, not a black box.
Each stage produces an artefact that the next stage depends on. If an assumption fails, we stop and reassess rather than building on it.
Talk through your constraints
01
Workload and dependency map
Traffic, data gravity, latency, recovery and compliance requirements determine the placement model.
02
Landing zone design
Network segmentation, identity, storage, backup and observability are defined as code.
03
Migration and cutover
Replication, DNS TTL strategy, rollback and acceptance tests are rehearsed before cutover.
04
Operate and optimise
Capacity, cost, patch level, backup restore and incident readiness are reviewed on a fixed cadence.
Technology context
Core stack
Technology choices follow constraints. These are the tools we commonly use, not a mandated catalogue.
KVMLinuxCephBGPRPKIAnycast DNSTerraformAnsiblePrometheusGrafanaLokiWireGuard
Handover
What you leave with
Deliverables are written so your team can operate, audit and evolve the system without us.
- Landing zone
- Network and routing plan
- Migration and rollback plan
- Observability stack
- Operations runbook
Cloud & infrastructure
Bring the constraint. We will bring the architecture.
Tell us what has to be true for this system to be acceptable: security, latency, recovery, regulation or operating cost.