HolyDC Infrastructure

HolyCode data centers and AI-agent leasing on owned capacity

This page defines the physical infrastructure layer of HolyCode: capacity rollout roadmap, SLA tiers, agent-leasing models, and governance processes for infrastructure capital decisions.

Version

v0.1 (Infrastructure Draft)

Publication Date

March 5, 2026

Status

Pilot Planning -> Capacity Launch

HolyDC Core Principles

  • • HolyCode scales software and physical infrastructure as one business model.
  • • HolyAgent is available in three operating modes: local, managed HolyDC, and hybrid.
  • • Clients lease not only compute but an operating layer with SLA, monitoring, redundancy, and support.
  • • Infrastructure revenue improves DAO treasury resilience and accelerates product scale.

Capacity Rollout Roadmap

Phased HolyDC deployment plan

Phase Timeline Capacity Objective Expected Output
Phase 0: Pilot Site 0-6 months 0.5 MW Launch managed hosting baseline and SLA operations First B2B/B2G contracts and validated unit economics
Phase 1: Scale Pods 6-18 months 1.0-2.5 MW Expand dedicated pod and private cluster offerings Infrastructure ARR growth and multi-pool capacity reserve
Phase 2: Multi-Site 18-36 months 3.0+ MW Regional multi-site rollout and cross-region resilience Enterprise-grade HolyDC footprint with contractual SLA classes

SLA and Service Tiers

How clients lease agents in HolyDC

Tier Availability Compute Footprint Support Target Segment
Shared Agent Cloud 99.5% Shared pool with usage limits Business-hours Pilots, small teams, early-stage launch
Dedicated Agent Pod 99.9% Dedicated pod/GPU pool 24/7 critical incidents Continuous B2B workloads
Private Agent Cluster 99.95% Isolated cluster + custom network policy 24/7 + technical account Enterprise/B2G and compliance-sensitive workloads

Client Activation Flow

From onboarding to production operation

  • 1. Client completes onboarding in Daenerys and creates an organization workspace.
  • 2. Deployment mode is selected: local / managed HolyDC / hybrid.
  • 3. LLM provider keys and HolyAgent role packs are connected.
  • 4. SLA tier, compute limits, and settlement contour are assigned.
  • 5. Monitoring, usage reporting, and recurring billing cycle are activated.

Infrastructure Governance Contour

Decisions routed through DAO process

Scope Decision Mechanism Cadence
HolyDC site CAPEX allocation Treasury proposal + on-chain vote As needed
SLA tiers and tariff updates Product RFC + governance approval Quarterly
Regional rollout of new sites Risk/legal review + DAO resolution By readiness gates