Live data from Hacker News

Show HN: I built a cloud on my own ASN w real 1:1 compute to fight the cartels

infuze.cloud

11–15 of 15 posts

Re: Show HN: I built a cloud on my own ASN w real 1:1 compute to fight the cartels

#11
post #4

Related to the API part, I was browsing and noticed that https://infuze.cloud/docs/api#/Virtual%20Machines/post_vms references templateVMID but https://infuze.cloud/docs/api#/Templates/get_templates shows only "get" so is the template just for quick-start scenarios or users could [eventually] create their own?

Great question. Currently, the templates are pre-configured by us for quick-start scenarios (e.g., Ubuntu 24.04, AlmaLinux, etc.). The API allows you to list these and use them to launch a new VM. The ability for users to create their own custom templates (i.e., take a snapshot of a configured VM and use it as a base image for future deployments) is very high on our roadmap. It's the logical next step after implementing cloud-init support. We see that as a critical feature for building scalable, repeatable infrastructure. So, to answer directly: not yet, but soon.

Re: Show HN: I built a cloud on my own ASN w real 1:1 compute to fight the cartels

#12
post #3

Because I have been curious about this for so long, and you said "It's built on mostly open source technology" I figured now's my chance to ask: Why roll your own control plane when OpenStack ships with so many batteries included, and (arguably important) doesn't require someone making a vanity SDK to interact with your vanity cloud?

This is a fantastic and fundamental question. We evaluated OpenStack, and it's an incredibly powerful and comprehensive project. For us, it came down to two things: complexity and opinionation. Complexity: OpenStack is a massive suite of services designed to do everything for everyone. We needed to do one thing exceptionally well: provide high-performance, dedicated-core VMs with a dead-simple control plane. The operational overhead of running a full OpenStack cluster felt like using a sledgehammer to crack a nut for our specific, focused use case. Opinionation: We have very strong opinions about how the user experience should feel (e.g., the simple slider for scaling, the transparent pricing unit). Building our own control plane allowed us to bake those opinions directly into the product from the ground up, without fighting the "OpenStack way" of doing things. It let us focus obsessively on the user-facing API and CLI experience. It was definitely a harder path in the short term, but it's given us the freedom to build exactly the lean, fast, and user-friendly platform we envisioned.

Re: Show HN: I built a cloud on my own ASN w real 1:1 compute to fight the cartels

#13
post #6

Why not have a non-cartel non-third-party payment method, too? Please support Bitcoin/Monero payments.

You read our minds. We agree that offering non-traditional payment methods is important. We just finished integrating support for cryptocurrency payments. Still having issues with a lot of coins but most of the common ones are there and XMR works fine just tested it, BTC as well.

Re: Show HN: I built a cloud on my own ASN w real 1:1 compute to fight the cartels

#14
post #4

Related to the API part, I was browsing and noticed that https://infuze.cloud/docs/api#/Virtual%20Machines/post_vms references templateVMID but https://infuze.cloud/docs/api#/Templates/get_templates shows only "get" so is the template just for quick-start scenarios or users could [eventually] create their own?

Great question. Currently, the templates are pre-configured by us for quick-start scenarios (e.g., Ubuntu 24.04, AlmaLinux, etc.). The API allows you to list these and use them to launch a new VM. The ability for users to create their own custom templates (i.e., take a snapshot of a configured VM and use it as a base image for future deployments) is very high on our roadmap. It's the logical next step after implement…

> (i.e., take a snapshot of a configured VM and use it as a base image for future deployments)

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)

Re: Show HN: I built a cloud on my own ASN w real 1:1 compute to fight the cartels

#15
post #3

Because I have been curious about this for so long, and you said "It's built on mostly open source technology" I figured now's my chance to ask: Why roll your own control plane when OpenStack ships with so many batteries included, and (arguably important) doesn't require someone making a vanity SDK to interact with your vanity cloud?

This is a fantastic and fundamental question. We evaluated OpenStack, and it's an incredibly powerful and comprehensive project. For us, it came down to two things: complexity and opinionation. Complexity: OpenStack is a massive suite of services designed to do everything for everyone. We needed to do one thing exceptionally well: provide high-performance, dedicated-core VMs with a dead-simple control plane. The oper…

Yeah but we definitely will get there, this also is not a race per se. Finishing quickly is important but finishing safely for everyone %99.99 of the time is probably the most important thing, next to a flashy UI/UX. We definitely have attention of some fantastic people and of course it will be even better when the bills can be more easily managed or offset costs. I know I immediately stopped paying for all my other cloud services and deposited to float an early bump but also importantly to test the payment systems. Last thing we need is that to fail for a user who has already been sold.
Post reply on HN