5 ms·

> All content that resides under any "ee/" directory of this repository, if such directories exists, are licensed under the license defined in "ee/LICENSE". M

by s1k3s 4y ago

> All content that resides under any "ee/" directory of this repository, if such directories exists, are licensed under the license defined in "ee/LICENSE". Man I really hate how the term "Open Source" is used nowadays.

vmatsiiako 4y ago
We provide all the main functionality completely for free under the MIT license. What this means is that all the integrations (Docker, AWS, Vercel, Kubernetes, Terraform, etc) are available completely to everyone. Next to that, all the features related to secret sharing, and security are also available under MIT. ee is only reserved for some features that are (mostly) needed by enterprises (e.g., audit logs, sso, advanced access controls). This helps us get the financial means to also maintain the free ope-source product better.
- mbarneyme 4y ago
  https://sso.tax/ https://sso.tax/
  - Kiro 4y ago
    Really strange thing to reply to this with. Did you find it just now and searched for "sso" on HN just to get a chance to randomly post it?
    - mdekkers 4y ago
      Why strange? That was the first thing that came to mind when I read “sso” as part of the “enterprise’ offering, and was not surprised to see that someone else linked the sso tax website
      - Kiro 4y ago
        You're right. I misread the original post and also managed to do a double fail and misunderstand the SSO Wall of Shame as well. Sorry, mbarneyme!
  - tptacek 4y ago
    In other words: this product is employing a pricing strategy that is overwhelmingly common in our industry (because it works).
    - ignoramous 4y ago
      And the industry is sick of it...? At least some vocal minority
- pc86 4y ago
  Audit logging and SSO is pretty basic functionality that requires very little (many people would argue no) additional effort or cost to maintain on the development side.
  - dabeeeenster 4y ago
    We just spent about 3 months refactoring our audit logging. If it requires "no" additional effort, you can just fork the project and provide that "no" effort yourself.
  - dangtony98 4y ago
    Surprisingly, audit logging has been deceivingly complex for us. There are many types of events (part of logs) triggered throughout the platform carrying different payloads/formats (e.g. events related to secrets, users, etc.). The variation in such events is increasing with the complexity of the product not to mention costs required to handle accumulating events. Last month, we served 14.2M+ secrets alone through the platform not counting other events — I hope this sheds more light on the audit logging side of things? Re SSO: Totally get this one and I'm aware of the SSO tax — we're still figuring this one out but know currently that it's an absolute must for enterprises.
    - pc86 4y ago
      You know what you're definitely right about audit logging. It does seem like one of those "easy on the surface, will absolutely kill you in the details" sorts of things.
    - grinich 4y ago
      I know we (WorkOS) have already chatted with you about SSO, but reading this comment I'm realizing we should really also chat about Audit Logs too. We recently built an entire product to make it insanely easy to offer enterprise-grade audit logs to your customers. Plus it includes strongly-typed event payload schemas and log streaming to 3rd-party SIEM vendors. Super fast to integrated with pay-as-you-go pricing based on volume. Vercel and others are using this. https://workos.com/audit-logs https://workos.com/audit-logs I think we have a shared Slack channel set up with Infisical so feel free to DM me there. You can also email me direct: mg@workos.com. (Same goes for anyone else on HN needing this stuff. :))
- benatkin 4y ago
  I'm not a fan of monorepos in general (though I admit tool support them better in many cases*) but making people download proprietary code makes them worse. * Especially GitHub. Very opinionated in favor of monorepos.
brandonmenc 4y ago
Why, what do you think it means? https://www.gnu.org/philosophy/open-source-misses-the-point.en.html https://www.gnu.org/philosophy/open-source-misses-the-point....
- vmatsiiako 4y ago
  Indeed! We are also planning to add the MIT-only copy of our repository that is going to remove all the ee licensed code.

by s1k3s 4y ago

vmatsiiako 4y ago

We provide all the main functionality completely for free under the MIT license. What this means is that all the integrations (Docker, AWS, Vercel, Kubernetes, Terraform, etc) are available completely to everyone. Next to that, all the features related to secret sharing, and security are also available under MIT. ee is only reserved for some features that are (mostly) needed by enterprises (e.g., audit logs, sso, advanced access controls). This helps us get the financial means to also maintain the free ope-source product better.

mbarneyme 4y ago
https://sso.tax/ https://sso.tax/
- Kiro 4y ago
  Really strange thing to reply to this with. Did you find it just now and searched for "sso" on HN just to get a chance to randomly post it?
  - mdekkers 4y ago
    Why strange? That was the first thing that came to mind when I read “sso” as part of the “enterprise’ offering, and was not surprised to see that someone else linked the sso tax website
    - Kiro 4y ago
      You're right. I misread the original post and also managed to do a double fail and misunderstand the SSO Wall of Shame as well. Sorry, mbarneyme!
- tptacek 4y ago
  In other words: this product is employing a pricing strategy that is overwhelmingly common in our industry (because it works).
  - ignoramous 4y ago
    And the industry is sick of it...? At least some vocal minority
pc86 4y ago
Audit logging and SSO is pretty basic functionality that requires very little (many people would argue no) additional effort or cost to maintain on the development side.
- dabeeeenster 4y ago
  We just spent about 3 months refactoring our audit logging. If it requires "no" additional effort, you can just fork the project and provide that "no" effort yourself.
- dangtony98 4y ago
  Surprisingly, audit logging has been deceivingly complex for us. There are many types of events (part of logs) triggered throughout the platform carrying different payloads/formats (e.g. events related to secrets, users, etc.). The variation in such events is increasing with the complexity of the product not to mention costs required to handle accumulating events. Last month, we served 14.2M+ secrets alone through the platform not counting other events — I hope this sheds more light on the audit logging side of things? Re SSO: Totally get this one and I'm aware of the SSO tax — we're still figuring this one out but know currently that it's an absolute must for enterprises.
  - pc86 4y ago
    You know what you're definitely right about audit logging. It does seem like one of those "easy on the surface, will absolutely kill you in the details" sorts of things.
  - grinich 4y ago
    I know we (WorkOS) have already chatted with you about SSO, but reading this comment I'm realizing we should really also chat about Audit Logs too. We recently built an entire product to make it insanely easy to offer enterprise-grade audit logs to your customers. Plus it includes strongly-typed event payload schemas and log streaming to 3rd-party SIEM vendors. Super fast to integrated with pay-as-you-go pricing based on volume. Vercel and others are using this. https://workos.com/audit-logs https://workos.com/audit-logs I think we have a shared Slack channel set up with Infisical so feel free to DM me there. You can also email me direct: mg@workos.com. (Same goes for anyone else on HN needing this stuff. :))
benatkin 4y ago
I'm not a fan of monorepos in general (though I admit tool support them better in many cases*) but making people download proprietary code makes them worse. * Especially GitHub. Very opinionated in favor of monorepos.

brandonmenc 4y ago

Why, what do you think it means? https://www.gnu.org/philosophy/open-source-misses-the-point.en.html https://www.gnu.org/philosophy/open-source-misses-the-point....

vmatsiiako 4y ago
Indeed! We are also planning to add the MIT-only copy of our repository that is going to remove all the ee licensed code.