Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
n2d4
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
21 ms
·
301.
▲
by
n2d4
2y ago
Our approach to sign-in pages is a bit different than Auth0's; instead of redirecting you to us, all of our components live on your very own website. The only time the browser will redirect to our domain is momentarily during the OAuth
302.
▲
by
n2d4
2y ago
Supabase Auth is just authN, and it doesn't do authZ (organizations, permissions/RBAC) or user management (impersonation, user metadata, etc.). It also doesn't integrate as deeply into Next.js as we do. I'm a big fan per
303.
▲
by
n2d4
2y ago
Everything is open-source. We implement providers when a paying customer requests them (Team plan for OIDC-compatible providers, Growth plan for everything else, including SAML). Once we've implemented them, though, everyone benefits.
304.
▲
by
n2d4
2y ago
Yes. But it will show our name and logo, and we limit shared key usage to a few users per project, so we highly recommend you set up your own keys before going into production. (The dashboard will let you know in time.)
305.
▲
by
n2d4
2y ago
Makes sense. Yep, we can support that — just shoot me a message if you end up needing this (konsti (at) stack-auth.com).
306.
▲
by
n2d4
2y ago
I've literally been building this right now, currently doing E2E tests! Should be done by end of the week. (and it'll be free for everyone)
307.
▲
by
n2d4
2y ago
Supabase Auth is only authentication; it doesn't do organizations, permissions/RBAC, impersonation, etc. We are working on some fancy Postgres connectors to let you use Stack Auth with the DB part of Supabase and RLS. GoTrue and P
308.
▲
by
n2d4
2y ago
This exact set of problems is precisely what we're trying to solve. Reading this feels like great validation :)
309.
▲
by
n2d4
2y ago
Our clients are MIT, our servers are AGPL.
310.
▲
by
n2d4
2y ago
Indeed, we launched an MVP in Show HN a few months ago — dang messaged us and said we should apply to YC, which we did, and now we're launching here again, officially. :D We will definitely support those frameworks too, eventually. Tho
311.
▲
by
n2d4
2y ago
Our backend and dashboard are language-agnostic, and you can access their REST API from anywhere. However, there is a Next.js SDK with server & client components, hooks, and functions that integrate very deeply into the framework — that
312.
▲
by
n2d4
2y ago
Yes. Both Zai and I care a lot about FOSS — we also believe that open-source business models work, and that most proprietary devtools will slowly but surely be replaced by open-source alternatives. Our monetization strategy is very similar
313.
▲
by
n2d4
2y ago
You might like what we built then — we have a setup wizard that adds auth to your Next.js project for you, including creating all the necessary pages, handlers, and config ;) npx @stackframe/init-stack@latest
314.
▲
by
n2d4
2y ago
Noted, thanks. We're focussing on Next.js frontends right now — which is fairly well-documented — I hope to get some Python & Golang examples in there by the end of the week.
315.
▲
by
n2d4
2y ago
Unfortunately, Web Components are still somewhat immature [1], but eventually, our plan is to support vanilla React as well. We really want to nail every single integration that we officially support before growing horizontally, because l
316.
▲
by
n2d4
2y ago
Supabase Auth: We do much more than them — e-mails, organizations, permissions & RBAC, user dashboard, impersonation are some of the features we have. (I like Supabase a lot as a DB — we're working on some fancy connectors to use S
317.
▲
by
n2d4
2y ago
Appreciate the feedback! We have the following in our GitHub README, which we should probably copy to our frontpage: > # How is this different from X? > > Ask yourself about X: > > - Is X open-source?
318.
▲
by
n2d4
2y ago
In theory yes — actually, we already are an OAuth provider behind the scenes — though we haven't documented this anywhere yet. What would you use it for?
319.
▲
by
n2d4
2y ago
Kratos is geared towards enterprises and less developer-friendly. We integrate very closely into the tech stack that we currently target, which is Next.js + Postgres, and want to make setup as straight-forward as possible. I would say we ar
320.
▲
Launch HN: Stack Auth (YC S24) – An Open-Source Auth0/Clerk Alternative
(github.com)
280 points
by
n2d4
2y ago
|
141 comments
321.
▲
by
n2d4
2y ago
Maybe that applies to people going to Gawker or whatever and writing an exposé on YC, but that's not what I'm talking about. There are very few people who, at the end of the batch in a private one-on-one conversation, say that joi
322.
▲
by
n2d4
2y ago
Going through it for my second time now, it's definitely worth it. There's an excess of smart people and it's transformational for any startup, but especially if you build in devtools like us. The network is strong and suppor
323.
▲
by
n2d4
2y ago
Pretty much, I think that sums it up quite well :)
324.
▲
by
n2d4
2y ago
So you'd rather write twice the code and use React contexts for this simple feature just to avoid iterating through an array?
325.
▲
by
n2d4
2y ago
Which is even more effort, and isn't better than the original solution. What if you want to render your navbar differently depending on the context? Eg. on desktop it's a flexbox at the top of the page, and on mobile it's an
326.
▲
by
n2d4
2y ago
Sure! Supabase is great, though their authentication is really just authN and doesn't have authZ or anything more advanced like impersonation, connected accounts, orgs, etc. We are more focussed on building the entire package. We have
327.
▲
Show HN: Stack Auth (YC S24) – the open-source Auth0/Clerk alternative
(github.com)
3 points
by
n2d4
2y ago
|
4 comments
328.
▲
by
n2d4
2y ago
Looks like it doesn't work for Libre Barcode :( https://www.google.com/search?q=libre+barcode+39+font
329.
▲
by
n2d4
2y ago
It's always fascinating to me when people say "not to burst your bubble but it's really simple to use this other tool which can already do the task", and then write an essay about all the workarounds they had to apply to
330.
▲
by
n2d4
2y ago
No, they shouldn't pay back the "benefits", because they already paid for the fuels. No market failures there. There is a very obvious market failure with the downsides of fossil fuels however (negative externalities), and Pu
More ›