Every B2B startup faces a common challenge when it comes to selling into the Enterprise; they need to allocate time and resources to support all the requirements to make their offering enterprise-grade. Supporting these requirements is a significant undertaking for the engineering team, especially since they already have their hands full with the core product. We experienced this problem ourselves and that is why we built BoxyHQ, a platform to integrate enterprise features in any SaaS app with just a few lines of code.
The main difference with Auth0 and WorkOS is that BoxyHQ is being built on an open source ethos. Our focus is to be a developer-first security platform, putting developers at the centre of our holistic approach and help them close the gap between compliance and security.
Please let me know if you have any questions, you can also reach out to me at deepak@boxyhq.com
I am excited by this.
However I got thoroughly confused on the introduction page of your docs:
https://boxyhq.com/docs/jackson/introduction
What is “Jackson” - did you rebrand at some point?
I think it’s a Pulp Fiction reference(?) but I spent more time looking that (and the name “Jules Winnfield”) up to try and understand the context then I did reading/parsing the intro!
I don’t mind a bit of humour, but this was a tad confusing…
What are your plans regarding a commercial model for your product (if you can share?)
Edit: also as a bit of feedback; because your website is quite basic at the moment and the only call to action seems to be the big “Contact Us” button, I’m left wondering what stage you’re at and whether you have anything that’s usable now that I can use in production, or if it’s still at a Beta / under-development stage?
If it’s ready to be used, perhaps add a “Get Started” button to the left of the “Contact Us” button as that serves as both a strong call to action and also clearly indicates that you consider the product is ready to use (even if your commercial offering isn’t yet).
If it’s not yet ready, perhaps change that suggested button to a “Keep Me Updated” button with an email signup?
There’s not enough here for me to consider contacting you at this stage… I would either want to try it out, or give you my email so that you can tell me when it’s ready to try out.
I glanced at the GitHub repo but I’m still not really clear if this is a work in progress or it’s ready to go…!
Just my opinion… for what it’s worth!
Pretty funny
It is a Pulp Fiction reference but I agree it is confusing. We'll refine the intro and the CTA on the webpage, great feedback.
Our core will always be free (Apache 2.0 license) and our commercials will be based on the following models: 1) A hosted solution in the future 2) Premium features on top of our core (To ease deployment, administration and integrations with Enterprise security products) 3) Vertical specific solutions for regulated industries like Healthcare and Finance.
Perhaps you could mention these product names on the marketing site so there is a bit of continuity between that and GitHub/docs?
I like the humour. My instinct would be to either “own” those product names fully and use them boldly throughout, or deemphasise them in favour of your Boxy brand… :)
Looking at the Audit Logs repo introduction, I know this is a reference I’m not getting, but I’m not going to look this one up!!
> A grade 36 Bureaucrat just like Hermes Conrad. Audit logs matters that only a true bureaucrat can handle properly.
Keep up the good work. What you’re doing looks very interesting!!
We do OAuth, OIDC, and idp routing based on domain or id. We track ips and have the ability (in the Enterprise tier) to add IP ACLs, but I am not sure what you mean by IP authentication.
I am not sure what you mean by wayfless, not familiar with that term.
Feel free to reach out to me for more info if you'd like to chat, my contact info is in my profile.
You can download and run the community version in a variety of formats. For testing you could spin up an ec2 instance if you'd like.
Download it here: https://fusionauth.io/download
If you want us to manage it, you can sign up for a basic cloud here: https://fusionauth.io/pricing
Let me know if you have questions.
Somewhat similar to using Azure or Okta B2B integration, but with support for things that don't support native SAML and older legacy platforms that we just can't kill.
Not to detract from this project, but I'm familiar with Auth0 and WorkOS both, and I think both would say the same thing about themselves.
But as far as pure open source authentication solutions, the ones I know of are:
* Keycloak
* Ory
* Identity server (.net)
But Auth0/WorkOS are definitely focused on building a developer first security platforms. Along with a lot of other companies.
We are currently focused on refining the SAML SSO integration. We abstract away SAML login as an OAuth 2.0 flow so that it plugs in seamlessly where a Google or Github login (for instance) would in your tech stack.
Regardless, this is a solution for your application that doesn't require running something like Keycloak. If I was developing an application I'd be looking at this, Auth0 or WorkOS to get the features my customers are demanding. (SSO/SAML/OAUTH mostly). Keycloak does the opposite, as a business I could deploy Keyclock to be my SAML IDP, but still need my applications to support SAML.
I like the open source ethos and appreciate you being upfront with your future business plans.
Welcome!
