
Alexhost is a Moldova-based hosting provider that has run its own data center since 2008, covering shared hosting, VPS, dedicated servers, and GPU hosting.
I put its dedicated server line through checkout, benchmarking, and three support channels to see if the ISO 27001 certification and 99.99% uptime claim show up in how the service actually runs. Keep reading for where AlexHost delivered and where I’d tell you to slow down before ordering.

Every score below follows HostAdvice’s rating methodology, which weighs pricing transparency, feature depth, tested performance, ease of use, and support quality rather than marketing claims. Here’s how AlexHost scored based on everything covered in this review.
| Parameter | Score | Why This Score |
|---|---|---|
| Prices | 9.0/10 | Rates are competitive for the hardware tier tested, and the checkout cart updates live so you always see the running total.. |
| Features | 9.0/10 | A broad lineup spanning shared hosting, VPS, dedicated servers, GPU hosting, and colocation, backed by ISO 27001 and ISO 9001 certification. IPAM tooling and six-plus cryptocurrency payment options go beyond what most hosts in this price range offer. |
| Performance | 8.8/10 | CPU scaling, memory throughput, and disk I/O all matched or beat what the spec sheet promised, and stress testing ran three full workloads with zero failures. The one miss was bandwidth, which landed around a third of the advertised 1 Gbps shared tier. |
| Ease of Use | 8.7/10 | Checkout condenses a full dedicated server configuration into one scrolling page, a genuine time-saver. Points came off for a RAID 0 default with no redundancy warning and a dashboard that doesn’t surface server status until you dig for it. |
| Support | 9.0/10 | Both the ticket system and live chat returned answers in under five minutes, and the ticket form’s encryption option and per-server routing stood out. The knowledge base is where this loses ground, thin coverage and at least one article that didn’t match my actual experience. |
| Overall | 8.9/10 | AlexHost delivers strong hardware performance and a fast, well-built ordering process backed by real certifications. The deductions come from RAID 0, bandwidth, dashboard visibility, that reward an experienced buyer more than a first-time one. |
AlexHost sells five hosting categories: shared/SSD virtual hosting, VPS, dedicated servers, GPU hosting, and colocation in Moldova.
See the exact pricing below. But beyond the numbers, here’s what matters: what AlexHost’s refund policy actually covers, which payment methods you can use, and where the fine print changes what you’ll pay.
| Plan Name | Space | Bandwidth | OS | Panel | Number of Sites | Price | |
|---|---|---|---|---|---|---|---|
| PROMO Basic Hosting | 1 GB | Unlimited | cPanel | 5 | CA$1.24 | Details | |
| PROMO Expert Hosting | 10 GB | Unlimited | cPanel | Unlimited | CA$9.37 | Details |
| Plan Name | Space | CPU | RAM | OS | Price | |
|---|---|---|---|---|---|---|
| Intel® Core™ i5-4570 Processor | 1000 GB | 4 x 3.6GHz | 4 GB | CA$62.71 | Details | |
| 2x Intel® Xeon® E5-2699 v3 | 1000 GB | 36 x 3.6GHz | 31.25 GB | CA$239.58 | Details | |
| Ryzen™ 9 3950X | 1000 GB | 16 x 4.7GHz | 62.5 GB | CA$319.98 | Details | |
| AMD EPYC 7642 | 4 TB | 48 x 3.3GHz | 250 GB | CA$803.96 | Details |
Money-back guarantee:
Dedicated server cancellation fees:
| Fee | Amount |
|---|---|
| Installation fee | 5 EUR flat |
| Cancellation processing fee | 30% of total paid |
| Third-party licenses | Non-refundable |
On a 100 EUR dedicated server order, that works out to roughly 65 EUR returned after both deductions.
Crypto refunds:
AlexHost may also request a government-issued Passport ID before releasing a refund, a fraud-prevention step tied to its anti-money-laundering obligations. Declining to provide it means the refund request gets denied, with no exceptions made.
Payment methods:
One thing to flag before you check out: the homepage promotes a 15% discount code for hosting plans, but the refund policy explicitly excludes promotional code orders from any refund.
If you want to keep the safety net of the 30-day guarantee, weigh that against what the code saves you. Switching to annual billing drops your rate separately, by up to 15%, and the 4% card fee shows up as its own line at checkout rather than being folded into the sticker price.

