Bare metal / Your operating model
Unmanaged dedicated servers for your operations team
An unmanaged dedicated server is a physical machine with server administration primarily in your hands. It can suit teams that already manage Linux or Windows systems and want direct control over their software. Agree on the infrastructure support boundary with Mixal before deployment.
Unmanaged dedicated plan options
Choose a starting point for a quote. Capacity, pricing, availability, and included services are confirmed before you order.
Self-Managed Essential
For a team operating its own steady workload.
- Define the base CPU, memory and disk configuration
- Your team manages the operating system and applications
- Confirm hardware support and replacement terms
Self-Managed Performance
For resource-intensive applications managed by your team.
- Review sustained CPU, memory and storage demand
- Your team manages the operating system and applications
- Confirm hardware support and replacement terms
Custom Bare Metal
For specialized self-managed hardware requirements.
- Specify hardware, networking and recovery access
- Your team manages the operating system and applications
- Confirm hardware support and replacement terms
Start with the essentials
Make the right choice for your project
Control the software
Choose a compatible operating system and application stack within the service’s installation and access options.
Own the maintenance
Assign responsibility for patches, monitoring, firewall rules, credentials, and application updates to named people.
Prepare for failure
Keep an independent recovery plan for hardware incidents, bad updates, and accidental data changes.
Know where infrastructure support ends
Unmanaged does not mean every provider offers the same support. Clarify hardware replacement, network troubleshooting, OS reinstall options, remote-console availability, and response procedures. Application debugging, database repair, and routine security maintenance should have an explicit owner rather than an assumption.
Treat remote access as part of the design
Before changing firewall or authentication settings, confirm how you would regain access. Restrict administrative entry points, use individual accounts, and retain a secure record of the build. A server that only one person knows how to operate creates avoidable business risk.
Budget for operations as well as hardware
The server rental is only part of the cost. Include licences, backup storage, monitoring, staff time, and recovery work. A managed arrangement may be better value when your team cannot maintain a reliable patching and incident-response routine.
Compare the fit
Choose by the work you need to do
From decision to deployment
Give your setup a clear starting point
-
Write a responsibility matrix
Assign OS, applications, monitoring, backups, security changes, and incident communication.
-
Validate access and recovery
Test administrative access and confirm the process for console access or reinstall assistance.
-
Operate from a runbook
Document deployment, patch windows, alert handling, and a restore rehearsal.
Useful answers
Before you get started
Does unmanaged mean no support at all?
Not necessarily. Infrastructure support may be included, but its scope varies. Confirm the boundary between provider incidents and your server administration.
Do I need an experienced administrator?
You need someone capable of operating the chosen OS and application stack, including security updates and recovery. If that is unavailable, discuss a managed service.
Is RAID enough for recovery?
No. Disk redundancy can address certain disk failures, but it does not replace independent backups or protect against every deletion, compromise, or site-level failure.
Technical references
Make it yours
Bring your requirements.
Let’s work through the options.
Tell Mixal what you are building, who it serves, and what your team needs to manage.