Thanks for sharing!
> We’re also toying with the idea of an “enterprise” self-hosted deployment, similar to gitlab’s billing model, and thoughts from the community on this front would be appreciated!
Transparency and an open stewardship of the project can help: https://about.gitlab.com/company/stewardship/ Make it clear what features are paid, and define that for example free features are never moved to the paid tier.
Re: the gitlab link you sent, we really like the transparency around not making a free feature paid, and the fact that all tests are OSS.
Overall, we'll work on something like this. Thanks for pointing it out!
We are a small start up. We use SAML / SSO. We care about security. We care about privacy.
None of this is “enterprise”.
We stopped using competitors to you because of data privacy issues.
We would happily pay for a self host version, where we control all the data recorded.
These type of tools are extremely useful, and it hurts not having it. But they are just way too much of a privacy issue.
Self hosted and paid - is the future of data privacy.
I would love to see you (and others) off these options, it’s really a game changer and makes the switch easy from any product that is not self hosted and collects our customers data.
> Self hosted and paid - is the future of data privacy.
So, you want a paid, self-hosted version - not named "enterprise"?
Much as I dislike the gitlab decision to gateway sso - there's no problem paying for and self-hosting it?
Or are you making two arguments - keep features like sso foss - we will happily buy paid self-host version anyway?
regarding self hosting, how can contributors make sure that you are self-hosting and paying? If code is open and already in your infra there is no way to enforce anything.
The way we're thinking of addressing this is not including the enterprise features in the output binary when you install highlight.io. This makes it a bit harder to actually build the project with all the enterprise features. It it something that folks can take advantage of, though.
Ultimately people do not want to run all their own services if they can pay someone else to run it for them.
On the other hand, I'm dealing right now with two services (NetSuite and Certify). Both "support" SAML, but they offer no direction on how to set it up or any sort of support for the setup. The documentation that is out there, is out of date and/or incorrect. Even though they offer these as paid additions, they don't really support them.
Anyway, that's where I'm coming from. I'm not trying to get into some deeper meaning debate here.