AlexHost’s dedicated server lineup runs from a 26 EUR single-core Pentium to a 500 EUR AMD EPYC 7642, so before any numbers, it matters to say exactly what generated the results below. I provisioned the 2x Intel Xeon E5-2690 v4 (28 cores, 56 threads, 64GB DDR4 ECC, RAID 0, Debian 12) in AlexHost’s Moldova data center for 180 EUR a month.
If you’re eyeing the entry-level Pentium or the top-tier EPYC, treat these numbers as a picture of what this specific mid-tier hardware class delivers, not a blanket score for every plan AlexHost sells.

Test setup:
| Component | Spec |
|---|---|
| CPU | 2x Intel Xeon E5-2690 v4, 28 cores / 56 threads |
| RAM | 64GB DDR4 ECC (62GiB usable, the small gap is standard reserved memory, not a shortfall) |
| Storage | 936GB available on a RAID 0 array |
| OS | Debian 12 (bookworm), kernel 6.1.0 |
| Location | Moldova (Chisinau) |
| Bandwidth ordered | 1 Gbps shared |
| Price | 180 EUR/month |
I ran the same benchmark suite you’d expect on any serious server review: sysbench for CPU and memory, fio for disk I/O, Ookla for network, and stress-ng to see how the box handles sustained load rather than a quick burst.
CPU tests come in two flavors because they answer two different questions. Single-thread performance tells you how the server handles work that can’t be split across cores, a single PHP request, a script running in sequence.
Multi-thread performance tells you how it handles parallel workloads: batch processing, video encoding, or anything that can spread across many cores at once.
| Test | Result |
|---|---|
| Single-thread (prime limit 20,000) | 401.17 events/sec |
| Multi-thread (56 threads) | 16,816.28 events/sec |


The multi-thread number scales close to linearly against the single-thread baseline given 56 threads are in play.
That matters more than the raw figure does, because a server that doesn’t scale cleanly across cores under a multi-thread test is often a sign of a shared or oversold CPU pretending to offer dedicated cores. This one scaled the way dedicated hardware should.
Thread fairness also showed a low standard deviation across the 56 threads (128.19 against an average of 3004.34 events per thread), meaning no single thread was starved while others hogged cycles. If you’re running anything that spreads work evenly across cores, like a compile job or a parallel data pipeline, that consistency is what keeps individual tasks from lagging behind the rest.
Memory speed matters most for anything that leans on RAM for speed rather than disk, database buffer pools, in-memory caches like Redis, or applications juggling large datasets in memory.
| Test | Result |
|---|---|
| Sequential write | 5,790.65 MiB/sec |
| Sequential read | 7,255.88 MiB/sec |
Both numbers land where I’d expect dedicated DDR4 ECC memory to land, comfortably ahead of what you’d see on a virtualized or shared-memory VPS plan. If your workload is database-heavy, this is the number that tells you queries hitting RAM instead of disk will move fast.

This is where the RAID 0 default from the Ease of Use section shows up directly in the numbers, so it’s worth reading this test alongside that earlier flag rather than in isolation.
| Test | Result |
|---|---|
| Sequential write (1GB) | 1,145 MiB/s (1,201 MB/s) |
| Sequential read (1GB) | 1,771 MiB/s (1,857 MB/s) |
| Random 4K mixed read/write | ~32,200 IOPS read, ~32,200 IOPS write, 126 MiB/s each |

Sequential speeds here are strong, and RAID 0 is a direct part of why: striping data across drives is what pushes sequential throughput up.
Random 4K performance, the number that matters most for database workloads and anything doing lots of small file operations, also held up at over 32,000 IOPS in both directions.
The trade-off I flagged earlier stands here too. You get fast storage on paper, but zero redundancy behind it. If a drive in that array fails, everything on it goes with it. These numbers explain why AlexHost defaults to RAID 0 (it makes the storage benchmarks look good), but speed and safety are pulling in opposite directions here, and the default configuration picks speed.
I ran the Ookla speedtest CLI twice, against different servers, to check for consistency and confirm there wasn’t a fluke result skewing the numbers.
| Run | Server | Download | Upload | Packet Loss |
|---|---|---|---|---|
| 1 | IP HOST Data Center, Chisinau | 285.93 Mbps | 285.97 Mbps | 0.0% |
| 2 | Moldtelecom 100G, Chisinau | 286.09 Mbps | 285.92 Mbps | 0.0% |


