Tools1 min read

The AI Stack Behind 4 Shipped Software Products

Some tool links below are affiliate links — I may earn a commission if you sign up, at no extra cost to you.

I don't rebuild the same stack from scratch every time I start a product.

Most of the boring pieces are already figured out.

This is what I'm actually using across Insidr, Probly, Haunt, and Cobble.

These are the main tools in my development loop. I use them to scaffold things, build features, debug problems, and make changes across the codebase.

This is the default for me right now. All 4 shipped software products use this combination.

Mostly a starting point for layouts and structure. I'll take something from v0 and make it my own rather than starting every page from an empty file.

My default once a product has real users and needs an actual database.

Subscriptions, checkout, webhooks, cancellations, refunds. Basically anything involving money.

For products that need live public data rather than a static dataset.

Transactional email and newsletters.

Mostly for figuring out what people are actually doing inside the product rather than guessing.

Domains, DNS, and email forwarding.

Still using its default theme for the site shell for now. Newsletter and resource content is file-based — BaseHub isn't the CMS anymore.

Security.

Every product gets a proper security pass before real traffic or real money touches it.

AI writes code incredibly quickly.

It can also write something confidently wrong.

I've learned that one the expensive way.

The useful part of having the same stack across multiple products isn't that the stack is particularly exciting.

It's that I don't have to think about it anymore.

The interesting 5% is the product itself.

Everything else should feel almost boring.

This is the exact stack behind Insidr — see it live.

Keep reading