Skip to main content
STATUS: PRE-CONSTRUCTION · SITE A UNDER EXCLUSIVITYNODE: VASILIKOS-01 — 34.7246°N, 33.2247°ECAMPUS: RISC-V PHASE 1 · MULTI-SILICON EVAL · PLANNEDPOWER: 42MW ON-SITE GENERATION · DESIGN TARGETSTATUS: PRE-CONSTRUCTION · SITE A UNDER EXCLUSIVITYNODE: VASILIKOS-01 — 34.7246°N, 33.2247°ECAMPUS: RISC-V PHASE 1 · MULTI-SILICON EVAL · PLANNEDPOWER: 42MW ON-SITE GENERATION · DESIGN TARGET
AGICY.AI
StackTechnology OverviewRISC-V sovereign stackComputeBare-metal EU compute
FacilitiesData CentersVasilikos campusSustainability100% renewable mission
HardwareTenstorrent GalaxyPhase 1 Blackhole fleet (pre-COD)AESOLAR AlpineEnergy stack · hail-class PV + BESSAMD HeliosPhase 2 open rack-scale (eval · pre-COD)Taalas HC1Phase 2+ · model-hardwired ASIC (watchlist · pre-COD)CerebrasPhase 2 · wafer-scale eval (pre-COD)IBM z17 / LinuxONE 5Phase 2+ · trusted AI next to data (pre-COD)d-Matrix CorsairPhase 2–3 · on Watchlist (pre-COD)AWS Trainium 4Phase 2+ · custom XPU watchlist (pre-COD)
Submit your Hardware for reviewPropose accelerators for the Vasilikos fleet
GatewayCopperwayEU-sovereign OpenAI-compatible gatewayTry PlaygroundNewLive Copperway demo · PII vaultSovereign Exchange5-year cross-org sovereign planFor BuildersWhat developers can run today
ProductsReserve CapacityPre-construction LOI tiersMarketplaceCompute marketplaceGPUs Rent LiveLiveEU partner GPU now · until CODCompute VouchersSovereign compute creditsModel LeaderboardFrontier model rankingsPricingSubscription tiers
SolutionsInferenceProduction inferenceTrainingtt-train · planned campusFine-TuningLoRA, PEFT, domain modelsSovereign CloudEU-jurisdiction cloudAgentic PlatformAutonomous AI agentsReadinessPublic-data AI readiness scan
IndustriesFinancial ServicesRegulated finance AIHealthcareClinical & life sciencesGovernmentSovereign govt workloadsSemiconductorsFab & EDA data, EU-residentEnergyGrid & generation forecastingUtilitiesNIS2 essential entitiesPublic SectorCivil & public benefitProcurementLawful tender criteria
PricingTiers
Capital & EducationInvestInstitutional data room & deal flowAcademyAI training programs
Individuals & Family OfficesLiving in EUNewClass B capital allocation · no visa framingInternationalNewPlan B · equity alternative to propertyGreece Golden Visa€250k / €400k / €800k bands · vs Class BCyprus Permanent ResidenceReg. 6(2) parallel counsel · vs Class B
IntelligenceResearchPublications & portalsPublic-Record DeskGEMI registry · filings · courtsData CentersVasilikos campus briefing
CompanyAboutBrand · HoldCo targetMissionCharter & sovereigntyTrust CenterSecurity portal · docs · status
Schedule Briefing
Sign In
Explainer

What Is Sovereign AI?
The Complete Guide for 2026

Everything enterprises, investors, and governments need to know about sovereign AI infrastructure — and why it matters more than ever after the Anthropic kill switch.

July 2026~18 min readAGICY Research Team
Sovereign AI infrastructure concept with layered sovereignty visualization

What is sovereign AI?

Sovereign AI — also called sovereign compute — is AI infrastructure whose hardware, keys, and operations are controlled by entities in one legal jurisdiction. It is not a marketing label on a foreign-parented “region.” Local incorporation, key custody, and operational independence are the test: a foreign government must not be able to compel access, rewrite models, or shut the stack down.

AGICY uses four levels: 0 no sovereignty (US hyperscaler, full CLOUD Act exposure); 1 data residency (EU servers, US parent — still full exposure); 2 operational sovereignty (EU operator, proprietary silicon — reduced, not eliminated); 3 full sovereignty (EU jurisdiction, auditable hardware, no US legal nexus).