Zero packet loss on both runs is a clean result, and the near-identical numbers between two different test servers rule out a one-off fluke. That consistency is the good news.
Here’s the part that needs a direct call-out: I ordered 1 Gbps shared bandwidth, and both runs landed at roughly 286 Mbps, under a third of that figure. Idle latency was excellent (0.50ms and 0.51ms), so this isn’t a routing or distance problem.
It’s most likely the “shared” part of “1 Gbps shared” doing exactly what shared bandwidth does, capping throughput well below the port’s rated ceiling during contention with other tenants on the same uplink.
Whatever the cause, if you’re ordering this bandwidth tier expecting to regularly see numbers close to 1 Gbps, plan around what I measured instead of the number on the order page.
Short benchmarks show peak capability. A sustained stress test shows whether a server holds that capability or starts throttling, erroring out, or degrading once it’s been under load for a while, closer to what a production server actually experiences over hours or days rather than a ten-second burst.
I ran three 180-second stress-ng workloads: CPU (all 56 threads), memory (2 VM workers at 75% RAM), and disk (2 HDD workers).
| Stressor | Bogo ops | Runtime | Result |
|---|---|---|---|
| CPU | 9,553,187 | 180.11s | Completed cleanly |
| Memory | 11,328,884 | 184.57s | Completed cleanly |
| Disk | 1,048,576 | 184.65s | Completed cleanly, 5,939 MB/sec read / 1,461 MB/sec write |

All three stressors ran their full duration with no failures and no flagged untrustworthy metrics. That “zero failures, clean completion across all three” result matters more than any single bogo-ops figure, since it’s the difference between a server that performs well in a quick test and one that holds up once you actually push it for an extended stretch.
This E5-2690 v4 configuration delivers on most of what its spec sheet promises. CPU scaling across 56 threads is clean, memory throughput is fast, disk performance benefits visibly from the RAID 0 default, and the server ran three separate 180-second stress tests without a single failure.
The one number that doesn’t match the order page is bandwidth: 1 Gbps shared advertised, roughly 286 Mbps delivered with zero packet loss across two separate test runs.
If raw CPU, memory, and disk speed are what you’re buying a dedicated server for, this tier holds up under real testing. If your workload depends on hitting close to that advertised 1 Gbps figure, factor in what I actually measured before you order.

When a hosting provider sells dedicated servers rather than shared plans or VPS instances, the stakes for a smooth ordering process go up. You’re choosing hardware, RAM, storage layout, and network specs for a physical machine, not clicking through a handful of shared hosting tiers.
I wanted to see whether AlexHost matched that complexity with a checkout flow that kept me oriented, whether creating an account added friction on top of an already detailed order, and whether the dashboard I landed in afterward made it clear what I had just bought and how to look after it.
I started on the AlexHost homepage and scrolled down to the server selection area rather than being pushed through a signup form first, which let me price things out before committing to anything.

I filtered the dedicated server list to the mid tier price range (90 to 195 EUR) and a 1 Gbps shared network, and settled on the 2x Intel Xeon E5-2690 v4, marked as the customer favorite, with 28 cores, 56 threads, DDR4 RAM, and SSD storage for 180 EUR a month.

Clicking that plan took me into a single, long configuration page rather than a multi-step wizard. Here’s what it asked me to set:
| Setting | What I chose |
|---|---|
| Operating system | I went with Debian 12 |
| Control panel | None |
| RAM | 64GB DDR4 ECC |
| Drives (up to 8 slots) | One 2.5″ SSD 1TB, seven left at None |
| RAID level | RAID 0 (pre-selected default) |
| Bandwidth | 1 Gbps shared, unmetered |
| Additional IPv4/IPv6 | Optional, priced per address |
| Remote console | IPKVM via HPE iLO 4 (paid add-on) |
| Additional GPU | Optional |

