Our great sponsors
-
infisical
♾ Infisical is the open-source secret management platform: Sync secrets across your team/infrastructure and prevent secret leaks.
-
onepassword-operator
The 1Password Connect Kubernetes Operator provides the ability to integrate Kubernetes Secrets with 1Password. The operator also handles autorestarting deployments when 1Password items are updated.
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
sso-wall-of-shame
A list of vendors that treat single sign-on as a luxury feature, not a core security requirement.
- 1-click deployments to AWS EC2, Digital Ocean, Render, [Fly.io](http://fly.io/): More ways to self-host Infisical on your own infrastructure.
In addition, the platform has become more stable and undergone a full-coverage penetration test; we’ve also begun the SOC 2 (Type II) certification process.
Overall, we’re really lucky to have support of the developer community, and, in fact, Infisical has gathered over 7k GitHub stars, and now processes over 200 million secrets per month for everyone from solo developers to public enterprises.
Our repo is published under the MIT license so any developer can use Infisical. Again, the goal is to not charge individual developers. We make money by charging a license fee for some enterprise features as well as providing a hosted version and support.
Check out Infisical Cloud (https://infisical.com/) or self-host Infisical on your own infrastructure (https://github.com/Infisical/infisical). We’d love to hear what you think!
We’re excited to continue building Infisical, and keep shipping features for you. Please let us know if you have any thoughts, feedback, or feature suggestions!
Very cool and congrats on the launch. Can you perhaps talk about pros/cons of using your Kubernetes operator vs 1Password Connect[1]? Seems like your operator would require writing some new CRDs where I believe 1Password Connect continues to use the existing kind: Secret.
[1] https://developer.1password.com/docs/connect/
Java SDK was actually already developed by one of our community members (Piyush Chhabra) and has to be reviewed: https://github.com/piyushchhabra/infisical-java
Rust SDK is coming soon too.
SDKs are not the most popular way of using Infisical though. You should look into our CLI (which most of the folks use) and API
There’s a strong, widespread objection to hiding security features behind a paywall: https://sso.tax/
If 2fa is the only way you can differentiate in order to force enterprises to pay, it’s better to have a fee for security than to die because you can’t make money… but broadly, as a security company, you should aim for maximum security for every user.