Recommended Services
Supported Scripts
Dedicated Servers · Dublin
Dedicated servers for data transfers.
Plan the transition.
Transfers, downloads and replication can shape a server choice as much as CPU or RAM. Review the published network terms for the selected configuration. Changing physical servers can alter storage, operating-system configuration and network rules.
- High performance
- 24×7 support
- 1 Gbit port speed
The specifications
behind the choice.
Compare the key specifications in the server rows, then review the complete details for the selected configuration.
SSD Dedicated Servers

Jupiter SSD
Intel® Core™ i7-6700 Quad-Core
RAM
64 GB DDR4
Storage
2 x 250 GB SSD
Data transfer
30 TB
Connection
1 Gbit/s
CPU: Intel® Core™ i7-6700 Quad-Core
RAM: 64 GB DDR4
Drives: 2 x 250 GB SSD
Drive configuration: Software RAID 1 SATA @ 6Gb/s
Data transfer: 30 TB
Bandwidth: 1 Gbit/s
Connection: 1 Gbit/s/port
Backup storage: 100 GB
Full root access
1 dedicated IPv4 address
IPv6 /64 subnet
VNC installation
Reverse DNS management
Redundant Network · Juniper Routing Technology
Minimum network availability: 99%

Neptune SSD
Intel® Xeon® E3-1275 v5 Quad-Core
RAM
64 GB DDR4
Storage
2 x 480 GB SSD
Data transfer
30 TB
Connection
1 Gbit/s
CPU: Intel® Xeon® E3-1275 v5 Quad-Core
RAM: 64 GB DDR4
Drives: 2 x 480 GB SSD
Drive configuration: Software RAID 1 SATA @ 6Gb/s
Data transfer: 30 TB
Bandwidth: 1 Gbit/s
Connection: 1 Gbit/s/port
Backup storage: 100 GB
Full root access
1 dedicated IPv4 address
IPv6 /64 subnet
VNC installation
Reverse DNS management
Redundant Network · Juniper Routing Technology
Minimum network availability: 99%

Mercury SSD
Intel® Xeon® E5-1650 v3 Hexa-Core
RAM
256 GB DDR4
Storage
2 x 480 GB SSD
Data transfer
50 TB
Connection
1 Gbit/s
CPU: Intel® Xeon® E5-1650 v3 Hexa-Core
RAM: 256 GB DDR4
Drives: 2 x 480 GB SSD
Drive configuration: SATA @ 6Gb/s
Data transfer: 50 TB
Bandwidth: 1 Gbit/s
Connection: 1 Gbit/s/port
Backup storage: 100 GB
Full root access
1 dedicated IPv4 address
IPv6 /64 subnet
VNC installation
Reverse DNS management
Redundant Network · Juniper Routing Technology
Minimum network availability: 99%
SATA Dedicated Servers

Jupiter SATA
Intel® Core™ i7-6700 Quad-Core
RAM
64 GB DDR4
Storage
2 x 2 TB HDD (Software-RAID 1)
Data transfer
30 TB
Connection
1 Gbit/s
CPU: Intel® Core™ i7-6700 Quad-Core
RAM: 64 GB DDR4
Drives: 2 x 2 TB HDD (Software-RAID 1)
Drive configuration: SATA @ 6Gb/s @ 7200 rpm
Data transfer: 30 TB
Bandwidth: 1 Gbit/s
Connection: 1 Gbit/s/port
Backup storage: 100 GB
Full root access
1 dedicated IPv4 address
IPv6 /64 subnet
VNC installation
Reverse DNS management
Redundant Network · Juniper Routing Technology
Minimum network availability: 99%