The cart total updated live as I moved through each choice, so there was no surprise jump at the final screen.
Two things about how those choices are presented say more about who AlexHost expects to be buying than the feature list alone does:
Dedicated servers work differently on the provisioning side. My server showed as Active immediately, a result of the review account setup rather than the standard process. For a normal order, AlexHost provisions dedicated hardware manually, typically within 3 to 6 hours and up to 24 hours in slower cases, since it involves physically configuring components, installing the OS, and activating the network port.
That’s a reasonable window for physical hardware, but if you’re used to a VPS going live in seconds, set your expectations accordingly for a dedicated server.

What I thought: The single-page checkout is faster than most dedicated server providers manage, and the live cart total removes guesswork. But the RAID 0 default and the unverified checkout are details that reward someone who already knows what they’re doing and can work against someone who doesn’t. If you’re new to dedicated hardware, change the RAID setting before you check out and don’t assume the default configuration is the safe one.
After the order confirmation, I landed on a “Welcome” screen with three shortcut cards (Place New Order, Client Area, Support) and a banner asking me to double-check my account details. That banner stayed pinned above the content on every page I visited afterward rather than clearing once I’d seen it.

Clicking Dashboard in the sidebar took me to a different, more useful screen than the welcome page suggested was coming.
Here’s what it showed:
| Section | What it displays |
|---|---|
| Summary counters | Total services, Active, Pending |
| My services | A card per service: status badge, location, hostname, price, billing cycle, expiry date |
| Search and sort | Search bar plus a sort dropdown (default: Expiry soonest) |
| Filter tabs | Service type (Dedicated Servers, and presumably others once you have them) |
My one server showed up as an ACTIVE card labeled Moldova, with the auto-generated hostname (server2690v4-139-ax), price, and a dash under Expiry since the account is on a free test cycle.
One more flag here is that Active status appeared right away because of how my review account was provisioned, not because dedicated servers activate instantly for a standard order. Budget for AlexHost’s usual 3 to 6 hour window instead.

The sidebar itself carries the full account menu: Dashboard, Services, Account details, Manage contacts, Billing, Affiliates, Security, History, Knowledge base, Support Tickets, Live Chat, Server status, and IPAM.
Having IPAM (IP address management) as its own item is a detail aimed more at someone running several servers than a single-site buyer.
What stood out is the gap between the two screens. The welcome page you’re dropped on right after checkout tells you nothing about your new server, but the actual Dashboard, one click away in the sidebar, answers exactly the question you’d have at that point: is my server active, and where is it.
That’s the right information in the wrong place. A new customer who doesn’t click Dashboard first could sit on the welcome screen wondering if the order went through, when the confirmation was there the whole time.
What I thought: Once you find it, the Dashboard does its job well. The service card format is easy to scan, the counters give you an at-a-glance status check, and search plus sort will matter once an account has more than one server. My complaint isn’t with the Dashboard itself, it’s that AlexHost doesn’t land you there first. If this were the default screen after login and after checkout, the “where’s my server” question I raised earlier wouldn’t come up at all.
Lastly, I wanted to see what happens once a server is live and you need to check on it, rename it, or change how it renews, since that’s the part of any hosting panel that gets used the most after the first purchase.

I clicked into Services, then Dedicated Servers, then Moldova, and found my server listed with its ID, status, price, billing cycle, and expiry date.

Opening it took me to a Service Details page with a sidebar offering:

The main panel showed the domain as server2690v4-139-ax rather than the hostname I had typed during checkout.
If you order more than one server, that auto-generated label is what shows up across your account, not the name you chose, so keeping track of which machine is which comes down to remembering an ID rather than a name you picked for a reason.
| What’s on the Service Details page | What isn’t |
|---|---|
| Domain/label, registration date | Server’s IP address |
| First payment amount, billing cycle | Login credentials |
| Auto-renew toggle | Power/reboot controls |
How I found it: The sidebar covers what a dedicated server owner actually needs (renewal control, relabeling, diagnostics, reinstall, IP handling), so nothing important is missing from the panel as a whole. The problem is what’s absent from the first screen you land on. No IP address, no credentials, and a label that isn’t the one you picked means the page named Service Details tells you less than its name suggests.
AlexHost gets you through checkout faster than most providers I’ve tested, and the single-page setup with a live-updating cart is a genuine convenience. Actual server delivery follows AlexHost’s standard manual provisioning window (typically 3 to 6 hours, up to 24), not the instant activation my review account saw.
Speed at checkout comes with trade-offs a newer buyer might not catch: a RAID 0 default with no redundancy, no identity verification before your card is charged, and a dashboard and server panel that tell you less about your live machine than you’d expect once it’s ready.
If you know your way around server hardware and just want an efficient ordering process, this works in your favor. If you’re buying your first dedicated server, slow down at checkout, budget for the provisioning window, and expect to dig through a few sub-menus before you get a full picture of what you own.

