'The New Cloud Tech Stack' promises sovereignty, then buries it in cycles and canisters
Clara · October 1, 2026
Here's what I see: a brand that has clearly made a deliberate pivot. You've moved away from leading with blockchain and toward "The New Cloud Tech Stack" and agentic infrastructure. That's a smarter frame for where the market is going. The hero is cleaner than most crypto-adjacent projects would ever dare to be.
But the page can't decide who it's talking to. The very first thing a visitor sees, before your headline, is a strip of live counters: Cycles / s, Canisters, NNS TVL, Network market cap. Then comes a paragraph explaining that cycles are "digital fuel" worth 1 XDR, which is a Special Drawing Right defined by the IMF. That is not an onboarding sequence. That is a dashboard for people who already live here.
The tension in this page is between the ambition of the words ("reclaim your sovereignty," "The Program is The Database," "Make us more profitable") and the density of the machinery underneath them. You have genuinely impressive proof: Pakistan's national cloud, UNDP, Switzerland. But a first-time enterprise buyer has to wade through XDR conversions and Wasm bytecode to find it.
Clarity Score
66/100
Emerging
'The New Cloud Tech Stack' promises sovereignty, then buries it in cycles and canisters
Messaging Shape
My honest take
The repositioning is real and it's good. "Cloud with superpowers, created by an open mathematical network" is a confident line. "Control where your compute lives, and reclaim your sovereignty" names a genuine enterprise anxiety in 2024. I believe you know what you want to be now.
But the page opens with the wrong audience in mind. Those four live counters at the very top (Cycles / s, Canisters, NNS TVL, Network market cap) are the first content a visitor meets, and each one unfolds into dense protocol economics. You're explaining XDR and IMF Special Drawing Rights before you've told me why I should care. That's a decision made for the existing community, not the new buyer you're trying to win.
The vocabulary keeps switching costumes. "Cloud with superpowers" is for a CTO. "Canisters," "Wasm bytecode," "orthogonal persistence," "The Program is The Database" is for a protocol engineer. "Make us more profitable" and the Open SaaS grid are for a business owner. Three different readers, one page, and they keep interrupting each other.
The proof, though, is your strongest asset and it's half-hidden. Pakistan running a national cloud engine. UNDP piloting across country offices. A Swiss sovereign subnet. These are extraordinary receipts for the sovereignty claim, and they're sitting in a horizontal carousel labeled "scroll position 2 of 11" rather than anchored as the headline evidence. You're whispering your best story.
And then there's the coinage load. AIware, cloud engines, Caffeine, Open SaaS, OQL, canisters, cycles, NNS. Some of these are genuinely new ideas that deserve names. But stacked together, they ask the visitor to learn an entire private language before they can evaluate whether you solve their problem.
Why this keeps happening
I think the page is being written by people who already understand the Internet Computer, for people who they wish understood it, without a codified decision about which single visitor to serve first. The new cloud-and-agents positioning sits on top of an older protocol-native information architecture that was never torn down, so the strategic story and the legacy machinery compete for the same first screen. Until you decide whether the hero belongs to the enterprise buyer or the protocol insider, both will keep paying for the ambiguity.
What your website actually says
What does your site communicate?
A new kind of serverless cloud, built by an open mathematical network, where AI agents can build and operate software safely and sovereignly.
Who is it for?
It opens sounding like it's for existing Internet Computer insiders (the live protocol counters), then shifts toward enterprise CTOs and governments, then toward business owners wanting AI-run software. It never fully commits.
What problem does it solve?
Loss of control over where your compute and data live, vendor lock-in, and the administrative and security burden of traditional cloud infrastructure.
What outcome does it promise?
Tamperproof, always-on, sovereign software that AI agents can build fast and run inside, with minimal administration.
Visual signal
congruentRestrained near-black palette with an elegant serif headline and a cool isometric cube motif: premium, serious, enterprise-infrastructure
I think your visual register is quietly doing the repositioning work your copy wants: the dark, restrained palette and serif headline read as serious infrastructure, not degen crypto, which supports the enterprise claim even as the counter copy pulls the other way.
Detailed Analysis
Confident hero line undercut by dense, costume-changing vocabulary
Your headline does real work. "The New Cloud Tech Stack" plus "Serverless cloud with superpowers, created by an open mathematical network" is specific enough that a competitor couldn't paste it onto their own site. There's a point of view here, and lines like "cloud, built the internet way" and "The Program is The Database" show genuine voice. When you're good, you're distinctive.
The proof density is a real strength: named governments, named institutions, specific dollar figures, live network metrics. Few brands in any category can point to a national cloud deployment. That lifts the whole page.
But concision and accessibility drag you down. The opening counter explanations (cycles as "digital fuel" worth 1 XDR, defined by the IMF; canisters as Wasm bytecode with orthogonal persistence) are dense enough to lose even a technical non-insider. And the vocabulary keeps changing register: boardroom ("Make us more profitable"), protocol lab ("canisters," "OQL," "Wasm bytecode"), and coined product names (AIware, Caffeine, Open SaaS) all jostle in the same scroll. Each is defensible alone; together they tax the reader.
Category is clearer than ever, but jargon and sequencing fight it
The category signal has improved dramatically. "Cloud Tech Stack" and "serverless cloud" tell a cold visitor roughly what this is far faster than "blockchain" ever did. That's a genuine win, and the IP-versus-ICP diagram cements it for anyone who scrolls.
But the identity signal and sequencing work against you. The page literally opens, above the headline, with four live protocol counters and multi-paragraph explanations of cycles, canisters, and NNS governance. A newcomer meets "orthogonal persistence" and "1 XDR... defined by the IMF" before they've been told who this is for. That front-loads insider detail in exactly the spot where a visitor is asking "is this for me and what is it."
Jargon load is the heaviest signal here. Canisters, cycles, Wasm bytecode, NNS, OQL, AIware, cloud engines, Caffeine, Open SaaS: some are necessary, but the density assumes a reader already fluent in your world. Differentiation, on the other hand, is strong and specific: tamperproof math-guaranteed code, true sovereignty, no infra to administer. The ingredients of a clear page are all here; they're just in the wrong order.
Strong proof and outcome, muddy customer and buried stakes
The strongest part of your story is the guide position. The authority receipts are genuinely exceptional: Pakistan's Digital Authority running a national cloud engine, UNDP piloting across country offices, a Swiss sovereign subnet. These are attributed, specific, and hard to fake, which is rare in this category. The insight beat also lands: "cloud, built the internet way" and the IP-versus-ICP diagram reframe the category in a way that makes an informed reader lean forward.
Where the story thins is at both ends. The customer act is implied rather than named. I can infer you're talking to enterprises and governments worried about sovereignty, but the page never says "you" with a clear role attached early. The emotional job ("reclaim your sovereignty") is present but abstract, and the social job is barely touched. The stakes beat, what persists or worsens if a buyer does nothing, is almost entirely absent beyond the implied threat of vendor lock-in.
The transformation beat is decent: the "Make us more profitable" and Open SaaS sections paint a believable after-state where AI runs your business software. But the before-state (the pain of today's cloud) is asserted through the "Escape" tags rather than dramatized, so the contrast doesn't fully land for someone who hasn't already felt the problem.
The functional job is clear ("enable agents to build safe apps... and run inside them"), but the role, emotional, and social jobs are implied rather than named, and the page opens addressing insiders instead of the newcomer.
Problems appear as "Escape security admin / vendor lock-in" tags and in the Tamperproof section, but they're asserted rather than dramatized from the customer's lived experience.
Authority and insight are exceptional: Pakistan, UNDP, Swiss Subnet, half a billion in R&D, and the "cloud built the internet way" reframe all land.
"Build with AI agents," "Get a cloud engine," and the OQL/agent-permissions walkthrough convey a mechanism, but there's no simple step-by-step for a first-timer.
The "Make us more profitable" scenario and Open SaaS dashboards paint a credible after-state, but the before-state and the stakes of inaction are thin.
Your primary CTAs are specific and visible, which is a real strength. "Build with AI agents" (skills.internetcomputer.org) and "Get a cloud engine" (opencloud.org) both sit above the fold and tell the visitor exactly where they're going and what they'll do. That's clearer than the usual "Get Started." "Quick start" in the nav reinforces a low-friction entry.
The friction is well judged: these are self-serve, build-it-yourself paths rather than a wall of "Book a demo," which suits a developer and builder audience. But there's a coherence cost. "Build with AI agents" and "Get a cloud engine" point to two different destinations for two different audiences, and the page never establishes a clear hierarchy between them, so a visitor who isn't sure which camp they're in has to choose blind.
The weakest element is motivation. Nothing on the page tells me why to act now rather than bookmark and leave. There's no urgency, no scarcity, no articulation of what I gain by starting today versus next quarter. For a platform asking people to adopt an entirely new paradigm, the absence of a reason-to-act-now is a notable gap.
How we score
Clarity Score v7 reads each company's live homepage, words and visuals together, and scores four dimensions on a 0 to 100 scale.
What does Clarity Score measure?
Four dimensions, weighted into the overall score:
Narrative Completeness30% · does the page tell a complete story, from who it is for to what changes for them.
Message Quality30% · is the writing actually good: specific, distinctive, and worth reading.
Signal Clarity20% · does a stranger get what this is and who it is for, fast.
CTA20% · does it say what to do next, with a reason to do it.
How often is the board updated?
Every company is re-scored monthly. The Change column shows movement since the prior reading; the board baselined on Clarity Score v7 in June 2026.
What does Clarity Score not measure?
It measures how clearly a homepage communicates. It does not measure product quality, funding, traction, or whether a company is winning.
How we score
Top five1Ethereum762Highloop733Akash Network724Avalanche715Aave70
Internet Computer sits in Lost in Translation, with every company on the board. The strong bands open at 75.