AllModules

We're hoping Q2 release, and we're dogfooding it now. Our dashboard will soon allow full navigation with a guest account, and we'll use those learnings to deliver a polished product. Guests get a JWT like any other user, but the token is denoted as being a guest, and your application can handle that however you like.

In short, it's a second-gen platform that doesn't have to support a bunch of legacy customers, so we can make it much less complex to use.

We started doing auth because our dev customers kept telling us how much of a pain it was with the first-gen companies (Auth0 et al). With Userfront, you don't have to learn all the standards/protocols or deal with browser quirks, and things like testing, access control, and multi-tenancy are first-class features instead of things you spend lots of time on.

Thanks for your feedback and agreed! We have a landing page overhaul on our short list.

Thanks! We have what you mentioned so will make it more accessible from the landing/guide/dashboard pages.

Yes you can do multi-tenancy natively, with each tenant having the same power as its parent in terms of roles, separate login pages, etc. Our architecture is "tenants all the way down".

> I'm not seeing anything about standards compliance

Thanks! We'll make a section to highlight them. We use the JWT standard (not sure if that is what you mean?), Oauth 2.0, SAML, etc... there are lots of standards in this space

> it should be trivial to rotate keys

This is exactly what we're rolling out in the next few weeks. We already have it trivial to rotate API keys [1], and we have a JWKS endpoint [2], so rotating the primary JWT private key is next on the list.

[1] https://userfront.com/docs/api.html#api-keys

[2] https://userfront.com/docs/api.html#json-web-key-set-jwks

Co-founder here. It's fun to see your work on the front page at 6am, and I guess I'll stop lurking now. I'm happy to try to answer any questions you may have.