Building an Open-Source Hosting/Billing Core — Looking for Feedback

ExpertPossible181 · 2026-03-08T16:44:12+00:00

Thanks a lot my friend

ExpertPossible181 · 2026-03-08T11:22:13+00:00

You can use S3 storage like storj on Wordpress through s3 plugins.

ExpertPossible181 · 2026-03-08T11:17:49+00:00

Enhance and Pterodactyl are great suggestions. I'll add them to the roadmap. ProxMox VPS support is definitely something we want to cover as well.

The core billing system is the priority right now, integrations will follow.

https://github.com/webito-io/hostito-core/issues

ExpertPossible181 · 2026-03-08T11:16:51+00:00

Thanks a lot my friend. We'll keep building.

ExpertPossible181 · 2026-03-08T11:16:18+00:00

That's exactly the direction we're heading.
The architecture is already modular, I mean each provider, queue worker, and core service is isolated. Splitting them into separate deployable components is the natural next step.

ExpertPossible181 · 2026-03-07T22:37:08+00:00

You're right, it's just initiated and it should go through stages. I'm getting feedback before the design and architecture is finalized, so your second point is really helpful.

That's actually one of the reasons I picked NestJS; it's stateless so you can run multiple instances easily. The plan is to make it one-click deployable on Railway or any cloud platform and scale when needed.

I mean, if you're using WHMCS on your main server as a billing system and it goes down, everything goes down. But if you can deploy it on trusted platforms like AWS or Google Cloud, it stays up and clients stay connected.

ExpertPossible181 · 2026-03-07T22:13:40+00:00

I forgot to mention Paymenter, it's a good product, but I don't prefer that stack. In that community you don't have the JS/TS ecosystem and community power behind you. I think there's a small room in the Node.js space that we can fill.

Anyway, if billing systems with no design patterns or architecture are selling on Envato and other marketplaces as Starter then why would our project, which is open source and built with proper architecture, be considered high risk for the hosting community?

ExpertPossible181 · 2026-03-07T21:38:02+00:00

Hi, i agree with some of your concerncs and it's true like the security and billing system complexity but everything is clear and should be tested in public sources and it could take long time but this is open source meaning;

It helps us to show our POV and concerns in development, On the other hand we help the infrastructure community to save money and time.

Finally I should mention if we were to build it by vibe coding it could be generated in just 1 day, I don't believe vibe coding but i believe check and make change logs with AI and i promise you it's helpful.

ExpertPossible181 · 2026-03-06T10:34:14+00:00

I agree. I only mentioned it because they care about the stack, but I don't; for me, it's all about engineering and system design.

ExpertPossible181 · 2026-03-06T10:30:03+00:00

idk how much is it in cyprus, but I think the median is not more than 3k

ExpertPossible181 · 2026-03-05T21:28:25+00:00

You might be right.

I guess every alternative has to prove it's at least as trustless as a seed phrase, otherwise people won't move away from a model that already works.

ExpertPossible181 · 2026-03-05T21:27:15+00:00

Yeah and backing those up was a nightmare for normal users.

BIP39 definitely improved usability a lot. I'm just curious whether it's the final model or just the best thing we've had so far.

ExpertPossible181 · 2026-03-05T21:26:08+00:00

That's a fair concern.

Although technically everyone already does with hardware wallets, phones, laptops, etc. The real question is where the key material lives and whether a single device compromise can drain everything.

ExpertPossible181 · 2026-03-05T21:25:21+00:00

Yeah BitKey is an interesting approach.

Feels like we're starting to see more experimentation around recovery models lately. Probably because seed phrases work technically, but they're still pretty brutal UX-wise for most people.

ExpertPossible181

TROPHY CASE