A dedicated server is the kind of purchase where you eventually need to call in a favor, whether that’s a RAID question, a kernel module, or a server that won’t boot.
So I wanted to see not just how fast AlexHost answers, but whether the process of actually reaching them, and the answers themselves, hold up under a real technical question. AlexHost offers three support channels: a ticket system, live chat, and a knowledge base. I went through all three, start to finish.
Opening a ticket takes one click, a red “Open Ticket” button sits permanently in the top navigation bar regardless of which page you’re on.

That single-click access from anywhere in the account is a small thing that saves you from hunting through a sidebar menu when something’s actually gone wrong.
The form itself asks for more than most ticket systems bother with:
| Field | What it does | What I chose |
|---|---|---|
| Department | Routes the ticket internally | Support Department (the only relevant option) |
| Priority | Sets urgency | High |
| Priority (second field) | A second, grayed-out “Priority” dropdown defaulted to Low | Left untouched, it wouldn’t accept input |
| Subject | Ticket title | Custom kernel module support on dedicated server |
| Message | Free text, with a live 360-character display as you type | My kernel question |
| Related service | Ties the ticket to a specific server on your account | Moldova – 2x Intel Xeon E5-2690 |
| CC recipients | Comma-separated list of additional emails to loop in | Left blank |
| Sensitive data checkbox | Encrypts the ticket’s contents | Not checked for this test |

A few of these deserve more attention than a quick glance gives them.
The duplicate Priority field is the kind of detail a reviewer notices and a first-time customer might not. There are two dropdowns both labeled “Priority,” one set to High and editable, the other grayed out and stuck on Low. It reads like a leftover from a form update that wasn’t fully cleaned up. It didn’t stop me from submitting the ticket, but it’s the sort of visible rough edge that makes you wonder what else in the account panel hasn’t been fully tidied.
The Related Service dropdown is a genuinely useful piece of design once you have more than one server on the account.
Instead of describing which machine you’re asking about in the message body, you tie the ticket directly to it, and presumably the agent sees your plan, specs, and history for that specific service before they even reply. For a provider selling dedicated hardware, where two customers’ “my server won’t boot” tickets could mean completely different physical machines, that’s a sensible piece of routing to have.
The encryption checkbox is the standout feature here, and it’s not something I’ve seen offered by name in most hosting providers’ ticket systems.
Checking “This message contains sensitive data, encrypt its contents” tells you AlexHost has built a specific path for tickets involving credentials, IP details, or anything else you wouldn’t want sitting in plaintext in a support queue.

I didn’t need it for a kernel question, but if you’re ever submitting a ticket with a password reset request or server access details, this is the box to check, and its presence at all says something about how AlexHost thinks about ticket security compared to competitors who don’t offer it.
The file attachment section supports up to 10 files, and the list of allowed extensions is worth a second look: .gif, .zip, .png, .jpeg, .txt, .mp4, .jpg, .pdf, .csv, .mov, and .conf. That last one, .conf, is a small but telling inclusion.
Config files are exactly what a sysadmin dealing with a server issue would want to attach, and a lot of generic support systems restrict uploads to images and documents. Allowing .conf directly suggests this ticket form was built with technical users in mind, not just billing complaints.
And before you even submit, the form tells you what to expect: “Usually replied within 2 hours.” That’s a specific, visible SLA-style promise sitting right on the page, not buried in a terms page somewhere.
I filed my kernel question with these settings and got a reply from Nicolai Russu in about five minutes, well inside that two-hour window.
The answer confirmed the server is fully under my control with no restrictions, then added that loading a custom kernel requires purchasing IPKVM separately at 10 EUR a month, since that’s what provides the console access needed to install one.