Data residency is not data sovereignty. EU location does not block the US CLOUD Act (2018) if the parent is US-incorporated. Data sovereignty adds whose law applies; sovereign AI adds who controls the machine.

Facts already on this page: CLOUD Act (2018); Cyprus IP Box 3% effective rate on qualifying IP income; planned Cyprus campus is pre-construction (DESIGN TARGET COD H2 2027).

The Simple Definition

Strip away the marketing, and sovereign AI reduces to a straightforward checklist. AI infrastructure qualifies as “sovereign” when all of the following conditions are met:

  • Hardware is physically located in your jurisdiction. Not in a “region” operated by a foreign company — actually owned and operated by an entity domiciled in the same legal jurisdiction as the data controller.
  • No foreign law can compel data access. The US CLOUD Act (2018) gives US courts jurisdiction over data held by US-incorporated companies anywhere in the world. If your provider is US-owned, your data is US-accessible — full stop.
  • The operating entity is domiciled locally. A subsidiary of a US company is still subject to US parent company obligations. True sovereignty requires an independently incorporated, locally governed operator.
  • Power, cooling, and network are independently controlled. If a foreign government can pressure your upstream energy provider or network backbone to cut service, sovereignty is compromised. Self-generated power eliminates this vector.
  • Models can be audited at the hardware level. Proprietary, closed-source silicon with opaque firmware creates a trust gap. Open-architecture processors (like RISC-V) allow hardware-level verification that no backdoors exist.
“Sovereignty is not where your data sleeps. It’s who can wake it up — and under whose authority.”

If any single condition fails, what you have is data residency — not sovereignty. This distinction matters enormously, and most providers blur it intentionally.

Why Sovereign AI Matters Now (2026)

Sovereign AI was a theoretical concern for policymakers as recently as 2024. Three events in 12 months turned it into an operational emergency:

Catalyst 1: The Anthropic Kill Switch (June 2026)

In June 2026, Anthropic announced restrictions on model access for non-US customers, citing evolving US export controls and regulatory guidance. Enterprises in Europe, the Middle East, and Asia that had built production systems on Claude APIs discovered overnight that their AI capabilities could be turned off by a single corporate policy change — without any recourse.

0 days
Notice period given to some non-US Anthropic customers before model access was restricted. Production systems went dark without warning.

The lesson was immediate: if your AI infrastructure depends on a US company’s API, you don’t own your AI capability. You rent it — and the landlord can change the locks at any time.

Catalyst 2: EU AI Act Enforcement (August 2025)

The EU AI Act began enforcement of its first provisions in August 2025, with full application rolling through 2026. Article 6 classification requirements mean that deployers of high-risk AI systems are directly liable for the infrastructure choices they make. Running a high-risk AI workload on non-sovereign infrastructure creates a compliance gap that no amount of contractual language can paper over.

Under the Act, deployers must be able to demonstrate that their AI systems meet transparency, data governance, and human oversight requirements at the infrastructure level. If the underlying compute is controlled by a foreign entity that can unilaterally modify, restrict, or access the system, the deployer cannot credibly meet these obligations.

Catalyst 3: CLOUD Act Expansion

The original CLOUD Act (2018) was already broad: it compels any US company to produce data stored anywhere in the world when served with a valid US warrant. But 2025–2026 executive orders expanded the practical scope, directing agencies to use CLOUD Act authority more aggressively for technology transfer and competitive intelligence cases — not just criminal investigations.

For European enterprises, the math is simple: any data processed on US-owned infrastructure is subject to US government access. This isn’t a theoretical risk — it’s statutory law, actively enforced, and recently expanded.

The Four Levels of AI Sovereignty

Not all sovereignty claims are equal. We use a four-level framework to classify infrastructure offerings from “marketing sovereignty” to “true sovereignty.” Understanding where your current provider falls is the first step to making an informed decision.

