FUNDING DESK · Portugal · Controlled agent infrastructure
Granite
A stack from modular energy-adjacent data centers to agent orchestration, emphasizing customer control.
Company website ↗First-party material retrieved
Last retrieval：2026-10-09
Evidence gaps：Product and features · Pricing · Customer cases · Technical documentation
Separately arranging energy, facilities, hardware, storage, networking, serving and agent runtime.
Supply, construction and operating delivery determine whether control beats existing cloud alternatives.
The following is editorial analysis based on public material. Inferences and open questions are labeled in the text. Funding is not evidence of revenue or product-market fit.
Product evidence checked 2026-10-09
01
What the product does
The site describes dedicated compute, GPUs, storage, networking, runtime and compliance layers, with hardware flexibility and customer-held keys. Speed and security claims were not field-verified.
02
Users, buyers and demand
AI teams requiring data, geographic or dedicated-resource control are plausible buyers. This is infrastructure procurement; lightweight prototypes may not need the whole stack.
03
The actual workflow
The described path places modular facilities near energy, then runs models and agents on a common stack. Energy, installation, isolation, operations and maintenance require joint acceptance.
04
Pricing and unit economics
The site offers owning infrastructure or consuming network services, without full public prices. Ownership brings capital and upkeep responsibilities; services require capacity and assurance cost comparisons.
05
Adoption evidence and gaps
Public material establishes architecture and routes to market, not independent deployment times or sustained customer load. Contractual ownership and effective administrative control need confirmation.
06
Competition and defensibility
Energy access, installation and orchestration could create combined advantages. Clouds, colocation and self-build are substitutes; practical portability needs migration tests.
07
How to read this round
Early capital supports stack validation without proving construction speed or power availability. Accepted projects and continuing workloads are better milestones than advertised capacity.
08
Where it could fail
Permitting and site conditions can delay delivery, and hardware needs long-term service. Customer-held keys without recovery plans can add operational burden.
09
What you can take from it
Explain control through responsibility: who owns keys, maintains systems and bears downtime. Deliver energy, asset and runtime boundaries together.
10
What to watch next
Watch construction time, usable capacity, customer loads and operating cost. Compare ownership and consumption separately on contracts, recovery and exit cost.