That’s a real answer, but a partial one. My question asked about the process for loading a module, and the reply told me what to buy rather than what to do once I had it.
It also skipped the bare-metal-versus-VPS distinction I’d specifically raised. What it did do, whether intentionally or not, is surface a genuinely useful piece of information: the base dedicated server plan doesn’t include the console access you’d need for kernel-level work, and that’s a 10 EUR/month add-on you’d only discover by asking.
What I thought: The ticket form itself is more thoughtfully built than I expected from a budget dedicated server provider, the related-service linking, the encryption option, and the .conf-friendly upload list all point to a system designed around actual sysadmin workflows rather than generic customer support. The reply speed backed that up.
Where it fell short was depth: a five-minute answer that solves half your question is still a five-minute answer, and the leftover duplicate Priority field is a rough edge on an otherwise well-considered form.
Live Chat sits in the same sidebar menu as Support Tickets, one click below it.

Clicking it opens what looks, at first glance, like a real chat window, it appears as a separate pop-up with its own title bar reading “Please leave message – ALEXHOST Web Hostin…,” complete with minimize, expand, and close controls, and even a browser-style address bar showing the underlying URL (bill.alexhost.com/hbchat/leavemessage/).

The form inside asks for:
I typed my RAID 0 to RAID 1 question, hit Send Email, and got an immediate on-screen confirmation: “Thank you for leaving message, we will get back to you as soon as possible.” No agent joined, no typing indicator appeared, and no back-and-forth followed in that window.
This is the detail that matters most about this channel, and it’s easy to miss if you’re moving quickly: despite the chat-style presentation, “Live Chat” here does not create a live conversation.
Instead, it files your question as a support ticket, labeled “Live chat question [date],” and it shows up in the exact same Support Tickets list as everything you submit through the ticket form.

The only way to find your answer is to leave the chat pop-up entirely and check Support Tickets.
| Ticket support | “Live Chat” | |
|---|---|---|
| Entry point | Open Ticket button | Live Chat sidebar link |
| Interface | Full ticket form on the page | Pop-up window styled like a chat widget |
| Where the answer appears | Support Tickets page | Also the Support Tickets page |
| Real-time back-and-forth | No | No |
| Response time (this test) | ~5 minutes | ~3 minutes |
The reply, from Gleb Cociurov, arrived in about three minutes, faster than the ticket, and opened with “Thank you for waiting,” an odd line given the short turnaround and a small sign the response may lean on a saved template rather than being composed fresh. The substance was solid regardless: switching from RAID 0 to RAID 1 wipes all existing data, back up first, then contact support again to perform the actual rebuild.

What I thought: Presenting this channel as “Live Chat,” complete with a chat-window skin and an address bar, sets an expectation AlexHost doesn’t deliver on. If you go in expecting to type a question and watch a real-time reply come back in the same window, you’ll be sitting in front of a static confirmation message instead.
The answer itself was fast and accurate, arguably the best response I got across all three channels, but the packaging oversells what’s actually a slightly quicker ticket form with a different name.
The Knowledge Base sits lower in the sidebar under Help, and opens to a search bar plus eight category tiles: SSD Virtual Hosting, Operating Systems, Dedicated Servers, Colocation, FAQ, VPS, DNS, and Articles.

Each tile shows an article count, and those counts tell their own story:
| Category | Articles |
|---|---|
| FAQ | 5 |
| VPS | 5 |
| SSD Virtual Hosting | 3 |
| Dedicated Servers | 3 |
| Articles | 2 |
| DNS | 1 |
| Operating Systems | 1 |
| Colocation | 0 (nothing to display) |
That’s around 20 articles across the entire knowledge base, and Colocation having zero content despite appearing as a full category tile is a strange choice, either pull the category or populate it, since an empty section with its own icon and “View All” link just advertises a gap.
I navigated into Dedicated Servers, which breadcrumbs cleanly (Knowledge Base > Dedicated Servers), and found three articles: a money-back policy, a “Forbidden – Dedicated Servers” entry, and one on install times.

I opened the install-time article specifically to judge quality rather than just counting headings. It carried a “1 min read” tag and a view counter showing 11,095 visits, with a 38-like to 14-dislike ratio sitting below it. The content itself read:
“Processing of orders for dedicated servers is done manually, which can take up to 24 hours. This is due to factors such as: configuring the components of the server depending on the order, checking and installing the OS.”