Mercury SATA
Intel® Xeon® E5-1650 v3 Hexa-Core
RAM
128 GB DDR4
Storage
2 x 2 TB HDD (Software-RAID 1)
Data transfer
50 TB
Connection
1 Gbit/s
CPU: Intel® Xeon® E5-1650 v3 Hexa-Core
RAM: 128 GB DDR4
Drives: 2 x 2 TB HDD (Software-RAID 1)
Drive configuration: SATA @ 6Gb/s @ 7200 rpm
Data transfer: 50 TB
Bandwidth: 1 Gbit/s
Connection: 1 Gbit/s/port
Backup storage: 100 GB
Full root access
1 dedicated IPv4 address
IPv6 /64 subnet
VNC installation
Reverse DNS management
Redundant Network · Juniper Routing Technology
Minimum network availability: 99%
Dedicated server management from €50.00/month
If your team needs help operating the server, discuss the responsibilities before ordering.
Custom Servers
Need a different configuration? Contact us for a server tailored to your project. Operating system and control panel options are available, along with additional IP addresses and backup services at an extra cost. Availability, compatibility and the total cost are confirmed before you order.
Hardware reserved
for your workload.
A dedicated environment combines hardware and network terms. Review the offered connection and traffic alongside the application’s data movement and operating requirements.
Root/Admin access
Configure the application runtime and services with administrative access. Keep the deployment account separate from everyday application users.
Operating system options
Compare software versions between the old and new environment before migrating. A different system image can require configuration changes.
Dedicated CPU & RAM
Builds, tests and demonstrations can have different peaks from a live website. Include those tasks when assessing the development environment.
HDD, SSD or NVMe storage
Imports and batch work can create intermediate files. Measure their temporary space requirements as well as the final output.
Network-level DDoS protection
Background services and their APIs need their own authentication and failure handling alongside the included network protection.
Dedicated IPv4
Each plan includes one IPv4 address. Additional addresses depend on availability, eligibility and cost.
Optional server management
Describe the runtime and the step that fails when requesting help. Agree which setup or application work is included before implementation.
99% network availability
Minimum network availability of 99%, as listed for these server models.

Choose the operating environment.
The selected panel or hypervisor must be compatible with the system and hardware. Include its licence and maintenance path in the server configuration.










Confirm the server region.
Server location and service coverage are different. We confirm the available deployment region for the chosen hardware.

- United States
- Canada
- Asia
- Europe
- Australia
Plan the software
alongside the hardware.

HTML5

CSS3

JavaScript

Angular

ReactJS

Node.js

CloudLinux
A PRACTICAL STARTING POINT
Keep the server stack compatible and maintainable.
The operating system and optional control panel should fit the hardware and the application. Confirm availability and licences before choosing the final configuration.
01 · Prepare
List required software versions, administration tools and any specialist installation media.
02 · Verify
Check supported installation options, remote access and the application’s compatibility with the intended system.
03 · Keep ownership clear
Keep installation records and an update owner, including responsibility for paid software renewals.
Illustrative sequence. The actual configuration and responsibilities follow the agreed requirements.
Identify the data and configuration needed to rebuild the service, where the recovery copies are kept and who can access them during an incident. Agree the acceptable recovery objectives rather than assuming that hardware ownership provides a complete backup service. A restore exercise should check the application and its recent records, not merely the existence of an archive. Optional backup or administration work needs an explicit scope.
DELIVERY & OWNERSHIP
Check readiness before demand increases.
Describe the expected busy period and the activity behind it. Separate a known event or planned launch from an unsupported assumption about future growth.
01 · Prepare
Compare workload growth with the published CPU, disk and network specifications.
02 · Verify
Use the relevant application activity to review CPU, memory, storage behaviour and transfers against the published server specification.
03 · Keep ownership clear
Set an operating review for capacity and network usage, with a named owner for escalation or a configuration change.
HOSTING & TECHNICAL SUPPORT — CLIENT FEEDBACK
“His pricing is excellent, and his hosting options are more than fair. Communication was outstanding every time I contacted him, he responded promptly. When I had an issue with my email ,which was something I did to mess it up , he jumped straight on it and had everything sorted quickly.”
Benjamin S.
SERVICE AREA
For your audience in Dublin.
Virtualisation.
Serving Dublin can involve customers with different usage patterns. Describe when and how the audience uses the service rather than assuming the city name predicts demand.
Compare workload growth with the published CPU, disk and network specifications.
The map shows the area served, not a datacenter or a local office. The physical hosting location and availability are checked separately.
- Active data versus archived data
- Read and write patterns
- Recovery procedure and responsibilities
Dublin
PRACTICAL QUESTIONS
Before we agree the next step.
Questions about the work, the checks and the handover.
It removes the need to share that physical server with other customers, but performance still depends on the hardware, storage, software and workload. Confirm the configuration against a real requirement.
Compatibility, access, available images and licensing must be confirmed for the specific model. Describe the intended platform before ordering so those requirements can be checked.
Potentially, but compatibility, licence costs and installation requirements matter. Some changes are easier on a clean system, so discuss the intended panel before the server begins carrying live applications.
YOUR NEXT STEP
Plan the guests as well as the physical host.
Tell us what is changing, when it matters and what evidence you already have. We can assess the preparation that is actually justified.
Compare workload growth with the published CPU, disk and network specifications.
