An introduction to who we are, what we built, and why we built it differently. Behind the scenes of Fluxorus — our infrastructure, philosophy, and what's next.
We're Fluxorus Networks — a hosting provider focused on one thing: making high-performance infrastructure available to people who actually need it, without the markup or the marketing fluff.
This is the first post on our new blog. Before we get into product updates and engineering deep-dives, we want to take a moment to introduce ourselves properly: where we came from, what we built, and why we think hosting can be done better.
Fluxorus was founded in 2024 with a simple thesis: hosting infrastructure has been getting worse for the people who depend on it most. Bandwidth bills hidden behind dashboards. DDoS protection sold as an upsell instead of a baseline. "Unlimited" plans that throttle the moment you actually use them. Game server providers running on shared, oversubscribed VMs marketed as "bare metal."
We're a small team — three engineers, one mission. Every server we deploy, every filter rule we ship, every line of our scrubbing engine is built and operated by people who use what they sell. That's not a marketing tagline. It's how we work.
When we looked at the hosting market in 2024, three things stood out:
We don't claim to have solved every one of these. But we've built our company around fighting them.
Three things define how we run infrastructure:
Building a multi-terabit scrubbing network from scratch isn't realistic for a team our size — and it isn't necessary, either. Instead, we partnered with Cloudflare for the heavy lifting: anycast routing, global edge presence, and the raw capacity to absorb attacks that would saturate any single datacenter on the planet.
Attack traffic gets absorbed at Cloudflare's edge, far from our origin. What reaches us is already filtered down to a manageable volume — and that's where our own protocol-aware filtering takes over: deeper game-protocol inspection, A2S query caching for the Steam server browser, RakNet validation for Rust and Palworld, FiveM-specific filtering, and so on. Cloudflare handles the scale; we handle the specificity.
The result: 0.0% packet loss on clean traffic, sub-second mitigation activation, and game servers that stay listed on the Steam server browser even while under active attack.
Every plan ships with a defined bandwidth allowance — VPS plans include a transfer cap that scales with the tier, and dedicated servers include 50 TB of monthly transfer. If you need more, you can buy additional bandwidth at a flat, published rate — no surprise overages, no automatic billing spikes mid-month.
Additional IPv4 addresses are available as an add-on at a flat published rate, so you can scale beyond the included IP without surprise — but your base plan price never moves. What you won't find: hidden fees layered on top of the advertised price, or support-tier gates between you and a real engineer. DDoS protection is included on every plan because it's part of the network, not a SKU.
When we publish performance numbers, they're measured under load — not theoretical. Our VPS plans run on AMD Ryzen 9950X with NVMe Gen4/5 (or Intel Xeon with 12 Gbps SSD), and we publish actual p95 disk and network latency from production hardware. If a number on our pricing page sounds too good to be true, it's not — it's the floor, not the ceiling.
A quick look under the hood:
Why this matters: We don't pretend to operate a global scrubbing network ourselves — that's what Cloudflare does, and they do it better than we ever could. Our job is the layer above: building the protocol-aware filters, the A2S caching, and the game-server-specific tuning that generic mitigation can't deliver.
We're past the "early days" milestone but still very much in the build phase:
A few things we're working on for the next quarter:
Subscribe to our RSS feed if you want to be the first to know when those drop.
This isn't documentation. For "how do I…?" questions, our Knowledge Base is the right place — it's where we keep step-by-step guides, troubleshooting, and reference docs.
The blog is for the rest: announcements, engineering posts, network changes, and the occasional opinion on how hosting should work. We'll publish when we have something genuinely useful to say — not on a schedule, not for SEO bait. If you read a post here, it's because we believed it was worth your time.
Thanks for reading. If you want to give us a try, our VPS plans start at honest prices with DDoS protection included, and our dedicated servers are spec'd for workloads that actually need bare metal. If you have questions, our team reads every email at hello@fluxorus.com.
— The Fluxorus Team
