Hosting environments are selected by our Technology department based on the computational requirements, traffic expectations, and maintenance scope of your build. Rather than applying a single generic setup, we configure infrastructure that balances performance, security, and long-term operating costs.
Technical evaluation criteria Every build requires an underlying infrastructure aligned with its runtime dependencies. During the scoping phase, the Technology department reviews four primary technical constraints:
1. Architecture and Runtime: Static sites, headless frontends, dynamic monolithic applications, and microservices have distinct execution profiles. Serverless edge networks are evaluated for decoupled frontends, while containerised or bare-metal instances are specified for platforms requiring persistent state or long-running daemon processes. 2. Regional Latency and Data Residency: Target user demographics determine server locations. For UK and European user bases, data nodes are provisioned in London or Frankfurt regions to ensure GDPR compliance and minimise round-trip network latency. 3. Traffic Profiles and Scaling: Predictable corporate websites operate efficiently on fixed-capacity provision. High-concurrency platforms or eCommerce stores subject to marketing surges require auto-scaling configurations with managed load balancers and edge caching. 4. Maintenance Overhead and SLA: Managed platforms handle security patching and operating system updates upstream. Self-managed virtual private servers require operational maintenance, which must be factored into your ongoing support arrangement.
Sequence of events Infrastructure is selected and deployed through a structured progression:
1. Brief and Technical Audit: Operations & Client Services log your requirements through the portal. If migrating an existing application, the Technology department requests temporary read-only access to inspect your database size, asset libraries, and server configurations. 2. Architecture Specification: Within 48 hours of receiving a complete brief, the Technology department produces the hosting specification. This is integrated directly into your bespoke quote, detailing the chosen environment, provisioning boundaries, and recurring vendor costs. 3. Provisioning and Staging: Once the initial deposit is confirmed, the Technology department provisions an isolated staging environment. All core development and internal validation occurs here under strict firewall rules. 4. Production Handover and DNS Cutover: Prior to launch, the production environment is hardened, SSL certificates are issued, and the DNS records are verified. The cutover is scheduled during studio working hours (Monday to Thursday, 09:00–17:00 GMT) to ensure direct engineering support.
Client responsibilities To prevent delivery bottlenecks, clients must provide the following items during scoping:
- DNS and Registrar Control: Access to your domain registrar or an assigned internal technical contact capable of applying DNS record changes within 24 hours of request.
- Traffic and Concurrency Estimates: Realistic projections for baseline visits and expected marketing spikes. Underestimating traffic leads to under-provisioned infrastructure that degrades under load.
- Third-Party Integrations: Explicit lists of external APIs, payment gateways, CRM connections, or database dependencies that require network allowlisting or dedicated IP addresses.
- Billing Account Ownership: Where client-owned cloud tenancy is requested, administrative ownership and active billing instruments must be configured prior to deployment.
Failure cases and mitigation Technical deployments occasionally encounter friction that requires escalation:
- DNS Lockouts or Administrative Lags: If registrar access is restricted or controlled by an external IT department with slow turnaround, cutover will stall. We require DNS access verification at least five working days before scheduled release.
- Under-Reported Database Footprints: Migrating undocumented multi-gigabyte databases or unstructured file storage midway through deployment causes unexpected infrastructure cost increases and migration delays. Audits must be completed during the initial scoping window.
- Mid-Build Scope Shifts: Adding dynamic functionality to what was scoped as a static build necessitates a complete hosting re-evaluation. Such revisions alter delivery timelines and will be recalculated in an adjusted quote. Deposits are non-refundable once your production slot is held. Before work begins, sums not yet earned are refunded pro rata; after work begins, completed work and booked time are charged. Defects are fixed free of charge within the acceptance window. The full terms are on the Refund Policy page of the main site.
Hosting selection checklist Before confirming your infrastructure plan, verify the following operational details:
- [ ] Target audience geography confirmed to establish server region.
- [ ] Concurrency and asset storage requirements documented in the brief.
- [ ] Domain registrar access verified and credentials supplied securely.
- [ ] Direct technical contact identified for DNS approval.
- [ ] Third-party service credentials and API dependencies collected.
- [ ] Cloud billing account activated if self-hosting rather than studio-managed.
Queries regarding your current hosting allocation should be submitted via the Ask Xylo chat on this portal.