Two sentences for a topic with over 11,000 views is thin, there’s room to explain what “configuring the components” and “checking and installing the OS” actually involve rather than just naming the steps.
On accuracy though, this article holds up. AlexHost’s standard dedicated server delivery does run on a manual provisioning process, typically 3 to 6 hours and up to 24 in slower cases, which matches what’s written here. My own server showed Active immediately only because of how my review account was set up, not because that reflects a normal order.
Below the article, a “Still have questions?” prompt offered a direct Open a Ticket button, which at least closes the loop when the article itself falls short.
What I thought: The category structure and breadcrumb navigation are clean, and article pages carry genuinely useful signals, read time, view counts, a like/dislike ratio, that most knowledge bases skip. The actual content is sparse across the board, though. The one Dedicated Servers article I checked in depth turned out accurate, a fairer result than my first read gave it, but at two sentences for over 11,000 views, there’s a clear gap between how much traffic this content gets and how much it actually explains.
AlexHost’s support moves fast, both the ticket and the live chat came back in under five minutes, and the ticket form itself is more capable than most budget providers offer, with per-server routing, message encryption, and a config-file-friendly upload list that all point to a system built for technical customers.
The knowledge base is thin enough that its one article most relevant to this review contradicted what I actually experienced at checkout.
If you need a quick, correct answer to a narrow technical question, AlexHost delivers reliably. If you’re counting on real-time chat or a self-service library to solve most things without opening a ticket, plan to open that ticket anyway.

