AxisNow Review: An Edge Platform That Doesn't Sell Bandwidth — Is It Worth Using?

Last year a friend of mine who runs a cross-border e-commerce business came to me. He said their site was getting hit, Cloudflare's free plan couldn't hold up, and he wanted high-defense protection without switching DNS. I recommended AxisNow to him at the time, and later I got an account myself to run tests. I've been using it ever since. How should I put it? At first glance it really is a bit confusing. The official site reads like technical documentation, and after browsing for ages you still can't tell what they're actually selling.

Then I figured it out. It's not a CDN. It doesn't sell bandwidth or nodes. What you're actually buying is its console. How traffic flows, which provider it goes through, when to switch — that's what it manages. But the traffic itself doesn't pass through it.

That logic sounds a bit convoluted, so let me give a real example. We have three sites: one on Cloudflare, one on Tencent EdgeOne, and one running on our own VPS in Japan. Previously these three were managed separately — certificates renewed individually, rules configured individually, and when Cloudflare got knocked out we had to switch DNS manually. After connecting them to AxisNow, the three edges became one list, and routing rules only needed to be written once. Health checks run every 30 seconds, and if an edge goes down it's automatically removed from DNS responses. The first time I saw it switch automatically, I stared at the dashboard for two minutes. It really does save you a lot of hassle.

The node deployment step was simpler than I expected. They provide a one-line script, and once it runs the node shows up in the console. But there's a catch: they recommend starting with 1GB of RAM. I tried it on a 512MB BandwagonHost box and it wouldn't come up. I switched to a 1GB one and it worked. If you have idle small VPSes lying around, don't be too stingy with the specs.

DNS scheduling is the core feature. Rules come in three types: Fixed, Failover, and Quality. Fixed means always going through one provider, Failover switches by priority, and Quality automatically picks the fastest. I use Failover for most of my sites, with Cloudflare as primary and EdgeOne as backup. I tried Quality mode for a while, but sometimes it would drift to less stable nodes, so I switched back. It might have to do with the distribution of health check points — I didn't dig into it.

On security, it comes with a WAF. I scanned my own test site with SQLMap and could see interception records in the logs, so it's definitely doing work. But if you're expecting it to withstand terabit-level DDoS, you're dreaming. The underlying scrubbing capacity depends on how much protection the edge you connect to has. AxisNow handles the scheduling layer. It doesn't take the bullet for you; it's responsible for pulling you behind someone else after one person gets hit.

The pricing is pretty clear. The commercial plan is $5 per month per domain, and the SDK one is $0.1 per active device. Traffic fees are separate — you pay whichever provider you connect to. The free plan gives you 100GB per month, 10 domains, and 1 day of log retention. I ran the free plan for a month at first, and only upgraded to commercial after exceeding the domain limit.

Some things really aren't there yet. Wildcard domains aren't supported — every subdomain has to be added individually. One of my sites has seven or eight subdomains, and configuring them was a pain. Root domains can't be onboarded with one click either; you have to point a CNAME manually. IPv6 origin support is incomplete. I asked them about it and they said it's in the works, but no timeline was given.

The documentation is so-so. Basics are covered, but for advanced parameters you're on your own. There's an official Telegram group with not many people in it, but questions do get answered. Once I asked about a routing rule at midnight and someone replied within ten minutes, which was a pleasant surprise.

I also ran into the issue where the main site and console login states aren't synced. The official explanation is that the main site is a static page without integration, so it doesn't affect usage, but the experience does feel a bit disjointed.

So who is this actually for? I think it's for teams that already have a bunch of edge resources but find managing them exhausting. Or if you need self-hosted nodes but don't want to write a scheduling system from scratch. Or if you have data sovereignty requirements — nodes must run on your own machines — but you still want a decent console. These types of people will find AxisNow worth it.

On the flip side, if you just have a small blog that doesn't even push 100GB a month, just use Cloudflare's free plan and save yourself the trouble. Pure overseas business doesn't need it either — multi-CDN scheduling doesn't mean much to you. And if you don't want to touch servers at all, definitely stay away. There's still a barrier to entry.

My feeling about AxisNow as a product is that it solves a real problem, but not everyone has that problem. If you're one of those people who's been through the wringer managing multiple CDNs, it'll make your life a lot easier. If you're not, it just looks like a somewhat complicated control panel.

That's about it.