Managed hosting technical specification
Not every customer receives every component below. The architecture is selected according to the workload, but the capability exists across the managed stack.
Edge and network
The default preference for straightforward websites is to move work toward efficient edge delivery where practical.
- Authoritative DNS capability
- CDN/caching
- TLS certificates
- DDoS mitigation
- Web Application Firewall capability
- Rate limiting and traffic controls
- Global edge compute where appropriate
Conventional compute
Applications that need conventional servers can use cloud or dedicated infrastructure rather than forcing every workload into serverless architecture.
- Linux servers
- Docker containers
- Node.js services
- PostgreSQL databases
- Reverse proxies
- Private networking and firewall controls
- Backups and snapshots according to the service
Operations
Operational discipline matters as much as raw infrastructure.
- Version-controlled code
- Controlled deployment
- Configuration review
- Monitoring and logging capability
- Rollback planning
- Separation of customer-facing services from internal operational systems where appropriate
Infrastructure, delivery and operations
Production sites can combine global edge services with conventional cloud/server infrastructure according to the workload.
Full text list
- Cloudflare — Global edge delivery, DNS, CDN, TLS, DDoS protection, WAF, rate limiting, Workers and storage services. Provider information
- Hetzner — Cloud and dedicated compute, networking, storage and conventional server workloads. Provider information
- Linux — Production server operating systems and secure service hosting. Provider information
- Docker — Portable containers for applications, services and controlled deployment. Provider information
- PostgreSQL — Production relational data storage for applications and services. Provider information
- GitHub — Source control, deployment history and auditable delivery workflows. Provider information
- Node.js — JavaScript runtime for APIs, tooling and server-side applications. Provider information
- Nginx — Web serving and reverse-proxy capability where conventional servers are appropriate. Provider information
Web standards, code and frameworks
We are not locked to a single framework. Straightforward sites should stay straightforward; applications can use deeper stacks when justified.
Full text list
- HTML5 — Semantic document structure and modern browser standards. Provider information
- CSS — Responsive layout, presentation, accessibility and performance-conscious styling. Provider information
- JavaScript — Standards-based browser and application behaviour. Provider information
- TypeScript — Typed application development for maintainability and safer change. Provider information
- React — Component-based user interfaces when an application needs them. Provider information
- Next.js — Full-stack React framework for suitable applications and content sites. Provider information
- Vue — Progressive user-interface development. Provider information
- Svelte — Compiled, performance-conscious user-interface development. Provider information
- Astro — Content-focused websites with low client-side JavaScript where appropriate. Provider information
- Python — Automation, data processing, APIs and supporting services. Provider information
The detailed pages exist for customers who want to inspect the engineering. The customer-facing offer remains deliberately straightforward.
