I’ve made the entire eniem project free and open source.
That includes the Next.js SaaS boilerplate, the CLI, the documentation, the starters, and an unreleased v2 experiment. The repositories are now read-only archives, with a banner pointing to TStack, the successor.
eniem used to cost $149 for lifetime access. Nobody bought it.
That’s part of why I’m making this change. But it’s also part of a broader decision about what I want to spend my time building.
A finished product isn’t proof that people want it
There was real work in eniem. It wasn’t just a landing page for something I hoped to build later. There was a boilerplate, tooling around it, and documentation to help people use it.
I also spent time improving how I worked on it. When I moved eniem into a monorepo, the goal was to let agents work across the boilerplate, CLI, and docs without losing context between repositories.
That made development easier. It didn’t tell me whether people wanted to pay for the product.
I don’t want to turn zero buyers into a confident explanation of what went wrong. It doesn’t tell me whether the problem was the offer, the way I presented it, or whether enough people even found it. It does mean I can’t treat the amount of code I built as evidence of demand.
That’s the part I want to take seriously before doing another big rebuild.
Why make it public and archive it?
Keeping the code behind a paid offer no longer makes sense to me. I’d rather make the work available for people to read and learn from than keep selling access to a project I’m moving on from.
eniem.dev now says “free & open source” and links to the GitHub organization.
The archive is intentional. I’m not announcing a new phase of active development for eniem, and I don’t want the public repositories to imply that. They preserve the project as it stands, including the unreleased experiment.
If you’re curious about how it was put together, the code is there. If you want to follow what I’m building next, that’s TStack.
The idea continues with TStack
TStack is a rebrand and an expansion of the eniem idea.
The boilerplate is still part of it, but “Next.js SaaS boilerplate” no longer describes the whole thing I want to work on. My focus is building AI-native products, and the application’s starting code is only one part of that work.
The direction for TStack is an AI engineering stack: an engineering harness, agent skills and workflows, and an agent-ready SaaS boilerplate. A remote agent workflow is also part of the plan, not something I’m announcing as available here.
I’m planning a substantial TStack v2 rebuild, including a brand-new boilerplate built from scratch. The unreleased eniem v2 in the archive is not that rebuild.
That’s a direction, not a finished release. Changing the name and broadening the idea won’t answer the questions that eniem left open.
Fewer product bets, more discovery
For now, I’m pausing big product bets. TStack will be my only product.
The question eniem left me with is not whether I can build the software. I built a paid product, and nobody bought it. Before the next bet, I need to look beyond building: who the work is actually for, and how it reaches them.
I know that sits awkwardly beside a plan for a substantial v2 rebuild. Having a direction for TStack doesn’t mean I should disappear into implementation and assume the result will find an audience.
I want to spend more time on discovery and teaching. More blog posts and videos about what I’m learning while building with AI. More effort helping people understand my work, rather than only adding to the code behind it.
Making eniem public doesn’t turn it into a commercial success. It does let me close that chapter without hiding the work.
The archive is available on GitHub. The next chapter is TStack.