pseudopuppet

Hi HN, Logto v1.2.0 just arrived with Redis cache support, new translations, new Management APIs, etc. etc. Please don't hesitate to let us know any thoughts you have.

Inspired by trpc and KoaJS, I started to think if the RESTful world can have something with native type support. Spent several days and here's the result:

- No mind-switch, still RESTful

- Write typed APIs, get a typed client free

- Guard request input (path params, query, body) and output (response)

- Minimalism, zero dependency and framework-agnostic (Use any parser or fetch polyfill if needed)

- Auto OpenAPI JSON generation

Some thoughts about future:

- Make it for prod use

- Infer CRUD APIs from a single type definition

The POC fits my needs, but don't know if it's a good idea to proceed. Is there any existing project like this? Please let me know.

Hi HN again. We just released a new version of Logto with Sign-in Experience v2, forgot password flow, user suspend API, and much more.

We are growing fast with the help of the community. So feel free to drop your comments to let us know your thoughts!

Hi HN,

We're maintaining this roadmap and expect to have some user comments to discuss plans and directions for the product. But we are still receiving requests mainly from Discord and GitHub issues.

I'd like to know what you feel about an open-source project's public roadmap. Is it helpful to you? What would you like to see in it? Any suggestion is appreciated.

Hi HN,

Our project is Logto, an open-source solution that helps you build the sign-in, auth, and user identity within minutes.

The first public beta launched two months ago, and it is incredible that many people love our project and are willing to contribute even before our “Bounty Hunter” series. The community contributed translations of Français, Türkçe, 한국어, and Português, along with connectors for Azure AD, Kakao, Naver, and Discord.

We cannot be here without the community’s help, and we’d like to hear more from you. Feel free to let us know if Logto can help you or what you expect from Logto. Cheers!

Thanks!

Just had a look on Authentik, it’s very cool. Looks like Authentik is for enterprise (i.e. workforce) identity only, while Logto starts from customer side. E.g. sign-in and identity for an online bookstore.

We started as for customer identity, which means the current version is for the apps that have external customers, e.g. an online store. We’ll constantly iterate to fit more scenarios.

You are right. Will refine the wording soon.

We don’t have a dedicated demo website for now. But a good feedback tough.

Thanks. Will add a11y lint rules and fix soon.

Since our first alpha version, we've had a lot of help and received great ideas from the community. Thank you!

Logto is now in public beta. We're working hard on more improvements, SDKs, and connectors. Feel free to drop your comments or needs.

Hope the official release of Logto will meet you soon.

Thank you!

Ah we noticed this - improving now.

Sure yes. That’s one of the huge advantages using Logto.

Thanks. Agreed with you. It’s just a start and we’re working on more SDKs. Stay tuned.

Yes. More auth methods are on the way.

I think Logto will be good at “standalone identity service”, which means you can delegate all the sign-ins and user identity issues to Logto. (Just like SSO)

So you can have only one Logto installed, and add multiple “API resources” (for apps with a dedicated API service) and “applications” (for traditional web apps or your native/spa clients) in Logto. No matter they are remote or local, VPS or SaaS.

The logic is simple:

- for clients and traditional web apps, when it detects user is not signed in, use SDK to redirect to Logto

- for API services, add a middleware function to check if the request holds a valid token

If you’d like to connect a third party identity provider, “connectors” will be your friend.

These cases are covered in the docs.

Hope my reply helps. Feel free to join our discord channel or send us an email if you have any questions. :-)

Thanks. This scenario makes sense. Logto now uses Docker image for deployment. We didn’t tested Logto in Lambda yet, but will do.

For SAML or other identity auth methods, we’ve designed “connector” protocol which enables you to easily connect arbitrary identity providers.

Permission and automation are the two of main topics we’ll focus on in the next half of 2022.

Also we’ll provide deployment guides for the mainstream cloud services.

Your needs are very practical and reasonable. Really appreciate it. Would love to connect via discord or email. Cheers.

Yes yes! It’ll be a amazing feature that can enable automation and save tons of time. Logto supports these hooks technically, and we can productize it in the near future.

Thank you for the great feedback. Stay tuned. :-P

We’re still exploring. Basically we’ll focus on the community and product first, and only charge for enterprise features and services in the future.

We saw ory.sh a while ago and it looks great. From what I can see now, ory is mainly focusing on the server side, while Logto is not only an identity service, also trying to provide a smooth and customizable sign-in experience (UI) for end-users and let you to focus on your real business asap.

Plus, Logto comes with a web admin console to manage Logto and to know your users with no coding skill required. You can get user insights like DAU/MAU with graphic charts within the console.

TL;DR it’s much easier and user friendly.

Thanks. Keycloak needs professional identity knowledge to correctly set up, and has tons of extra UI/UX works to do. Logto provides out-of-box usage even if you are not familiar with OAuth/OIDC at all. It comes with a customizable end-user sign-in experience (UI) for both web and native, and a web admin console to manage Logto and know your users.

Logto provides a frontend-to-backend identity solution, with minimum invasion to the current tech stack.

We’re currently focusing on end-user experience, but CLI support would be not hard since our service is based on OIDC.

Co-marketing would be great, let’s keep in touch. What’s your preferred communication channel?

With the idea “why should I code sign-in again,” I started building Logto with several developer friends about one year ago. Quickly we found the idea goes bigger (also the team); now, we want to build not just a customizable sign-in UI but also an identity solution.

Here comes the public alpha:

- An OIDC-based identity service

- Multi-platform user sign-in/up experience with dark mode and SDKs (Web, iOS, and Android)

- Sign in/up with dynamic SMS/Email passcode (Passwordless)

- Out-of-box social sign-in integration (GitHub, Google, WeChat, Alipay, etc.)

- A web UI to control all the above (Admin Console)

- Extendable multi-language support

It’s fully open-sourced, and we are super happy to hear from the community.