Questions we hear,
and our answers.

A VPS is a slice of a shared physical host. CPU steal time spikes, IO is contested, and noisy-neighbour effects are invisible to you. Bare-metal removes all of that: you see the whole machine, not a guest view of it.

Yes, root from the first boot. You set the firewall, you choose the kernel, you install whatever you want. The line at our side stops at the network port and the IPMI controller.

Any OS that can be expressed as an ISO can be booted via IPMI/KVM: mount your own ISO over IPMI and install it yourself. Debian, Ubuntu, RHEL clones, FreeBSD, Proxmox, VMware ESXi, a custom build: we don’t care, we don’t gate it. Windows Server: we install it on request; the licence, and everything licensing needs, is yours to bring. We do not supply or resell licences.

Yes. It is your machine: any hypervisor or container stack, within the acceptable use rules (Terms, section 4).

Anywhere from a few hours to 7 business days once payment clears. The spread comes down to whether the configuration you need is already on the shelf. A build that needs parts sourced, or a configuration nobody keeps on a shelf, takes the far end of that range.

Once payment clears, the access arrives as a ticket in the HostiServer panel. What is in it depends on what you need: IPMI, if you want to do everything yourself, or SSH, if you want us to set the operating system up. Either way the machine has been tested in full by then.

Supermicro, Dell and Gigabyte are the main makes, with ECC memory in every server. All of the hardware is ours, with a stock of spare parts, so a failed part is replaced from that stock at our cost; a machine that is down is an emergency, handled as fast as possible, often within hours. Every server is fully tested before handover: memory, disks and ports.

Disks are any type and size the job needs: SSD, NVMe or HDD. On two disks with Linux the default is a software mirror; with more disks, the RAID level you need, software or hardware. A hardware controller is fitted when the job needs one. RAID protects against a failed disk, not against a mistaken delete, so the backup is still yours to make.

Moving over is your job by default; if you need our help, ask and we will help where we can. The console, the addresses and root are yours from the first boot, so a migration needs nothing from us to start.

Yes, by agreement. Whether a given upgrade is possible depends on the server: sometimes parts go into the same machine, sometimes the answer is a replacement machine. Timing is agreed case by case. Tell us the change you need and we answer for your build.

Literally unmetered: no fair-use clause, no soft 95th-percentile, no rate-limit that appears at month-end. Line rate on a 1, 10, 25, 40 or 100 Gbps port, sustained around the clock. Saturate it every day of the month and the bill does not move. The port is yours alone. The uplink behind it is shared, sized for the servers on it, and when it gets close to full we add capacity rather than hold anyone back. (Terms, section 3.)

No quota. The practical limit is the speed of the port: a 1 Gbps port moves about 324 TB in a 30-day month at line rate. The port is yours alone. The uplink behind it is shared, sized for the servers on it, and when it gets close to full we add capacity rather than hold anyone back.

No, not as a product. We do not sell mitigation, we do not advertise an absorption figure, and we will not promise you an outcome for a given attack. What exists is filtering at the network edge and monitoring that pages a human. If your workload attracts attacks and you need guaranteed mitigation, tell us before you order: that is a fair reason for us not to be the right host, and hearing it on day zero beats finding out on the day it matters.

2 IPv4 addresses on every machine, plus IPv6, native, sized with you at deploy time. Additional IPv4 is $5 per address per month. Tell us how many you need and what they are for; addresses are a finite resource and we allocate them against a use, not a wish.

Yes, natively. No tunnels, configured at deploy time. Tell us the size you need and we will size the allocation with you.

Yes: port 25 is open by default, and reverse DNS (PTR) is set for your addresses on request. Send only mail people asked for, because the first spam complaint ends the service, with no warning first (section 4 of the terms). One spam run costs every other customer on the range their deliverability.

Data centres of Tier III and Tier IV design. In practice that means two power supplies in every server, redundant power to the rack, diesel generators on site as a rule, redundant cooling, as the Tier III and IV classes require, and controlled physical access, as the Tier III and IV classes require. The buildings are Equinix AM3 in Amsterdam, Kolo NL2 in Meppel, Anexia ANX85 in Manassas, phoenixNAP in Phoenix; their certifications, as each operator lists them, are on /network. We sign no uptime percentage.

Four today: Amsterdam and Meppel in the Netherlands, Manassas on the US East coast, Phoenix on the US West coast. Each location has its own set of builds in stock and its own prices, because bandwidth costs differ between data centres; the unmetered port is the same in all of them. Details on /network.

24/7, through a ticket in the panel. Network and hardware tickets reach a human who can read a traceroute. OS-level questions are out of scope by design: we will say so, and escalate to HostiServer if you want someone to do the work for you.

Yes: technicians on site in all four data centres, 24/7, weekends and holidays included. They do the physical work: power cycles when IPMI cannot reach the machine, disk, memory and power-supply swaps, cabling and cross-connects, a visual check of the machine and its lights. Failed hardware is ours to fix, at our cost; other physical work you ask for is priced per job: rates differ between data centres and change over time, so we quote before we start. Everything goes through a ticket, with a report afterwards, photos when useful, and anything found along the way is agreed with you before it is done. Emergencies are handled as fast as possible, often within hours; planned work usually takes 1 to 2 business days. That is practice, not an SLA.

We do not publish a percentage, because a number without a measurement method and a credit schedule is decoration. What we do run: redundant power and cooling in every facility, multiple independent uplinks, and monitoring that pages a human (section 10 of the terms).

Not one of ours, and there will not be. Invoices, renewals and account details live in the HostiServer panel. The parent brand already runs one, and a second half-built copy would serve nobody. The machine itself you run the way you would run any server you own: SSH, and IPMI when SSH is not enough. What we do not put in front of you is a panel that meters your traffic, because nothing meters it.

Monthly and in advance: each invoice covers the coming month and is paid in advance; a new one follows every month. Once an invoice is paid, you have the month. You have 4 days to pay it; if it is still unpaid after that, the server may be suspended, and the timeline that follows is in section 6 of the terms. Setup is $0, and tax, where it applies, is shown separately on the invoice.

No. Nothing on the invoice depends on how much you transfer.

Card (Visa or Mastercard), bank transfer or PayPal, and the account has to be in your own name. That is a compliance requirement, not a preference (section 5 of the terms). We do not take cryptocurrency.