Scalable web and application platforms require hardware that can grow in line with the workload. At IT-RESELL.COM, we configure web and application servers from HPE, DELL, Lenovo and Fujitsu – whether as a single high-performance host or as a scalable cluster comprising multiple nodes. Refurbished systems are particularly cost-effective, especially for stateless web tiers.
Buy web hosting & application servers – for the web, Kubernetes & CI/CD
Web infrastructure · Containers · Kubernetes · CI/CD · new & refurbished
Which servers would you like to purchase?
Please send us your enquiry or contact our representatives directly.
Technical requirements for a web hosting and application server
A balanced CPU/RAM ratio, fast NVMe storage and a high-performance network are key to determining throughput and response times.
A balanced ratio for handling parallel requests. RAM according to caching requirements (Redis, application caches).
NVMe for databases, caches and CI/CD builds. Stateless web nodes require little local storage.
10/25 GbE for high throughput and fast communication between nodes (microservices, service mesh).
Multiple compact 1U nodes for horizontal scaling – load distributed via a load balancer and expandable with additional nodes.
Distributed load handling mitigates the failure of individual nodes – provided there are sufficient nodes (N+1).
Remote management (iLO/iDRAC/XClarity/iRMC) for automated deployment within a running cluster.
Typical software stacks
NGINX · Apache · Node.js · Java / Tomcat · .NET · PHP · Docker · Kubernetes · GitLab CI · Jenkins · GitHub Actions Runner.
Our hardware recommendations
From a single web server to a scalable Kubernetes cluster.
| Scenario / Requirement | Recommended systems | Configuration recommendation |
|---|---|---|
| Single web/application server | DELL R650 · HPE DL360 Gen 11 · Lenovo SR630 V2 · Fujitsu RX2530 M6 | 1U, balanced CPU/RAM, NVMe – compact and efficient |
| Scalable web tier (multiple nodes) | Multiple DELL R650 or HPE DL360 (refurbished) | Multiple 1U nodes behind a load balancer, horizontally scalable |
| Kubernetes/container cluster | DELL R750 · HPE DL380 Gen 11 · Lenovo SR650 V2 | Dual-socket, plenty of RAM, NVMe – multiple worker nodes + control plane |
| CI/CD build servers | DELL R750 · HPE DL380 Gen 11 · Fujitsu RX2540 M6 | Powerful CPU + fast NVMe for speedy builds and tests |
| Cost-optimised (refurbished) | DELL R640/R740xd · HPE DL360/DL380 Gen 10 · Lenovo SR530 | Ideal for stateless web nodes – maximum cost-effectiveness |
As a Dell and Lenovo partner, we receive particularly attractive terms on a project-by-project basis – it’s well worth enquiring, especially for scale-out projects with multiple nodes.
Specific use cases
Scalable web platform
Four stateless web nodes (refurbished DELL R650) behind a load balancer handle fluctuating peak loads – if one node fails, the others take over seamlessly.
On-premises Kubernetes
Three Lenovo SR650 V2s as worker nodes, plus the control plane, form an on-premises K8s cluster – full control over data and costs, without reliance on the public cloud.
Self-hosted CI/CD
A high-performance DELL R750 acting as a dedicated build server significantly speeds up pipelines – with full control and no ongoing cloud charges.
Why refurbished web hosting and application servers make sense
Stateless web and app nodes are the prime example of where refurbished hardware shines: the performance of the previous generation is perfectly adequate for web workloads. Instead of an expensive new server, you can build a broader, more resilient cluster for the same budget.
Frequently Asked Questions
For modern web architectures, usually several smaller nodes (horizontal scaling): more resilient, flexibly scalable. A single powerful server is worthwhile for monolithic applications.
Excellent. Stateless web nodes are interchangeable – the performance of the previous generation is sufficient, and you can build a larger, more redundant cluster for the same money.
Yes. Several worker nodes plus a control plane form a fully-fledged on-premises K8s cluster. We configure appropriately sized nodes.
Speed, control and predictable costs: builds often run faster on dedicated hardware than on rented cloud runners – without ongoing cloud charges.
Multiple nodes behind a load balancer (N+1): if one node fails, the others take over. It is important to have a sufficient number of nodes.
For high throughput between microservices and container clusters, we recommend 10–25 GbE.
Multiple stateless web nodes behind a load balancer – if one node fails, the others take over seamlessly. This is what makes refurbished hardware particularly attractive here: cheaper nodes, a broader cluster.
Owning your own web hardware gives you full data sovereignty, predictable costs and lower latencies. With continuous operation, owning your own hardware quickly pays for itself compared to ongoing cloud fees.