2
7 Comments

Bootstrapped solo, no funding, 2 years in building an “AI Operating System” instead of another app

What Zyaku actually is now

I didn’t set out to build an “AI Operating System.” I set out to build a fairer creator platform - 80% revenue share, zero follower minimum to earn, real ownership over what you create. But somewhere along the way, the problem got bigger than “creator economy.” We ended up building out identity, commerce, publishing, AI tooling, and resilient infrastructure - all connected, not bolted together.

One thing I’m genuinely proud of: we just shipped Disaster Alert - an offline-first emergency communication system. It works even when the internet doesn’t. Local broadcast queuing, biometric auth, cached safety info - built so people can still reach each other when networks fail. It’s part of a broader “Wellbeing as Infrastructure” idea I’ve been pushing internally - that platforms should protect people, not just engage them.

The honest bootstrapped-founder stuff

No funding means every infra decision is a real tradeoff - we migrated off Replit/Neon to Railway + Cloudflare partly for cost, partly for control

Building solo (then with 2 people) across 10 product domains sounds insane in hindsight, and some days it still does

~2,400 registered users so far, live creator payouts running, and real coverage from international outlets including AP News - earned the hard way, not bought

Why I’m posting this here

I’ve mostly been heads-down building. I want more honest feedback from people who’ve actually shipped things solo/bootstrapped - what worked when you tried to do “too much” at once, and how you knew when to cut scope vs push through.

Happy to answer anything about the stack (React Native/Expo, Node/Express, Postgres/Redis on Railway), the offline-first architecture, or just the mess of building solo without funding.

zyaku.com if you want to poke around.

posted toAvatar for product Zyaku
Zyaku
  1. 1
    2,400 users across 10 domains is a lot of surface area. What’s the one part users keep coming back to most?
    1. 1

      That’s exactly what we’re watching closely. Right now, the strongest signal is around the core workflows where users can actually get something done, rather than just explore features. We’re still early, so I’d rather let the repeat behavior tell us what deserves to become the center of Zyaku

      1. 1
        That’s the right thing to watch. I’d be curious which workflow is actually showing repeat behavior already, even if it’s still too early to call it the center of Zyaku.
        1. 1

          I think the strongest signal may be broader than one workflow. The interesting behavior is when people start using Zyaku for things they’d normally need separate apps for creating, publishing, managing identity and earning, but also the safety side: Safe Space and our offline-first emergency and disaster features.

          The goal isn’t to make users switch between more apps. It’s to see whether one connected system can become useful enough that they keep coming back for different parts of their digital life.

          1. 1
            That’s an interesting distinction — you’re really testing whether the value comes from any single workflow or from the system becoming useful across someone’s digital life. I’d be interested in digging into that a bit more privately. What’s the best email to reach you on?
            1. 1

              Absolutely, that’s exactly the question I’m trying to answer with Zyaku. I’d be happy to dig into it. You can reach info[ at] zyaku [dot ] com Looking forward to the conversation.

              1. 1

                Thanks! I’ve just sent it over.

                Looking forward to hearing your thoughts whenever you have a chance.