Certain workloads hate neighbours. A warehouse system near Gebze may need to print hundreds of picking sheets before the first trucks roll out at 06:00. An automotive parts maker in Bursa may run its MRP calculation through the night. Put either of them on shared hardware and their speed starts to depend on strangers: whoever else is renting a slice of the same host. The month-end report finishes in twenty minutes on Tuesday and two hours on Wednesday, and no one can say why. Renting a dedicated server removes the guesswork. You get one physical machine in a professional facility, paid monthly, with every CPU core, memory module and drive reserved for you. There is no capital purchase, nothing new on the asset register and no server room to keep cool. Electricity, air conditioning and replacing a dead component are the data centre's job. Operating system, databases, virtual machines, backups and security are ours, handled entirely over remote access. We put that split in writing on day one, so nobody argues about responsibility in the middle of an outage.
The classic mistake is ordering the biggest machine in the price list. Our approach is to measure first, cost the software licences together with the rent and then operate the server by rules everyone has signed off.
We size the hardware from what your current systems actually do. If the database spends its time waiting on storage, NVMe drives. If reports are built in RAM, more memory. If an ageing single-threaded application is the limit, a smaller number of high-clock cores.
A site in Turkey or in the EU, dual power and dual uplinks, contractual deadlines for hardware replacement and a written description of what the provider must do as a data processor for your company.
A RAID level chosen for the workload and access to the IPMI or iDRAC-style management interface. If the operating system will not start, we can still see the screen and fix it without waiting for facility staff.
When useful, a hypervisor such as Proxmox or Microsoft's Hyper-V turns the server into several virtual machines: ERP here, file storage there, a remote desktop host alongside. Each one gets fixed resources and a patch window of its own.
A firewall sits in front of the machine. Branches and staff working from home come in over VPN, admin traffic travels on a network separate from application traffic, and nothing is exposed publicly unless someone has approved it.
Every day the data is copied to outside storage that cannot be erased before a set date. When a single hour offline would cost you more than renting a spare, a replica server is added and kept in sync.
Patching, watching drive and array health, opening tickets with the facility, re-checking the system after any component swap and an annual review of whether the machine is still the right size and price.
Lead time is mainly set by stock at the provider. The final migration date is only agreed once a full practice run has been completed and timed.
An agent records processor, RAM, storage and network use on the systems you run today. If possible the week includes the monthly closing or an inventory count, when the load is highest.
One or two configurations with rent, licensing and our fee added up, set against what a large VPS would cost. The choice rests on figures, not on instinct.
The server is fully set up, then we perform a trial migration and time it. That timing decides the switch-over slot, which is always after hours.
Production moves across, power users confirm everything works, and the machine enters normal operation with alerting and a fixed patching rhythm.
Watch the per-core licensing. Microsoft typically licenses Windows Server and SQL Server by the number of cores. A model with double the cores can look cheap on the rental invoice and still double what you pay Microsoft, even though your ERP never touches that extra capacity. We therefore always cost hardware and licences as one figure, and the answer is frequently a server with fewer cores running at a higher clock speed.
Standard configurations tend to be handed over in a few business days, while special builds may take weeks. With the practice migration included, plan on roughly a fortnight to a month before production runs on it.
Our alerting spots it and we log a fault with the facility. Their engineer replaces the drive, and we follow the array rebuild to completion, with the server online the whole time. RAID only protects against hardware failure, though. Accidental deletion and ransomware are covered by the off-site copies.
That arrangement is colocation. It works, but somebody has to rack the machine, cable it and change parts on site, and that is not a service we provide; a firm with engineers near the facility would have to do it. Renting avoids the issue because the hardware remains the facility's responsibility.
We migrate everything to its new home, securely erase the old machine and record that we did so. Before signing, we ask the provider how returned drives are destroyed and whether you get a certificate. File that certificate alongside your KVKK retention and destruction policy.
Monday to Friday, 09:00-18:00 Turkey time (GMT+3). Response times follow your plan: Start 4 hours, Business 1 hour, Premium 15 minutes. Premium contracts also include a round-the-clock duty line.
Describe the systems that will run on it, the approximate size of your databases and any rules about where the data must be kept. You will receive matching configurations with the total monthly cost.
We have your enquiry
A reply will reach you by the next working day at the latest. If your message says work has come to a halt, it goes to the top of the pile.
No such city in our list. Try another spelling, or just pick the closest big city: we work entirely over remote connections, so nothing about the service changes from one province to the next.
The only cookies here are the essential ones: they keep the site running and remember the city you picked. Nothing is used for advertising or tracking. See our privacy notice for more.
