Kurynt

Today's the day I've launched Kurynt! Similar to my last product, The Wheel Screener, the majority of the effort came together in the past few weeks. Kurynt will be a bit different, however, where I see many new features to be built over the coming months and years. I've launched my product on the following platforms:

• IndieHackers (here!) with a large in-depth post: https://www.indiehackers.com/post/introducing-kurynt-the-last-tool-you-will-ever-need-to-manage-third-party-code-5579ca3313
• My blog: https://chrisfrew.in/blog/my-second-saas-product-introducing-kurynt/
• Medium: https://chrisfrewin.medium.com/my-second-indy-saas-product-introducing-kurynt-23e0ec227fec
• DEV.to: https://dev.to/fullstackchris/kurynt-the-last-tool-you-will-ever-need-to-manage-third-party-code-31no
• Product Hunt: https://www.producthunt.com/posts/kurynt
• Show HN: https://news.ycombinator.com/item?id=32278967
• Kernal: https://kern.al/idea/package-deprecations-and-end-of-life-alerts

Initially formulated in April of 2022, I'm back giving the last push to get the Kurynt MVP out. Today I'm finalizing the stripe checkout flows and some of the long put-off account management tools and API endpoints. I'm using Supabase as my main backend tool, which is a bit of an experiment for me, but we'll see how it goes!

I formulated the idea for Kurynt as a tool to help me manage a large React Native app at my day job. We frequently ran into the issue that upgrade a single package would break the entire application. Tools like Dependabot and Snyk have always felt incomplete to me, so I wanted to build Kurynt as more powerful tool to help manage upgrades, regressions, and end-of-life managing for all third-party code.