Turkey's eighth unicorn arrived without raising a round

HubX, an app studio based in İzmir, has become Turkey's eighth unicorn. It was founded in 2022 by Cem and Kaan Ortabaş, which makes the run from incorporation to a billion-dollar valuation four years long. According to Adapty, whose subscription infrastructure the studio uses, it got there without taking external funding.

That last detail comes from a vendor rather than from HubX or the financial press, so treat it as reported rather than confirmed. The valuation itself is not in dispute.

The table is the story

Put the eight side by side and the interesting column is not the one you expect.

Dream Games got there in three years and Loom in one, so four years is not a record. What separates HubX is what it did not do. Trendyol, Getir, Hepsiburada, Peak, Dream and Insider all scaled on rounds of venture capital, with the growth targets and the ownership dilution that come attached. HubX is reported to have scaled on subscription revenue from apps people chose to pay for.

The public numbers are consistent with that. The studio reports more than 300 million users; independent trackers put annual recurring revenue near $100 million as of April 2026; its Nova AI app alone has passed 50 million downloads. That is a business funded by its customers.

What the model actually looks like

Strip away the valuation and the method is unglamorous. Publish many small apps rather than betting everything on one. Ship quickly and let install and retention data decide which ideas get a second version. Monetise by subscription so revenue compounds instead of arriving once. Kill what does not work without ceremony.

None of that requires a billion dollars of validation to be worth copying. It requires being able to ship to a store repeatedly and survive what happens after launch — which is the part nobody writes about.

What we learned running the same model, much smaller

We publish our own apps too. Twelve of them are live on the App Store, alongside seventeen products on CodeCanyon. The scale is not comparable and the point is not to compare it. The point is that the failure modes are identical at every size, and you only learn them by having your own name on the listing.

• Store review rejects on grounds the guidelines describe only in the abstract. Subscription screens, restore-purchase flows and what counts as a "free trial" account for most of it. You learn the real rules by being rejected, not by reading.
• Subscription billing breaks quietly. A receipt that fails to validate does not surface as an error; it surfaces as a user who paid and has no access, three days later, in a support ticket.
• Crash rate decides whether a release survives. A version that crashes for two per cent of sessions will bury the feature it shipped, and you will not see it in the reviews until the rating has already moved.
• The environment is invisible. Our software runs in installations we cannot reach and never configured. Every incompatibility arrives as a message from someone who is already annoyed.

Those four lessons cost us releases. They are also the reason our client work is built the way it is: upgrade safety before features, rollback proven before launch, support answers measured in hours. We did not adopt those standards because a methodology recommended them. We adopted them because our own products punished the alternative.

What it means if you are building an app

HubX is worth celebrating for the obvious reason — a studio from İzmir reached a billion dollars by making things people pay for. But the useful reading is narrower than the headline.

It says the distribution problem is solved for everyone equally. The App Store does not care where you are incorporated. It says subscription revenue can fund growth that used to require a round. And it says the constraint has moved: not capital, not access, but whether you can ship repeatedly and hold quality while you do it.

The hard part was never writing the app. It is everything that happens after it is live.

That is the part we do for a living — architecture, release, and the maintenance that follows. If you are taking an idea to a store, or you have shipped one and the second release is where it started hurting, tell us what you are building.