I'm very curious how much revenue this is generating.
Next is a full stack framework and Keystone is a CMS built on top of Prisma and GraphQL. Keystone was created by this Australian company called Thinkmill. They have used it to help businesses build custom backend systems for more than a decade. But it needed to be deployed separately from Next and they were using emotion css for their dashboard and I wanted to use Tailwind/Shadcn. So first, I had to make the Next Keystone Starter that brought in Keystone into Next so each SaaS is just 1 Next app with a built-in storefront, GraphQL API, and dashboard.
Once that was built (and it took a while tbh), I started to build the Shopify and Toast alternative. But the itch to get these built quickly and autonomously had me working on the harness in the past months and now that is nearly complete.
Here is the e-commerce[2] and restaurant[3] repos. They have a link to deployed demos you can check out as well.
As far as revenue, I don’t feel comfortable relaying that right now. We have other revenue streams like fractional CTO where companies give us equity to manage all their tech and that is quite hard to quantify. Before Openfronts being built, I built Openship, and e-commerce OMS and that has exceeded 5M orders processed since its inception in 2019. That’s not counting orders by businesses running it on-prem.
I actually posted about this vision on HN[4] when I launched Openship and the response is what kept me building.
2. https://github.com/openshiporg/openfront
Second, take this for what it is: your product may not be compelling in its current form. Building it to many different markets will not make it compelling. If you had a stronger revenue, please share it. This sounds incredibly thin.
Third, dont mistake building the same thing 20 times for different verticals for bonifide software skills. When a SWE builds the thing they have built before its usually to learn a language which is the easiest part of software. There is a reason a common adage in software is "9 women cant make a baby in a month". Breath is no replacement for depth.
In the end, I built Openship and Openfront for my e-commerce business and then turned them into SaaS. All the revenue for these are just a cherry on top of our existing e-commerce businesses.
And I worked with Next and Keystone long before AI came along. Check my GitHub commits if you need some back story.
And I’m not building these 20 SaaS to prove I have bonafide SWE skills. I’m building them because I plan to have my own gyms, hotels, grocery stores down the line powered by these SaaS. SWE to me a means to an end and that’s to have many different businesses.
Okay but, you know this isn't a quality metric right? These models are incredibly biased towards positive confirmation of the prompt. I could give them nearly any repo and they would sing the praises of the best parts, if I asked.
This sounds a bit like psychosis.
Crazy how you guys blindly trust proprietary apps where you can’t even read the code but asking you to read open-source code is psychosis?
Wow okay, I'm a huge open source advocate, I run hardly anything closed source. No one here was talking about that, this is your own weird segue.
> but asking you to read open-source code is psychosis
But you didn't ask that. You told me to get an agent to read it (actually, not even read it, make its own quality assessment for me).
That's a massive difference, and if you consider them to be the same thing, then yes, my statement stands.
It’s actually the whole premise of my open source alternative directory called Opensource Builders[0].
We’re also very bullish that the chat interface is the universal UX now. Instead of sifting through the dashboard to change a product price or sell in a new region, you can use the built-in agent and just tell it to do that. Every Openfront comes with an MCP server that interfaces with the API so the agent can literally do anything you can do using the dashboard and API. This is where an agent running the business autonomously comes in.
And even then if you’re not satisfied with the backend API for each vertical, these Next apps can be forked and adapted to tightly fit your business instead of you messing with configs, you can make the app your own.