Re:Launch HN: Arengu (YC S21) – Frictionless Signup Flows
by ollerac on Friday August 06, 2021 @09:09PM
(#28094716)
I believe you're looking for something like Outseta (https://www.outseta.com/)
They're a membership platform that supports:
- Payments
- Sign up forms
- CRM
- Authentication
- Content protection
- Email marketing
- Help desk
- Notifications
Pretty amazing if you ask me. I have no affiliation with Outseta, but I do follow the founder on Twitter.
Re:Launch HN: Arengu (YC S21) – Frictionless Signup Flows
by runako on Saturday August 07, 2021 @11:36PM
(#28104022)
Thank you so much! This appears to be exactly what I am looking for, and then some.
This is exactly why I keep coming back to HN.
Re:Launch HN: Arengu (YC S21) – Frictionless Signup Flows
by jacobovidal on Friday August 06, 2021 @05:38PM
(#28093051)
This is a really interesting use case. If you use Stripe, you can use the Stripe Customer Portal to allow your users to handle subscriptions, update users' information, billing details, etc: https://www.arengu.com/tutorials/passwordless-authentication...
Anyway, there are many boilerplate SaaS blocks that might make sense to explore for Arengu, but currently we're focused on signup and onboarding flows/screens.
A feature request: I would absolutely love to have something like Arengu that also handles the rest of the boilerplate SaaS stack. Key is a branded user portal with a billing area (I should just give it my Stripe keys and let it generate the screens); user/team management, etc.
To give an example: if you click your avatar in the top right of a Github page, I would like to outsource all of those pages. (How would that work? I would provide APIs and then have some kind of page builder in Arengu that would display the data & handle user input. So for example if I were Github, I would have an endpoint that would return JSON for the repositories for a user, and Arengu would display github.com/$USER?tab=repositories. There could also be API contracts where my API essentially returns the HTML for part of the page.) Basically -- use your front-end builder to reduce the front-end code I need to write & manage.