CLI

Push. Deploy. Done. Permissionless AI-Cloud infra. Your code, your hardware.

[CLI @clidotcloud]

Excited to support @traderclawAI as they scale their autonomous agent ecosystem.

TraderClaw is building across:

Signals
Analysis
Gateway
Execution
and always-on agent workflows

That kind of system needs infra that can scale with it.

Agents need compute. CLI helps power it.

[TraderClaw @traderclawAI]

We’re excited to be working with @clidotcloud on one of the most important layers for agent infrastructure: scalable compute.

CLI has been helping us explore GPU-backed infrastructure that can support real agent usage at much larger volume.

[CLI @clidotcloud]

Sovereignty is not a software feature because everything starts with hardware.

You cannot govern your way into decentralization if the machines aren't yours, the boot process is not verified, and the provider can pull the plug at anytime.

[Startup Archive @StartupArchive_]

Brian Armstrong explains how he built Coinbase on nights and weekends while working at Airbnb

Brian first advises those who are currently employed to not build your project on company hours or on your company laptop:

“If you build it on company time or on the company hardware, the company probably owns the IP.”

Then he describes his schedule for working on Coinbase while still working full-time at Airbnb.

“I would often work [at Airbnb] until 7pm. I’d come home, eat dinner, and then I would work from 8pm to midnight. I would do that maybe 3-4 days a week on weekdays. And then on the weekend I’d work Sunday afternoon for 7-8 hours.”

Brian did this consistently for about a year and a half until Coinbase was far enough along for him to get seed funding from Y Combinator.

“It sucked. I mean I was tired after the full day of work [at Airbnb]. But this is where determination comes in… At that moment in time, I was in my late 20s, and I was like, ‘I really want to try to build something important in the world.’”

When asked how he maintained friendships during this time, Brian replies:

“I was pretty intense about it. I would say I sacrificed friendships for it. It’s not like I was just never responding to people, but I’ve seen this happen to various people. They get to a certain point in their life. Sometimes they turn a certain age where they thought they would have more done by then or maybe someone in their family passes away and they’re like, Oh my god, time is finite. It’s precious. And something happens where they’re like, ‘I’m going to get this done, no matter the cost.’”

Brian tells those out there who might be in a similar situation:

“Go hard at it. Finish your book. Launch your thing. Just start doing stuff - and even if you don’t know what to do, just do anything, because action will produce information and it’ll help you get to the right thing.”

Video source: @StevenBartlett (2022)

[CLI @clidotcloud]

There's a common piece of advice: "Want to write better code? Read good code."

Curious how that statement changes now with AI writing most of the code and good code becoming less and less, because the cost of maintaining bad code went down.

[Ilir Aliu @IlirAliu_]

AI in robotics gets all the attention right now, but sometimes the most interesting work is very practical.

Viet built a small vision system that counts potatoes on a conveyor belt. No giant dataset. No huge model. Just a clear problem and a smart setup.

He used Ultralytics’ ObjectCounter, trained a tiny YOLO11 nano model, and because there was no potato dataset, he annotated a single frame with SAM 2 and trained from that. One frame. Still works across the whole video.

It is a good reminder that useful AI in industry often looks like this.
Focused. Lightweight. Solves a real task.

If you work in manufacturing or robotics, these small systems are usually the fastest wins. They save time, reduce errors, and do not need massive infrastructure.

Nice work, Viet.

His projects:
https://t.co/1TSrwcKGCW

—-

Weekly robotics and AI insights.
Subscribe free: https://t.co/dsa6wcvq6n

[CLI @clidotcloud]

Japan recently committed $12B to build a sovereign AI factory in Kagoshima with 1 GW of power. Entirely domestically controlled.

Their stated reason: "AI computing power is a fundamental pillar of national security and economic competitiveness."

Nations are spending billions to own their compute.

And CLI is the only crypto native project with sovereign bare metal infrastructure and federal compliance.
https://t.co/3LRvG0l9N2

[CLI @clidotcloud]

HPE made the distinction clearly:

A lot of so called "sovereign" cloud products were not built for sovereignty from the start. They are older systems with security and compliance layers added later.

Many are legacy systems stitched together from multiple vendors, or public cloud stacks reworked after the fact.

That is the difference.

Sovereign by design means security is built in from day 1. Sovereign by retrofit means controls are added later to satisfy a checklist.

One is architecture. The other is security theater.

At CLI, we built security into the system from day 1.

https://t.co/xJHjU6zCiz

[CLI @clidotcloud]

62% of organizations say sovereignty and privacy risks are the biggest factor slowing their AI projects in public cloud.