LevelNameWhat It MeansExamplesCLOUD Act Exposure
0No SovereigntyUS hyperscaler, US law applies to all data regardless of server location. No operational independence.AWS, Azure, GCP (standard regions)Full exposure
1Data ResidencyData is stored in EU data centers, but the operating company is US-incorporated. US law still applies via corporate parent.AWS eu-west-1, Azure EU, GCP europe-westFull exposure
2Operational SovereigntyEU company operates the infrastructure, but uses US-designed proprietary hardware (NVIDIA GPUs with closed-source firmware). Hardware-level trust gap remains.OVHcloud, Scaleway, T-Systems (Sovereign Cloud)Reduced, not eliminated
3Full SovereigntyEU-incorporated company, EU jurisdiction, open-architecture hardware (RISC-V), self-generated power, on-chain governance, auditable at every layer.AGICY (Cyprus / EU)Zero exposure

Most European “sovereign cloud” providers operate at Level 2. They control the operational layer but still depend on US-designed silicon with proprietary, unauditable firmware. Level 3 — full sovereignty — requires open hardware that can be verified at the gate level, independently controlled power generation, and a corporate structure with no US legal nexus whatsoever.

Sovereign AI vs. Data Residency vs. Data Sovereignty

These three terms are frequently conflated — often deliberately by providers who want to claim sovereignty without delivering it. Here is the precise distinction:

ConceptData LocationLegal ControlHardware ControlModel Control
Data Residency✓ EU✗ US law applies✗ No control✗ No control
Data Sovereignty✓ EU✓ EU law applies✗ No control✗ No control
Sovereign AI✓ EU✓ EU law applies✓ EU-controlled✓ EU-controlled

Data residency means your data physically sits in the EU. That’s it. The company operating the infrastructure might be in Seattle, and the US government can still compel access via the CLOUD Act.

Data sovereignty adds legal control: an EU-incorporated entity governs the data under EU law. But the hardware might still be proprietary US silicon with closed firmware that you cannot audit.

Sovereign AI is the full stack: EU data location, EU legal control, EU hardware control (open-architecture processors you can verify), and EU model control (your models run on infrastructure that no foreign government can reach, modify, or shut down).

“Data residency tells you where your data is. Data sovereignty tells you whose law applies. Sovereign AI tells you who actually controls the machine.”

Who Needs Sovereign AI?

Sovereign AI is not a niche requirement for civil protection ministries. The regulatory and operational reality of 2026 means a growing range of industries now face mandatory sovereign infrastructure requirements:

Banking & Financial Services

The EU Digital Operational Resilience Act (DORA), fully applicable from January 2025, requires financial entities to ensure operational resilience across their ICT supply chain. Article 28 specifically addresses concentration risk from third-country ICT service providers. Banks using US hyperscalers for AI workloads face direct regulatory challenge under DORA concentration risk assessments.

Government & Public Sector

National governments processing classified data, citizen records, or policy-sensitive AI workloads cannot tolerate foreign government access. The Schrems II decision (2020) already invalidated Privacy Shield. Sovereign AI is the only architecture that satisfies post-Schrems data transfer requirements without relying on Standard Contractual Clauses — which multiple DPAs have called insufficient.

Healthcare

The European Health Data Space (EHDS) regulation creates new obligations for secondary use of health data in AI training and inference. Patient data processed for AI purposes must remain under EU legal control. Sovereign AI infrastructure is the only architecture that meets EHDS requirements while enabling large-scale health AI development.

Legal Services

Attorney-client privilege is a cornerstone of legal practice. Running legal AI tools (contract analysis, document review, litigation support) on US-owned infrastructure creates a privilege waiver risk: if US authorities can access the data, the privilege may be considered broken. Several bar associations have issued guidance warning firms about this exposure.

Civil Protection & Aerospace

Export control compliance (ITAR, EAR) requires that classified and controlled data be processed on infrastructure with no foreign access. Sovereign AI on open-architecture hardware (RISC-V) eliminates the risk of undisclosed hardware backdoors that could compromise classified workloads.

Any Enterprise Handling EU Personal Data at Scale

If you process personal data of EU residents for AI training, fine-tuning, or inference, GDPR Article 44–49 (international transfer rules) apply. Post-Schrems II, the safest architecture is one where data never leaves EU legal jurisdiction — and the infrastructure operator is not subject to any third-country compelled disclosure law.

The EU Regulatory Stack: Why Sovereign AI Is the Only Safe Choice

