Recommended Services
Supported Scripts
Dedicated Servers · Utrecht
Dedicated servers for a specialist stack.
Plan the recovery.
The operating system and optional control panel should fit the hardware and the application. Confirm availability and licences before choosing the final configuration. Include disk contents, remote access and off-server recovery copies in the discussion.
- High performance
- 24×7 support
- 1 Gbit port speed
Dedicated hardware.
Clearly stated options.
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
Management work needs an agreed scope based on the operating system and applications.
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.
Dedicated resources.
Explicit management responsibilities.
A move to physical hardware should preserve the working parts of the service. Check runtime, storage, network rules and the route back before retiring the source.
Root/Admin access
Retain control over system configuration as the workload changes. Document the settings so a later resource or application change can be checked.
Operating system options
Consider the supported lifetime and update path as well as initial compatibility. Paid software and administration tools can have separate licence requirements.
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
A test environment may hold copied databases, builds and temporary files. Set a cleanup routine instead of letting unused releases consume the allocated storage.
Network-level DDoS protection
Availability also depends on application behaviour, maintenance and recovery. Treat network DDoS protection as part of that wider operating plan.
Dedicated IPv4
Each plan includes one IPv4 address. Additional addresses depend on availability, eligibility and cost.
Optional server management
Share the affected site, account and observed behaviour so a hosting issue can be investigated with useful context.
99% network availability
Minimum network availability of 99%, as listed for these server models.

Software and storage
that fit the application.
Keep the initial stack maintainable: record installed software, paid renewals and the update owner. Optional administration work should have an agreed scope.










Deployment details matter.
Confirm the physical deployment location and model availability before ordering. The city named on this page identifies the audience served, not a local facility.

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

HTML5

CSS3

JavaScript

Angular

ReactJS

Node.js

CloudLinux
A PRACTICAL STARTING POINT
Choose disks for the way the application reads and writes.
Capacity alone does not describe a storage requirement. Consider access patterns, growth and recovery alongside the published disk configuration.
01 · Prepare
List live data, indexes, logs and expected growth. Separate the working dataset from archive and backup requirements.
02 · Verify
Test representative reads and writes and verify usable capacity under the intended disk layout.
03 · Keep ownership clear
Document disk configuration, monitoring and the response to a storage fault.
Illustrative sequence. The actual configuration and responsibilities follow the agreed requirements.
Hardware, operating system and application support are different layers. Record the work included in the offer and any additional administration agreed with the team. Identify who responds when the machine is reachable but an application task fails. Keep authorised access and escalation contacts current so a problem does not become a search for the right owner. Specialist application development remains a separate discussion from the physical server specification.
DELIVERY & OWNERSHIP
Decide what information is actually required.
List the information used for the agreed task and who needs access to it. Avoid collecting extra records simply because a form or system makes it possible.
01 · Prepare
Include disk contents, remote access and off-server recovery copies in the discussion.
02 · Verify
Review access to application data, disk contents and off-server copies, including the records used in testing.
03 · Keep ownership clear
Document recovery-copy ownership and the handling requirements that remain with the business or application administrator.
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 Utrecht.
Storage planning.
The audience area does not describe the entire system. For work serving Utrecht, also identify existing providers, external tools and other users affected by a change.
Changing physical servers can alter storage, operating-system configuration and network rules.
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
Utrecht
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.
Permissions, runtime versions, services, database configuration, certificates and network rules can all affect the result. Verify the application on the destination before treating a successful copy as a completed migration.
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
Make the transfer a controlled change of environment.
Describe the information the service will handle and any known requirements. We can identify the technical decisions and the additional review needed.
Include disk contents, remote access and off-server recovery copies in the discussion.