Not cost.
Not performance.
Sovereignty.

And AI makes this worse, training and inference pipelines move sensitive data across jurisdictions organizations can't control.

The more AI you run, the more sovereignty matters.

https://t.co/NyFL0gZj0B

[CLI @clidotcloud]

In 2025 we are giving agents wallets.

In 2026 we are giving them autonomy.

But we are still deploying them on infrastructure where the hosting provider has more access to the agent's environment than the developer who built it.

Sovereign inference means little if someone else still controls the machine it runs on.

[CLI @clidotcloud]

Crypto’s original thesis was simple:

1. Remove intermediaries.
2. Own your assets.
3. Verify, do not trust.

Today’s reality is much different.

- Most dApps run on AWS.
- Validators rely on a handful of cloud providers.
- Many so called "decentralized" systems can be shut down by a single terms of service update.

We decentralized the ledger but we centralized the infrastructure beneath it.

Sovereign compute is the path forward.

[CLI @clidotcloud]

In crypto, everyone talks about technology moats.

Almost no one talks about compliance moats even though they're just as hard to build, take years to earn and can’t be replicated overnight.

- SOC 2 Type II.
- FedRAMP Moderate.
- NIST 800-207 Zero Trust.
- NSA/CISA hardening at the admission layer.

These are multi-year, multi audit validation processes.

As CLI operates under these certifications, the gap widens.

Changing the competitive landscape.

[CLI @clidotcloud]

Sovereignty Watch #2

- Sovereign cloud spending hits $80B in 2026, up 35.6%. https://t.co/wSs1mX5gdD

- Microsoft expands country specific, compliance driven sovereign cloud services for clients with strict data residency and security requirements.
https://t.co/HGdPObZjN7

- Gartner estimates 20% of workloads shifting from global hyperscalers to local providers as governments demand stronger regional control and data security. https://t.co/CZ4hwkn8Wq

- Forrester predicts multiple major cloud outages in 2026, suggesting that large scale outages may become the new normal.
https://t.co/sfBcp0veNK

[CLI @clidotcloud]

CLI exists because we could not find what we needed.

We needed sovereign compute. Real bare metal. Zero trust. No surveillance.

We looked everywhere:

- AWS GovCloud: shared infrastructure dressed up as compliance.
- Defense contractors: process heavy, architecture weak.
- Self-hosted Kubernetes: requires a team most companies cannot afford.

Every option forced a tradeoff. Security or simplicity. Scale or control.

No one delivered enterprise security and operational clarity in one system.

So we built it.

SOC 2 Type II validated. FedRAMP Moderate. Zero Trust by design.

And the platform is live today.

https://t.co/wIxCdJUqF3

[neo•gio @neogio3d]

This is part of the reason we created @clidotcloud. US government employees should be using hardened, bespoke local AI models and infra.

[CLI @clidotcloud]

Neoclouds are a $23B market that didn't exist 2 years ago.

It is growing 69% annually.

CoreWeave alone has a $55B contract backlog. This is the fastest growing infra sector in tech and crypto has been completely absent from it.

This changes with: https://t.co/k0JHxqjJrD

[CLI @clidotcloud]

The US is spending more on AI infrastructure in 2026 than the Apollo program, interstate highways, and broadband buildout combined.

Neoclouds (Specialized cloud providers built specifically for AI workloads) went from $0 to $23B in two years.

Private cloud grew to $242B.

CLI stands out as a crypto native infrastructure company strategically positioned to capture this upside onchain.

[CLI @clidotcloud]

Sovereignty Watch #1

- Azure was down twice this week. Config change lead to 10+ hours of cascading failures across regions.

- NSA released Phase One and Phase Two of the Zero Trust Implementation Guidelines:

Zero Trust means continuous verification of every user, device, and application. "Never trust, always verify." The DoD deadline is: FY2027.

https://t.co/6RfiBS5Ncf

[CLI @clidotcloud]

The American compute buildout is underway.

The question is whether it runs on infrastructure we control or infrastructure we're renting.

CLI is building for sovereignty.

More soon.

[CLI @clidotcloud]

America is rebuilding its industrial base. Semiconductors. Energy. Defense. AI.

But there's a bottleneck most people aren't watching closely enough:

Compute infrastructure.

The chips are useless without sovereign systems to run them on. 🧵

[CLI @clidotcloud]

Reindustrialization isn't just factories and chips.

It's the compute layer underneath everything else.

Sovereign AI. Defense modernization. Critical infrastructure.

All of it needs a foundation that isn't rented.
We're building that foundation.