The wait’s been long, the whispers constant. Everyone in the ICP ecosystem knew it was coming—what they didn’t know was when, or just how much it would deliver. That moment finally arrived on 3 June 2025 in Zurich, as the Internet Computer marked its fourth anniversary with the launch of something it’s been quietly building toward for years. On World Computer Day, at the World Computer Summit, Caffeine AI was introduced—not with fanfare, but with function.
The first output? A smiley face web page. Followed by a blog styled like Medium. Then, a tennis lesson booking app. And finally, a birthday party registration page for ICP’s fourth anniversary. All created in under 23 minutes. No IDE. No copy-pasting. No traditional coding. Just a conversation between a human and an AI assistant that builds apps in real time—and deploys them directly to the blockchain.
This was no gimmick. Caffeine AI is now live in alpha, and it’s already sparking buzz across Web3, developer circles, and among founders long fatigued by technical bottlenecks. Powered by Motoko 2.0—the first AI-native programming language—and running natively on the Internet Computer Protocol (ICP), the tool allows anyone to build working apps using plain language. No prior dev experience required. No infrastructure worries. Just describe what you need, and refresh the screen.
Dominic Williams, founder of DFINITY, opened the demo referencing a quote by Steve Jobs: “Have faith in people—they’re good and smart. Give them tools, and they’ll do wonderful things with them.” That’s the backbone of Caffeine’s mission. Williams explained that while there are around 35,000 web engineers and over 15 million fullstack developers in the world, Caffeine is meant for everyone else—the ones who can describe a product, but not build it. Now they can.
He also framed Caffeine as part of a sovereign cloud for AI. This isn’t just an assistant—it’s an entire platform. Personal blogs, business sites, marketing pages, internal dashboards—they’re all on the table. And once built, these apps run on-chain with built-in safety and security features, backed by the resilience of the Internet Computer network.
Joseph Hurtado from Granata Consulting praised the live demo, calling it one of the first times he’d seen blockchain-deployed apps built through English prompts—successfully, and live. “We saw web apps running on the IC that were created based on English language prompts, similar to Replit, but where the code actually was deployed to a blockchain!” he noted. The system used Motoko and TypeScript under the hood, though users don’t interact with the code directly. Hurtado also asked whether Rust might be supported in the future—an indication of growing curiosity about extending the language stack.
Aaron Biebert from ICP United called Caffeine “extremely and sincerely optimistic.” His team, involved in projects like The Swop and ICP Hub US, had long felt held back by a lack of Web3 engineers. “Caffeine AI feels good,” he said. “It works fast. 700 lines of code in a few minutes.” He also pointed to built-in safety features and on-chain backups as major advantages, especially compared to other AI code assistants that risk enabling “vibe coding”—building fast without proper security modelling.
Biebert believes that once users understand how to prompt with intent—bringing a vision for features, style, and function—Caffeine can output highly capable applications. “It’s a conversation,” he wrote, “and you’ll have to bring a vision for what needs to be in the app.” He sees Internet Identity playing a key role in future logins, but also hopes Caffeine expands to offer more login options to make adoption easier for builders and their audiences.
The idea that Caffeine can act as both builder and deployer is what’s setting it apart. Harley Kimball, co-founder of Bug Bounty Village, shared a cautionary tale of an app he built using other tools—aggregating security researcher profiles from HackerOne and GitHub. Despite rapid development, it was hacked twice due to misconfigured database views and lax authentication features. It was an example of how even skilled users can run into trouble when rushing without guardrails.
Dom responded directly: “Caffeine fixes probs like this. Vibe coding not necessary. Self-writing. Apps are tamperproof.” That claim—of a system that prevents users from making common mistakes—resonated widely.
The tool’s simplicity is striking. You just chat with Caffeine. It writes the code, deploys it, and you refresh to see it working. No database setup. No separation between logic and storage. On the Internet Computer, logic lives in the data, allowing updates and migrations to happen in sync. When you modify your app, the AI understands and shifts the structure without breaking the chain.
And there’s more coming. Dom confirmed during the stream that an App Store is in the works—where creators can share, sell, or clone each other’s applications. It’s the sort of ecosystem play that Web2 nailed with mobile—and Web3 has been chasing for years. Users will also be able to configure custom domains, or opt for quick something.caffeine.ai names out of the box.
Of course, early access is still invite-only. Caffeine is in alpha. But even now, applications range from basic proof-of-concept builds to full-scale platforms. Dom’s presentation showed that this is not theoretical—it’s real. The apps created weren’t static prototypes; they ran on the network, using Internet Identity for authentication and built entirely through natural language.
As expected, the stream drew a flurry of commentary. Some users tried to diminish the showcase by pulling early demo clips and posting them without context. Dom took it in stride, noting that their criticism might need rethinking once Caffeine is broadly available. “Some fudders have been extracting the app orientation from the livestream where I created the smiley page and posting that was the demo,” he said. “Not sure what they’re going to do when it’s launched in not very long.”
Matt Laird asked about the platform’s impact on cycles—the compute fuel that powers apps on ICP—and whether the system would burn enough to make tokenomics deflationary. Dom responded, “If Caffeine creates millions of apps on ICP, there will be a lot of cycles being burned.”
@gizzycrypto, who appreciated the demonstration but wondered why nothing had been said about pricing or the business model. In response, Dom revealed a key feature that hadn’t yet been highlighted: Caffeine will have its own App Store. This marketplace will allow users to publish their creations for others to use—free or paid—opening up monetisation options for developers and creators without needing separate infrastructure. It also offers clarity on how Caffeine may sustain itself in the future: by letting usage drive value.
Others asked about domain features and potential tokens. @TradingFilet, shared their enthusiasm about Caffeine’s capabilities but also posed two practical questions. First, whether Caffeine would eventually have its own token, and second, how it would handle compute costs—especially if users would need to hold ICP to power their apps. Dom responded that while the full model is still being finalised, Caffeine will operate on a freemium structure. Published apps will require cycles, ICP’s compute fuel, but this complexity will be kept behind the scenes for mainstream users—delivering accessibility without forcing token management onto everyone.
On the user feedback side, @AmSpeed01 suggested integrating domain configuration into the UI—Dom replied that it’s already built in. @TradingFilet called the platform “really really incredible,” and raised the big question: will Caffeine eventually have its own token? While specifics are still under wraps, what’s clear is that Caffeine is built to scale.
As for what happens next, applications for early access are open at join.caffeine.ai. And the energy around it hasn’t cooled. Dom summarised the vibe at WCS25: “Caffeine was inspired by a quote by Steve Jobs… and now anyone who can communicate in natural language, on desktop or mobile, can use it to build or customise apps without technical skills.”
Whether it’s a personal blog, a marketplace, or a scheduling system, Caffeine is offering something that feels deceptively simple: a prompt, a reply, and a working app. All running on-chain. All owned by you.
Community Discussion