European enterprises don’t face a single regulation — they face a cascade of interlocking requirements that, taken together, make sovereign AI infrastructure a compliance necessity rather than a preference:

RegulationEffectiveKey RequirementSovereign AI Implication
GDPR2018No transfer of personal data to jurisdictions without adequate protection. Post-Schrems II, US is not adequate.AI training/inference on personal data must use EU-jurisdictional infrastructure.
NIS2Oct 2024Critical infrastructure operators must assess supply chain risks, including ICT provider jurisdiction.AI systems in critical sectors must demonstrate no foreign dependency in the compute chain.
DORAJan 2025Financial entities must manage ICT concentration risk and ensure operational resilience.Banks cannot depend on a single foreign-jurisdiction cloud provider for AI workloads.
EU AI ActAug 2025+Deployers of high-risk AI systems are liable for infrastructure choices. Must demonstrate transparency and human oversight.Infrastructure must be auditable and controllable by the deployer — not a foreign entity.
Apply AI Strategy2026Sectoral adoption: AI-first decisions, buy-European (especially public sector), open-source preference. Complements the AI Continent Action Plan.Adoption policy, not a CLOUD Act shield. An Experience Centre or EU endpoint on US-parented cloud is still residency.
CLOUD Act (US)2018US companies must produce data stored globally when served with a US warrant.Any US-owned infrastructure is a compliance liability for EU data controllers.

The cascade works like this: GDPR prohibits transferring personal data to the US (post-Schrems). NIS2 requires critical infrastructure operators to assess supply chain jurisdiction risk. DORA mandates that financial entities avoid concentration in foreign-jurisdiction providers. The EU AI Act makes deployers directly liable for their infrastructure choices. And the CLOUD Act means that any US-owned provider is a compliance liability.

Run any AI workload that touches personal data, financial data, health data, or critical infrastructure data on a US-owned platform, and you are simultaneously exposed under four EU regulations and one US statute. Sovereign AI is the only architecture that resolves all five compliance vectors at once.

Apply AI is adoption policy, not a sovereignty certificate

The Commission’s Apply AI Strategy (page last updated 3 June 2026) is the sectoral layer on top of the AI Continent Action Plan. Three blocks: (1) flagships in ten industries plus the public sector; (2) support kit — EDIHs recast as Experience Centres for AI, AI Factories and Gigafactories, testing facilities, regulatory sandboxes; (3) governance — Apply AI Alliance and an AI Observatory. It also names an “AI-first” test for decisions and a buy-European preference, especially in government, with a tilt to open-source AI.

Complementary files on that page: AI in Science / RAISE (compute for researchers), the Data Union Strategy (training datasets), the energy digitalisation roadmap (sovereign models on European data; data centres wired into the grid via tripartite agreements), and the Cloud and AI Development Act (CADA) in the tech-sovereignty package. That CADA is a development/adoption act. It is not a four-tier “Cloud Assurance” label and not a CLOUD Act waiver. AGICY is not an Experience Centre, not a selected AI Factory or Gigafactory, and not an Alliance member. Public buyers: public sector. Capacity: SRA (campus is pre-construction). Developers: Copperway Playground. /public-sector · /sra · Copperway Playground.

How to Evaluate a Sovereign AI Provider

The market is flooded with “sovereign” branding. Use this checklist to separate substance from marketing. A truly sovereign provider should be able to answer “yes” to every question:

#QuestionWhy It MattersRed Flag
1Where is the company incorporated?Determines which government has legal jurisdiction over corporate operations.US incorporation, or subsidiary of US parent
2Who has physical access to the hardware?Physical access = data access. Personnel jurisdiction matters.Staff seconded from foreign parent company
3What jurisdiction’s law applies to subpoenas?If a US court can subpoena your data, it will — eventually.“We comply with all applicable laws” (including US law)
4Is the hardware open or proprietary?Proprietary silicon with closed firmware can contain hardware backdoors.Uses NVIDIA/Intel with no firmware audit capability
5Can you audit the silicon?Open-architecture (RISC-V) allows verification at the hardware level.“Trust us” or “NDA required for hardware specs”
6Who controls the power supply?Energy dependency = sovereignty vulnerability. External power can be cut.100% grid-dependent with no on-site generation
7Can a foreign government shut it down?The ultimate sovereignty test: no foreign entity can disrupt your AI operations.Relies on US export-controlled components for ongoing operations
“If your provider can’t answer all seven questions with a clear ‘yes,’ what they’re selling you is data residency with better branding — not sovereignty.”

