The first thing you notice on Tulika's homepage is the word itself. Tulika, Sanskrit for paintbrush, sits over a one-line promise: "the first truly personal software platform" [tulika.ai]. There is no enterprise logo wall, no demo video looping a dashboard, no pricing toggle. There is a metaphor, and an invitation: create, share, and remix mini apps tailored to you [tulika.ai]. For a category that has spent fifteen years insisting software must scale to millions to matter, that framing is a small act of resistance.
The bet underneath the metaphor is unusually clean. Tulika is positioning itself as infrastructure for software that serves an audience of one, or maybe a few dozen: the recipe tracker your mother actually wants, the practice log built around your kid's specific swim drills, the invoicing tool shaped to a single freelancer's quirks. The company describes a future "where software is made for all of us, by all of us" [tulika.ai]. The product noun the team has chosen is mini app, and the verbs are create, share, and remix, which together suggest something closer to a creative medium than a SaaS product. Users make a thing. They pass it around. Someone else opens it up and changes it.
That language matters because it sets Tulika apart from the dominant framing of the moment, which is that software creation should be automated end-to-end by a model. Tulika's pitch, at least as stated on its own site, keeps the human in the author's chair and treats the platform as the brush rather than the painter. Whether the underlying construction tools are template-based, code-based, or model-assisted is not specified in the public material, and the company has not disclosed which. The positioning, though, is consumer and expressive rather than enterprise and productive.
Why the bet could be big
The ambient conditions for personal software are better than they have been at any point since the spreadsheet. A generation that grew up customizing Notion pages, building Airtable bases, and stringing together Zapier flows already understands that software is something you assemble, not just something you buy. App stores trained users to expect a tool for every micro-need. What has been missing is a surface where the tool itself can be authored as casually as a playlist, then handed to a friend without a deploy step or an app review queue. If Tulika's remix primitive works the way the homepage implies, with a mini app being forkable the way a Google Doc is copyable, the social loop could be genuinely new.
The upside, if execution holds, is a category that has been promised many times and delivered rarely: end-user programming as a mainstream behavior. HyperCard gestured at it in the late 1980s. Glide, Softr, Bubble, and Replit have each pushed pieces of it forward in the last decade. None has produced the cultural moment where non-developers casually ship software to each other the way they share TikToks. Tulika is implicitly arguing that the missing ingredient was not power but personality: software framed as personal expression rather than as a startup-in-waiting.
The honest counterfactual
What skeptics will say is that the personal software category has a long graveyard, and that the hard part has never been the authoring tool. It has been distribution and durability. A mini app that lives inside one platform's runtime is only as portable as that runtime, and the remix loop only compounds if enough people show up to remix. The bull answer, drawn from Tulika's own framing, is that the unit of creation is small enough (a mini app, not an app) that the bar for a useful artifact is correspondingly low. A weekend project that helps four people is a success in this model, not a failure. If the platform can make those small wins social and visible, the network can build from the bottom rather than waiting for a breakout hit.
There is also a real question about who the first thousand authors are. Personal software platforms tend to attract two very different audiences: tinkerers who would have built the thing in a spreadsheet anyway, and curious non-technical users who need scaffolding the tinkerers find condescending. Threading that needle in onboarding is a design problem more than an engineering one, and it is the kind of problem that tends to reveal itself only after launch.
What to watch
The next twelve months for Tulika will be defined by surfaces the public has not yet seen: the editor itself, the gallery of remixable apps, the social mechanics that turn a creation into something a stranger picks up. The company's homepage is, for now, a thesis statement rather than a product tour [tulika.ai]. The interesting milestones to track are the first public mini apps shared outside the founding circle, any pricing or creator-economy mechanics that emerge (do authors get paid when their app is remixed?), and the kind of community Tulika cultivates in its earliest cohort. Personal software platforms tend to take on the personality of their first hundred users for a long time afterward.
The cultural question Tulika is implicitly answering is whether software, after four decades of being a thing professionals make for everyone else, can become a thing everyone makes for the few people they actually know.
, Viral Bernstein