Yes, with a couple of conditions attached. AlexHost’s checkout is faster than most dedicated server providers I’ve tested, the hardware performed close to its listed specs in every benchmark except bandwidth, and support answered a technical ticket in under five minutes with a correct, if incomplete, answer. Just don’t expect the server itself to be ready the moment you pay, standard provisioning runs 3 to 6 hours and up to 24.
This host fits you best if you already know how to configure a server, you’re comfortable changing a RAID default before it costs you data, and you want EU-based, ISO-certified infrastructure without paying for a fully managed experience. If you’re ordering your first dedicated server and want a provider to catch your mistakes for you, or you need guaranteed full-speed bandwidth on a shared network tier, look closer at the fine print before you commit.
Either way, read the refund fee structure before you buy. A 30% cancellation fee on a dedicated server changes the math on “just try it and see.”
| Plan Name | Space | Bandwidth | OS | Panel | Number of Sites | Price | |
|---|---|---|---|---|---|---|---|
| PROMO Basic Hosting | 1 GB | Unlimited | cPanel | 5 | CA$1.24 | Details | |
| PROMO Expert Hosting | 10 GB | Unlimited | cPanel | Unlimited | CA$9.37 | Details |
| Plan Name | Space | CPU | RAM | OS | Price | |
|---|---|---|---|---|---|---|
| Intel® Core™ i5-4570 Processor | 1000 GB | 4 x 3.6GHz | 4 GB | CA$62.71 | Details | |
| 2x Intel® Xeon® E5-2699 v3 | 1000 GB | 36 x 3.6GHz | 31.25 GB | CA$239.58 | Details | |
| Ryzen™ 9 3950X | 1000 GB | 16 x 4.7GHz | 62.5 GB | CA$319.98 | Details | |
| AMD EPYC 7642 | 4 TB | 48 x 3.3GHz | 250 GB | CA$803.96 | Details |
| Plan Name | Warranty | Price | |
|---|---|---|---|
| Comodo PositiveSSL | CA$0.00 | CA$20.89 | Details |
| RapidSSL Certificate | CA$0.00 | CA$24.81 | Details |
| Thawte SSL Web Server with EV | CA$0.00 | CA$360.45 | Details |
| Comodo PositiveSSL Multi Domain Wildcard | CA$0.00 | CA$393.54 | Details |
| Plan Name | Warranty | Price | |
|---|---|---|---|
| PROMO Basic Hosting | CA$0.00 | CA$1.24 | Details |
| PROMO Expert Hosting | CA$0.00 | CA$9.37 | Details |
| Plan Name | Space | CPU | Bandwidth | Panel | Warranty | Price | |
|---|---|---|---|---|---|---|---|
| PROMO Basic Hosting | 1 GB | - | Unlimited | CA$0.00 | CA$1.24 | Details | |
| PROMO Advanced Hosting | 5 GB | - | Unlimited | CA$0.00 | CA$4.02 | Details | |
| PROMO Expert Hosting | 10 GB | - | Unlimited | CA$0.00 | CA$9.37 | Details | |
| PROMO Super Hosting | 20 GB | - | Unlimited | CA$0.00 | CA$12.49 | Details |
| Plan Name | Space | RAM | Bandwidth | Warranty | Number of Sites | Price | |
|---|---|---|---|---|---|---|---|
| PROMO Basic Hosting | 1 GB | Unlimited | CA$0.00 | 5 | CA$1.24 | Details | |
| PROMO Advanced Hosting | 5 GB | Unlimited | CA$0.00 | 20 | CA$4.02 | Details | |
| PROMO Expert Hosting | 10 GB | Unlimited | CA$0.00 | Unlimited | CA$9.37 | Details | |
| PROMO Super Hosting | 20 GB | Unlimited | CA$0.00 | Unlimited | CA$12.49 | Details |
| Plan Name | Space | Warranty | Price | |
|---|---|---|---|---|
| PROMO Basic Hosting | 1 GB | CA$0.00 | CA$1.24 | Details |
| PROMO Advanced Hosting | 5 GB | CA$0.00 | CA$4.02 | Details |
| PROMO Expert Hosting | 10 GB | CA$0.00 | CA$9.37 | Details |
| Plan Name | Space | CPU | RAM | Bandwidth | Warranty | Price | |
|---|---|---|---|---|---|---|---|
| M1 | 10 GB | 1 core | 1 GB | Unlimited | CA$0.00 | CA$16.08 | Details |
| M2 | 25 GB | 1 core | 1 GB | Unlimited | CA$0.00 | CA$32.16 | Details |
| M3 | 40 GB | 2 cores | 1 GB | Unlimited | CA$0.00 | CA$48.24 | Details |
| M4 | 60 GB | 4 cores | 4 GB | Unlimited | CA$0.00 | CA$64.32 | Details |
| M5 | 100 GB | 6 cores | 6 GB | Unlimited | CA$0.00 | CA$88.44 | Details |
| M6 | 150 GB | 8 cores | 8 GB | Unlimited | CA$0.00 | CA$112.55 | Details |
| Plan Name | Space | CPU | RAM | OS | Panel | Warranty | Price | |
|---|---|---|---|---|---|---|---|---|
| M1 | 10 GB | 1 core | 1 GB | CA$0.00 | CA$16.08 | Details | ||
| M2 | 25 GB | 1 core | 1 GB | CA$0.00 | CA$32.16 | Details | ||
| M3 | 40 GB | 2 cores | 1 GB | CA$0.00 | CA$48.24 | Details | ||
| M4 | 60 GB | 4 cores | 4 GB | CA$0.00 | CA$64.32 | Details | ||
| M5 | 100 GB | 6 cores | 6 GB | CA$0.00 | CA$88.44 | Details | ||
| M6 | 150 GB | 8 cores | 8 GB | CA$0.00 | CA$112.55 | Details |
AlexHost operates its own data center in Chisinau, Moldova, and this is where the dedicated server tested for this review was provisioned. The company has run this infrastructure since 2008.
Yes, a 30-day money-back guarantee applies to first-time purchases of shared hosting, VPS, and dedicated servers. Dedicated server cancellations carry a 5 EUR installation fee plus a 30% processing deduction, and orders placed with a promo code aren’t eligible for a refund at all.
AlexHost accepts credit and debit cards, PayPal, Webmoney, Ukrainian bank cards, and cryptocurrencies including Bitcoin and USDT TRC20. Card payments carry a 4% processing fee, and crypto refunds have their own minimums and fees depending on the currency used.
Both the ticket system and live chat returned answers in under five minutes during testing, faster than many budget hosting providers. The live chat channel doesn’t function as real-time chat though, it files your message as a support ticket, so expect a ticket-style wait rather than an instant back-and-forth.

Answer a few simple questions and find the perfect solution for you!
Start Hosting Search