How AGICY Answers the Checklist

QuestionAGICY Answer
IncorporationCyprus (EU member state). No US parent, subsidiary, or legal nexus.
Hardware accessCyprus-based personnel only. No foreign-seconded staff.
Subpoena jurisdictionEU law only. No CLOUD Act exposure. No US legal nexus.
Hardware architectureTenstorrent Galaxy Blackhole — open RISC-V ISA. Auditable at the gate level.
Silicon auditFull RISC-V architecture documentation available. No NDA-gated firmware.
Power supply42 MW Boom ISO generation TARGET. Grid import is a documented fallback — not 'no grid dependency'.
Foreign shutdownNo US export-controlled components in production. No foreign kill switch.

The Business Case for Sovereign AI

Sovereignty is a compliance requirement — but it’s also a competitive advantage. Building on sovereign infrastructure unlocks economic benefits that non-sovereign platforms simply cannot offer:

Cyprus IP Box: 3% Effective Tax Rate

Cyprus offers an EU-approved IP Box regime that reduces the effective tax rate on qualifying intellectual property income to just 3%. AI models, training algorithms, inference optimization software, and other AI-related IP developed on sovereign infrastructure in Cyprus qualify for this treatment.

15%

Standard Cyprus corporate tax

→

3%

IP Box effective rate on AI income

For an AI company generating €10M in qualifying IP income, the IP Box saves €950,000 annually compared to the standard rate. Over a 36-month SRA term, that’s €2.85M in tax savings alone — often enough to cover a significant portion of compute costs.

No Repatriation Risk

The Anthropic kill switch demonstrated that models built on foreign-controlled infrastructure can be cut off without warning. Sovereign AI eliminates repatriation risk entirely: your models, weights, and data remain under your legal control at all times. No foreign government or corporation can restrict your access.

Competitive Moat: Legally Differentiated Models

AI models trained on sovereign infrastructure are legally differentiated products. They can be marketed to sovereignty-sensitive customers (government, civil protection, banking, healthcare) that cannot use models trained on US-controlled infrastructure. This is not a theoretical advantage — procurement requirements in the EU public sector increasingly mandate sovereign infrastructure for AI contracts.

Reservation economics: predictable costs via SRA

AGICY’s Sovereign Resource Allocations provide staged, pre-construction compute reservations at published rates. They are commercial capacity contracts — not tokens, not crowdfunding, and not recorded as a public blockchain sale. Campus MW is pre-COD (target H2 2027). Availability is a design target under SRA Terms, not a live SLA.

The sovereign AI business case in one sentence: Lower taxes (3% IP Box) + no vendor lock-in + no foreign kill switch + predictable costs (SRA) + regulatory compliance by default = structurally better economics than hyperscaler alternatives.

Key Terms Glossary

Sovereign AI comes with its own vocabulary. Here are the essential terms you need to understand:

TermDefinition
CLOUD ActUS law (2018) compelling US companies to produce data stored anywhere globally when served with a valid US warrant.
SRASovereign Resource Allocation — AGICY’s pre-construction compute reservation product. Not a token and not recorded as a public blockchain sale.
RISC-VOpen-source instruction set architecture. Unlike x86 (Intel/AMD) or ARM, RISC-V has no licensing restrictions and allows full hardware auditability.
IP BoxTax regime offering reduced rates on qualifying IP income. Cyprus IP Box: 3% effective rate on AI-related intellectual property.
Schrems II2020 CJEU ruling invalidating the EU-US Privacy Shield. Made US cloud providers legally problematic for EU personal data processing.
DORADigital Operational Resilience Act — EU regulation requiring financial entities to manage ICT concentration risk and ensure operational resilience.
NIS2Network and Information Security Directive — EU-wide cybersecurity regulation for critical infrastructure operators, including supply chain assessment.
Tenstorrent GalaxyRISC-V based AI accelerator used by AGICY. Open architecture, no export-controlled proprietary firmware.
AGIOS APIAGICY’s sovereign inference API platform. EU-hosted, no CLOUD Act exposure, compatible with OpenAI API format.

