This is not a flex post. This is what happens when you stop planning and start shipping.
I run NeuralChain Hub, a small company out of Dubai. Between March 27 and April 17, 2026, we shipped 4 digital products and built a production-grade live broadcasting relay server. None of this was planned as a batch. Each one came from a real problem that needed solving right now, not next quarter.
Here is what we built, why, and what I learned.
Product 1: The Guest (the-guest.org)
My daughter is 13. She needed a period tracker that wasn't designed for adults, wasn't creepy with data, and didn't show her fertility content she shouldn't be seeing at her age. Every app on the market failed at least one of these.
So we built The Guest together. She is the creator behind the product. My wife handles the education side. I handle the technical building.
The website is live at the-guest.org with real users. The app is built in Expo React Native with 62 features including cycle tracking, mood and symptom analytics, calendar, age-filtered recommendations, and full COPPA compliance. Under 13 users never see fertility or mature content. That was a non-negotiable rule from day one.
Stack: React for the website, Expo React Native for the app, Neon PostgreSQL in Frankfurt, NextAuth with verification codes (not Google OAuth, because minors). Both the website and app share the same database and API.
The hardest part was not the code. It was getting the medical logic right. Ovulation calculation must follow cycleLength minus 14. Period records only get created on day 1 of a new cycle. Predictions always use the profile's last period date as the primary source. Get any of these wrong and you're giving someone incorrect health information. That kept me up more nights than any bug.
Product 2: SportzGenesis Arena (sportzgenesisarena.com)
This one I wrote about last week on dev.to. Free sports prediction platform covering IPL, Premier League, Champions League, and World Cup 2026. No gambling, no money, just predictions and points.
58 users after the first week. Built with Next.js, Neon PostgreSQL, Vercel. Two different scoring systems for football and cricket. Match chat, private leagues, 16 badges, festival bonuses.
The interesting thing about building this alongside The Guest is how different the problems are. The Guest is a health product where accuracy is everything and one wrong calculation can hurt someone. SGA is a sports product where engagement is everything and nobody gets hurt if your leaderboard has a minor bug for an hour.
Same database provider, same hosting approach, completely different mindset required for each.
Product 3: The Guest App (Expo React Native)
Same product as the website but native mobile. 62 features, 99% parity with the web version. Onboarding flow, settings, dashboard, tracker, calendar, insights, all of it.
Building the same product for web and mobile simultaneously taught me something. Your API is the product. The frontend is just a view layer. Once the API was solid, the app was mostly about adapting the UI to mobile patterns. Swipe instead of click, bottom tabs instead of sidebar, pull to refresh instead of reload button.
The app is ready for App Store submission. That is a separate process involving Apple review, screenshots, descriptions, and the specific way Apple wants you to explain data collection to users.
Product 4: NeuralChain Hub Digital Products (neuralchainhub.gumroad.com)
While building the tech products, we also launched a Gumroad store with 4 digital products. AI Toolkit, a free lead magnet, a legal bundle for freelancers, and a freelancer starter kit. My wife is the public face of the brand. These are template and guide products for other entrepreneurs.
This was the fastest to ship because Gumroad handles everything. No code, no hosting, no auth. Upload PDF, set price, publish. The lesson here is that not everything needs to be a custom-built platform. Sometimes a marketplace product on an existing platform is the right answer.
The Broadcasting Infrastructure
This is the one that surprised me the most.
A client needed a production relay server for live cricket broadcasting. Venues in different countries stream via SRT to a central relay, which then pushes to multiple broadcast takers including major sports networks and streaming platforms. This is not a hobby project. This is live television infrastructure where downtime means millions of viewers see a black screen.
We set up a Hetzner cloud server in Germany running Nimble Streamer. SRT ingest from multiple venues on dedicated ports. Output via SRT push, RTMP republishing, and MPEGTS to different broadcast partners. Each venue gets its own port. Each taker gets its own output configuration. The server handles protocol conversion, so a venue can send SRT and a taker can receive RTMP without knowing or caring about the difference.
The port convention system was important for scaling. 9900 range for ingest, 10000 range for outputs. First two digits identify the venue, last two identify the taker. When you are managing multiple countries and multiple broadcast partners, this kind of structure prevents chaos.
Total infrastructure cost: about 87 dollars a month for a server that handles production broadcasting for international cricket.
The technical stack for this is completely different from everything else I built. No JavaScript, no React, no databases. Just Linux, streaming protocols, firewall rules, and a deep respect for what happens when a live feed drops during a match.
What ties all of this together
On paper these products have nothing in common. A period tracker, a sports prediction game, digital templates, and broadcasting infrastructure. But they share a few things:
They all solve real problems for real people I know personally. My daughter needed a tracker. My friends needed a prediction game. Freelancers in my network needed templates. A client needed broadcasting infrastructure.
They all run on boring, reliable technology. PostgreSQL, not MongoDB. Next.js, not the framework that launched last week. Ubuntu LTS, not the latest unstable release. Hetzner, not the most expensive cloud provider.
They all shipped imperfect and improved after launch. Every single one of these products had bugs on day one. The Guest had a cycle calculation error that took 3 iterations to fix. SGA had a match sort order bug that showed completed matches above upcoming ones. The broadcasting server needed firewall rule adjustments after the first test stream. None of that matters as long as you ship, listen to feedback, and fix things fast.
The non-technical founder reality
I keep saying I am not a developer because I think it matters for context. Everything described above was built with LLM assistance. I prompt, I read every line of generated code carefully, I test, I debug, I make architectural decisions. The LLM writes the syntax. I make the product decisions.
This is a new way of building things and I think it is underestimated. The bottleneck for most products is not the code. It is knowing what to build, for whom, and why. If you have clarity on those three questions, the code is increasingly solvable with tools.
That said, the broadcasting infrastructure humbled me. Streaming protocols, port management, codec settings, and latency tuning are not things you can vaguely prompt your way through. You need to understand what SRT does differently from RTMP, why keyframe intervals matter for segmented streaming, and what happens when packet loss hits 2% on a live feed. Some domains still require deep understanding even if you are using tools to execute.
Numbers as of April 17, 2026
The Guest: live website with active users, app ready for store submission
SportzGenesis Arena: 58 users, 215 predictions, 6 private leagues, 13 SEO pages
Gumroad store: 4 products live
Broadcasting relay: production server handling live international cricket feeds
Monthly infrastructure cost across everything: under 100 dollars
What is next
Getting SGA to 500 users before World Cup 2026 kicks off in June. Adding push notifications through PWA so existing users actually come back. Writing more SEO content so Google sends organic traffic. Eventually building a white label version of SGA for sports federations and colleges.
For The Guest, the immediate next step is App Store submission and then iterating based on what real users ask for.
For the broadcasting side, scaling the port and venue system to handle multiple concurrent tournaments across different countries.
Thanks for reading. Happy to answer questions about any of these in the comments.
Top comments (1)
If you want to see any of the products live:
the-guest.org (menstrual health tracker)
sportzgenesisarena.com (sports predictions)
neuralchainhub.gumroad.com (digital products)