So I decided to try building something I’d want to use. The whole stack is built custom from the ground up with no external dependencies or costs to third parties apart from hardware and IP space.
What Infuze is:
Raw, dedicated performance: 1 vCPU = 1 physical thread. No overcommit. I cap my nodes allocations at the physical hardware limit with some overhead.
Pricing based on what you use: It's set at $10/m for 4gb/1vcpu/50gb but can be provisioned for min 1hour(3 cents). Discounts on wallet top up's to prevent pressure to get unneeded resources(even the minimum top up starts at 10% discount so its actually $8+ a month goes down to $7.50 with larger top up's.
Runs on our own hardware(leased) and autonomous system: We operate our own Intel Xeon Platinum 8280 servers and BGP-routed IP space (AS211747).
KVM based with storage NVMe gen4 with ZFS
Stack:
It's built on mostly open source technology!
Proxmox for virtualization, Knot for master authorative and outsourced for anycast slaves, custom Go microservices for most of the automation needed by the frontend(open sourcing some of them soon!). FRR for BGP. Networking is standard bridged networking that's routed from leased IP space that I'm announcing with FRR. Mail using maddy. Prometheus/node exporter for metrics, grafana for panels. The LLM chatbot is using AnythingLLM with openrouter but that was mostly like a FOMO thing lol tbh I don't expect anyone to use it much(because i dont) but if it helps someone then that's great. Support/ticketing is custom, with the Next.js frontend, billing is Stripe. Each VM gets a public IPv4 and a /64 subnet routed to it, no NAT or SNAT.
If you guys have any questions or want to discuss more on the stack that I didn't mention I'm very open to sharing, discussing, and learning about new ways to optimize my stack. I'm still very new to all this and learning as I go along so any insight is appreciated! I'm working on something more experimental(custom firecracker fork that directly boots ELF+IVSHMEM apps from memory with a unikernel or initramfs), which I hope to bring to the public soon, but lacked funding to keep moving forward so I decided to start this as a learning experience and first venture into the industry, with a more mature stack that's reliable and battle tested enough for public use.
Who it's for:
Developers who prefer using linux with root access, via SSH, etc.
People who want to pay for something closer to real infra costs. Compute isn't expensive and the tech isn't difficult. We shouldn't be forced to pay an amount that a monopoly feels they deserve.
This isn't for those that engage in yaml-therapy or love contributing to the charitable foundation for wooden figureheads, but I've got something lined up for you guys too! ;)
This is the first public beta, and while most things are battle-tested, I expect a few bumps. I’ll be around all day to answer any questions, fix bugs quickly, and learn from the feedback.
For the benchmark nerds I spun up a quick little site for fun with v0 because I was finding endless things to tinker with and feed my impostor syndrome to delay launching this but I've dragged it long enough https://bench.infuze.cloud
You can get a free dollar voucher there and run a benchmark for fun, I wanted to do a larger amount but realized that my hourly billing is gonna be a magnet for abuse and being entirely self funded that's probably not a good idea, but I'm prepared to pivot fast(and strike back, to those even considering it -_-)
Thanks for reading, and I’d love to hear any feedback, ideas, and critique. Appreciate you all.
I would advise against that if possible, since the "reset" process for an already contaminated VM is much trickier than the "build-up" process for what one would think of as a template. That's actually why `docker build` exists when `docker save` already exists. I do recognize from your other comments that my mental model may not map onto your target audience, so my comments are always "for your consideration" and not wagging my finger at your choices
If you were to choose to go with "build up," there are already so many specifications for that template construction process you could choose any one of them that you think would work well for your audience: Containerfile[1], Dockerfile, Packer, AWS Image Builder, and probably hundreds of others
1: relevant: bootc-image-builder: Build your entire OS from a Containerfile - https://news.ycombinator.com/item?id=44367004 - June, 2025 (27 comments)