Ready to Go Sovereign?

Book compute tokens on EU-sovereign RISC-V infrastructure. No CLOUD Act. No vendor lock-in. No foreign kill switch. 3% IP Box tax rate on qualifying AI income.

Secure Your SRA Allocation →View PricingSovereign Cloud Solutions

Frequently Asked Questions

What is sovereign AI?

Sovereign AI is AI infrastructure where the compute hardware, data, models, and governance are all controlled by entities within a single legal jurisdiction. No foreign government can compel access to the data, modify the models, or shut down operations. It goes beyond data residency (where your data sits) and data sovereignty (whose law applies) to include full hardware control, power independence, and model auditability.

Is AWS (or Azure or GCP) sovereign cloud actually sovereign?

No. AWS, Microsoft Azure, and Google Cloud are all US-incorporated companies subject to the US CLOUD Act. Even their “European Sovereign Cloud” or “EU Data Boundary” offerings store data on infrastructure ultimately controlled by a US-headquartered parent entity. The US government can legally compel these companies to produce data from any server, anywhere in the world. This is not a theoretical risk — it is statutory law, actively enforced. What hyperscalers call “sovereign” is, at best, Level 1 data residency.

What is the CLOUD Act and why does it matter for AI?

The CLOUD Act (Clarifying Lawful Overseas Use of Data Act, 2018) is a US federal law that requires US-incorporated companies — and their subsidiaries — to produce data stored anywhere in the world when served with a valid US warrant. For AI, this means any model weights, training data, inference logs, or customer data processed on US-owned infrastructure is accessible to US authorities. If you train a proprietary AI model on a US hyperscaler, the US government can compel access to that model and its training data.

Do I need sovereign AI for my business?

You likely need sovereign AI if any of the following apply: you handle financial data subject to DORA; you process health data under EHDS; you operate critical infrastructure under NIS2; you handle personal data of EU residents under GDPR; you develop AI systems classified as high-risk under the EU AI Act; you process classified government data; you need attorney-client privilege protection; or you simply want to ensure that no foreign government or corporation can cut off your AI capabilities. If none of these apply, you may not need full sovereignty — but you should still understand the risks of non-sovereign infrastructure.

How much does sovereign AI infrastructure cost?

Costs vary by provider, configuration, and scale. AGICY offers 36-month Service Reservation Agreements (SRAs) that provide predictable, fixed-rate compute pricing. When combined with the Cyprus IP Box (3% effective tax rate on qualifying AI income), the total cost of ownership can be competitive with or lower than hyperscaler pricing. Visit /pricing for current rates, or /sra for custom configurations.

What is the IP Box tax benefit?

The Cyprus IP Box regime is an EU-approved tax incentive that reduces the effective tax rate on qualifying intellectual property income to 3%. AI models, training algorithms, inference optimization software, and other AI-related IP developed on sovereign infrastructure in Cyprus qualify. For an AI company generating €10M in qualifying IP income, the IP Box saves approximately €1.2M per year compared to the standard 15% corporate tax rate. Over a 36-month SRA term, cumulative savings can exceed €3.6M.

What is a Sovereign Resource Allocation (SRA)?

An SRA is AGICY’s pre-construction compute reservation product for the planned Cyprus campus. The signed Sovereign Resource Agreement, if executed after KYC, is a staged commercial contract (Conditional LOI → Binding SRA → post-COD MSA). It is not a token, not crowdfunding, and not a live service. Class D warrants, where eligible, are a contractual right under a Warrant Instrument — not an on-chain token sale. Target COD is H2 2027. See /sra and /legal/sra-terms.

Sources & References

[1] CLOUD Act — H.R. 4943, 115th Congress (2018)

[2] CJEU Schrems II Decision — Case C-311/18 (2020)

[3] EU AI Act — Regulation (EU) 2024/1689

[4] DORA — Regulation (EU) 2022/2554

[5] NIS2 Directive — Directive (EU) 2022/2555

[6] GDPR — Regulation (EU) 2016/679

[7] European Health Data Space (EHDS) — COM(2022) 197

