What I'm building right now

A confused builder stands beside a crooked, collapsing house.

In 2023, my attention was caught by some tech influencers and indie hackers making a lot of money developing their own SaaS products. That was a game changer for me. Like many developers, I love building things on the side, not realizing that one day I could create something people would actually use and maybe even pay for.

So, I started developing an app dedicated to workout building with AI. It was still the early days of AI, and I was essentially building a wrapper around it. It took me a few months, but in the end, I had a fully functional app that allowed you to invite people, share workouts, build your program manually or with AI, handle payments through Stripe, and export everything as a nice PDF.

It was fun, and I discovered a lot. But apps like this are everywhere on the internet, and honestly, I’m not that passionate about the gym or workouts. So, I didn’t go beyond the MVP stage.

We are now, at the beginning of 2025 and I want to keep building, but this time I have my first solo experience. I started searching for my next app idea but ended up with nothing. Every time I thought of an idea, either it was too big to build alongside my work or there was too much competition. I tried my best to find a new idea, even asking my wife if she needed something for her work, but didn’t have any success.

Looking back at my first project, I realized the part that took the most time wasn’t the AI or the workouts. It was the technical challenges around designing the app with a multi-level tenant system. This let users create workspaces within their organizations, keeping everything secure and separated.

One thing I want to add is that while many people build “B2C” apps (where one user has access to their own resources and that’s it; no invitations, organizations, roles, or scoped access), I aim to build apps that are B2B-ready. I might start with a simple B2C approach, but I always make sure my foundations support B2B features for organizations later on.

Based on that, I came up with an idea. Even though I didn’t know exactly what I wanted to build, I knew I wanted to create something, and I had a clear vision for its foundation. Thanks to my work experience, I knew what was needed to develop a SaaS. So, I started building nanostack.dev, an app that manages all the common logic needed for SaaS, such as user management, API key systems, permission systems, and features like email templates. Every redundant block in app development is handled in one place, allowing me in the future to develop other apps based on nanostack. It acts like a set of generic APIs for SaaS.

I plan to open source it someday, which is something I’ve always wanted to do. As someone who relies heavily on open source code, I hope to be able to contribute more one day.

Nanostack is designed to support multiple products and run with minimal dependencies. Only a Postgres instance is required, with optional Redis support.

Screenshoot of nanostack app

I have almost finished the MVP version and found a fun app idea when developing it with a more commercial approach, called echopoint.dev. It is a tool that makes functional testing easy using a flow-based approach. The idea is to use nanostack as a foundation, making sure I am heading in the right direction with its development and that it meets real needs. I might be biased since I’m creating my own product to validate that my first product is useful, but at least I’m having fun.

Subscribe to Alexis Dev Notes

Don’t miss out on the latest issues. Sign up now to get access to the library of members-only issues.
jamie@example.com
Subscribe