Hacker News new | past | comments | ask | show | jobs | submit login

I had a similar thought when looking at the Pricing FAQ section "Where is the differentiation between non-commercial and commercial systems?", which lists among other things Proxmox VE, which itself is open source and anybody is free to use it for free without commercial support. Lots of people use it for homelab-type things, or in academic or test environments.

Would you consider detecting whether each PVE instance the user connects to is a licensed / subscription-supported instance, and allowing non-licensed XPipe to connect to non-licensed PVE instances? There is an API for it already, see the 'level' field in https://pve.proxmox.com/pve-docs/api-viewer/index.html#/clus... .




Yeah the Proxmox limitation originally came about because I didn't find a reliable way to detect enterprise use from the CLI (But I had not used Proxmox before implementing that, so I might have missed it).

But if I see this correctly, I could call the API from the command-line with this: https://pve.proxmox.com/wiki/Proxmox_VE_API#Using_'pvesh'_to... and check the response. If that is possible I can definitely change that limitation.


To the latter point: yes, and each API page contains both the HTTP endpoint to curl and also the pvesh command to run


Same for Amazon Linux and Azure/EKS and AKS. I would understand if this were targeted towards a general consumer, but if it's targeting techies then precluding two of the biggest cloud services in the world is... certainly a choice.

Doubly so on Yubikey/GPG/PKCS11 support. Enhanced security should never be behind a paywall, IMO.

A better approach might be number of machines instead of this detection.


The original idea was that since the systems you listed usually cost quite a bit of money to run, these would primarily be run in an enterprise context. I don't think I could afford hosting a managed kubernetes cluster and multiple decent servers in Amazon or Azure for personal use.

The Yubikey security argument is fair though, I will reconsider that.

The number of machines detection has been on my TODO list for a while, but it's a little bit tricky to implement with the current implementation.


This is a challenging thing to get right. It's interesting seeing your back and forth with the other commenters on here.


I think you're good wrt the AWS/EKS cloud stuff fwiw. You'll always have beggars coming.

If the user can afford the enterprise costs of those, they can certainly afford paying for xpipe?

Discount for individuals actually managing their own infra sounds like a reasonable place to draw the line.

Probably a lot of shadow IT around where the employer pays for all the big cloud stuff and employees either can't or won't bother getting the software side of their work tools paid for.

(As for me, I'm one of those annoying FLOSS maximalists so I won't be interested without the source under a reasonable license and I'm able to compile it locally without spending a week spelunking in undocumented build scripts. But hey, I wish you the best and don't be afraid to charge properly. It's easier to lower prices than raise them if you catch my drift)




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: