[HN Gopher] Show HN: BoxyHQ - open-source alternative to Auth0/W...
___________________________________________________________________
Show HN: BoxyHQ - open-source alternative to Auth0/WorkOS
Hi HN, we are Deepak and Sama, co-founders of BoxyHQ
(https://boxyhq.com/). BoxyHQ provides an open-source platform for
developers to quickly integrate enterprise features into their
software solutions. These include SAML Single Sign-On (SSO), Audit
logs, with more to come :) 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
Author : deepakprab
Score : 97 points
Date : 2022-03-22 15:16 UTC (7 hours ago)
(HTM) web link (boxyhq.com)
(TXT) w3m dump (boxyhq.com)
| mushufasa wrote:
| > 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.
|
| 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.
| grinich wrote:
| Yep, we even launched WorkOS via HN :)
| https://news.ycombinator.com/item?id=22607402
| deepakprab wrote:
| Would love to see both Auth0 and WorkOS go open-source as
| well! ;) Jokes aside, hi grinich. Would love to catch up
| sometime, my email is deepak@boxyhq.com
| Peer_Rich wrote:
| we use boxy over at cal.com and it's been super cool. deepak
| personally helped us get started
| deepakprab wrote:
| Thanks Peer. We are a natural fit for OSS projects/COSS
| companies that inevitably need these features once they start
| seeing interest from Enterprise customers.
| stillbourne wrote:
| keycloak is an easy to use easy to deploy idp
| deepakprab wrote:
| Keycloak is indeed a great product and more feature complete.
|
| 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.
| nickmyersdt wrote:
| If anyone knows an identity solution that supports bilateral and
| multilateral saml (federation of identity providers), automatic
| retrieval of metadata/certs, Oauth, Oidc, group rules, IDP
| discovery (routing to IDP based on identifier), wayfless, and IP
| Authentication I would love to hear about it. We run a B2B that
| sells our web based service into education (primary to through to
| university) and have a small team so are always interested in
| solutions in this space.
| deepakprab wrote:
| Great question, I would think Shibboleth might cover some of
| the topics you are looking for. I am not too experienced with
| the education sector, would love to chat further to get a
| better understanding.
| tailspin2019 wrote:
| Great day for a ShowHN for an open source SSO product :)
|
| 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!
| Ocha wrote:
| SAML Jackson -> Samuel L. Jackson
|
| Pretty funny
| deepakprab wrote:
| Haha, making SSO a little less boring. :)
| sotu wrote:
| I worked at an SSO Vendor for years, in our early days when
| we were 20 people we had a whiteboard with funny SAML
| names.. one of my favorite was King Federate which we
| abbreviated as K-Fed!
| deepakprab wrote:
| Haha, love it. Hope no one was fed up! Do you recollect
| the other names?
| [deleted]
| deepakprab wrote:
| Thank you tailspin2019, it definitely is an interesting day for
| an SSO product! :)
|
| 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.
| tailspin2019 wrote:
| Thanks I was looking further at GitHub and realise that
| Jackson and Hermes etc are your product names.
|
| 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!!
| deepakprab wrote:
| Thank you, great feedback once again. :) We definitely have
| some thinking and work to do with the branding of each
| product.
| crad wrote:
| Looks like the name of one of the open source projects in the
| platform: https://github.com/boxyhq/jackson
| deepakprab wrote:
| Indeed, thank you.
| the_arun wrote:
| How are you planning to make money?
| caloique wrote:
| > 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.
| pimterry wrote:
| The 'privacy vault' feature sounds interesting - do you have any
| more details how that might work?
| deepakprab wrote:
| At a high level it lets you separate (and centralize) your PII
| data from your main infrastructure whilst providing
| configurable semantics on how the data should be encrypted
| underneath. Additionally you'd have granular control (and
| audit) on who/where/when (access control, geo, time) can access
| the vault. As an example you'd ship Social Security Numbers to
| the vault and configure access to it for a KYC application
| which can verify the SSNs as needed.
___________________________________________________________________
(page generated 2022-03-22 23:01 UTC)