Infrastructure servers overview
CoreLatency infrastructure servers are bare metal cloud instances designed for teams that want dedicated compute without the friction normally associated with physical provisioning. Deployment is typically near-instant, with exact timings depending on the operating system and image path selected.
This section is split into three pages:
- Overview summarises the platform and lists your deployed servers.
- Deploying a server explains the provisioning workflow step by step.
- Custom images covers custom ISO and disk image workflows.
Platform summary
We currently offer two server flavours:
- Standard bare metal servers without GPU acceleration.
- GPU-enabled bare metal servers for accelerated workloads.
Servers are presently available in our London data centre. Additional locations will be introduced over time, but the deployment and operating model remains consistent across regions.
Provisioning model
Provisioning a server is designed to be fast and operationally direct. In the standard flow, you select a server profile, choose an operating system, apply network and access settings, select an SLA, and confirm the order. Longer billing terms are usually more cost-effective, although shorter terms are also available where offered by the platform.
If you need a non-standard bootstrap path, you can deploy without a default operating system and instead boot from your own custom ISO or disk image. This is useful when you already maintain hardened or preconfigured operating system builds. Those workflows generally require additional configuration in the console or from the operating system itself after boot, rather than being handled entirely through the standard provisioning flow.
Deployment flow
The server deployment wizard is structured as follows:
- Flavour and billing model: choose the hardware profile and the commercial term.
- Location: select the deployment site. At present, London is the available data centre.
- Operating system: deploy a standard image, select from available favourites, choose alternatives such as AlmaLinux or Fedora, or leave the server without an operating system so you can use your own image workflow.
- Configuration: set the hostname, attach the server to a VPC, assign IP addressing, and add SSH keys. From this step you can also create SSH keys and make certain IP-related changes directly in the workflow.
- SLA: every server includes a basic SLA. A premium SLA is also available.
- Confirm: review the build before final submission.
Support contracts and SLAs
Basic SLA coverage is included with all servers. If you require premium coverage, or a custom SLA arrangement for your organisation, raise a request with Contact us and we will route it for commercial review.