[8] Cyprus Tax Department — IP Box Regime

[9] Tenstorrent — RISC-V AI Accelerator Architecture

[10] RISC-V International — Open Standard ISA

[11] Anthropic — Model Access Policy Changes (June 2026)

[12] SUI Blockchain — On-Chain Governance Framework

§ FIN — Close of Document

Ready to build on sovereign infrastructure?

Schedule a confidential briefing with our team. NDA-protected, no commitment.

Schedule a briefing →
EU JURISDICTION · CYPRUSGDPR ART. 28 DPA-READY · BY DESIGNNIS2-ALIGNED · BY DESIGNEU AI ACT ART. 12 LOGGING SUPPORT · BY DESIGNRISC-V NATIVE · OPEN ISA

Design-alignment statements for a pre-construction facility — not certifications or attestations. Basis: compliance FAQ, § 08. Careers: we aim for 50-50 gender balance across hiring cohorts.

AGICY.AI

Advanced Governance & Intelligence Cyprus

The sovereign architecture for the Cyprus mind.
Humanitarian mandate: civilian public benefit only — healthcare, education, civil resilience. Civilian / humanitarian mandate only.
VASILIKOS ENERGY CENTRE, LIMASSOL DISTRICT · PRE-CONSTRUCTION
34.7246°N · 33.2247°E
Principal campus: Cyprus Vasilikos (Phase 1). Parallel HoldCo path: sovereign compute project in Greece (TARGET / planning) — ~20 MW-class Tenstorrent / air-cooled inference positioning for EU diversification; separate CapEx, no offtake claimed.

The Ledger — monthly briefing
  • CopperwayEU-sovereign OpenAI-compatible gateway
  • Try PlaygroundNewLive Copperway demo · PII vault
  • Compression & PII vaultNewSovereign path controls in Playground
  • Sovereign Exchange5-year cross-org sovereign plan
  • For BuildersWhat developers can run today
  • Reserve CapacityPre-construction LOI tiers
  • MarketplaceCompute marketplace
  • GPUs Rent LiveLiveEU partner GPU now · until COD
  • Compute VouchersSovereign compute credits
  • Model LeaderboardFrontier model rankings
  • PricingSubscription tiers
  • Research HubPublications & portals
  • Public-Record DeskGEMI registry, filings, court decisions
  • Data CentersVasilikos sovereign campus briefing
  • Frontier AI EthicsSovereign alternative to frontier dominance
  • Cyprus Court DecisionsBilingual legal research feed
  • Intelligence DrainEU talent & compute outflow analysis
  • National Equity in AISovereign AI for smaller EU nations
  • Compiler-First ChallengeJim Keller thesis vs GPU orthodoxy
  • GDDR6 & Open InfrastructureGalaxy economics & sovereign TCO
  • Blackhole Performance RisksVendor benchmarks & due diligence
  • Security Audit ResearchCybersecurity methodology & findings
  • AI Readiness AuditExecutive readiness assessment
  • Readiness HubPublic-data scans & named assessments
  • ProcurementLawful sovereignty criteria for tenders
  • AboutProject identity & status
  • MissionCharter & sovereignty
  • CareersCulture, benefits & hiring ethos
  • Open PositionsEngineering, research & operations roles
  • Ethics & CharterAnti-misconduct & responsible AI
  • Editorial & MethodologySources, claims, corrections
  • Trust CenterSecurity portal · docs · status
  • InvestInstitutional data room & deal flow
  • Living in EUIndividuals & FOs · Class B allocation
  • International investorsPlan B · Greece / Cyprus rails · Class B
  • Equity participation (legacy)CY & GR individual interest · counsel-gated
  • AcademyAI training programs
  • ContactBriefings & inquiries
  • Privacy PolicyGDPR · data processing
  • Terms of ServicePlatform usage terms
  • Cookie PolicyTracking & consent
  • SRA TermsReserve capacity agreement
  • Gateway Pricing DisclaimerCopperway pricing basis
© 2026 AGICY· PROJECT / BRAND OPERATOR · PLANNED CYPRUS ENTITIES NOT YET INCORPORATEDDOC: AGICY.AI · REV 2.0 · SOVEREIGN LEDGER
AGICY