Three paths to own
your AI stack.
Every Avalon deployment runs the same software. The choice is where the hardware lives, who owns it, and how you want to scale. Cloud infrastructure is billed direct from vendors to Avalon with no markup.
Three deployment options. One software stack.
Every client gets the same stack. The choice is where the hardware lives. Swift's default recommendation is colocation: Avalon owns the hardware and gets real redundancy without needing a server-ready building. Cloud is always available as a starting point; a move to owned hardware requires no software rebuild.
| On-premises | Colocation | Cloud | |
|---|---|---|---|
| Hardware owner | Avalon | Avalon | Provider |
| Cost pattern | Upfront, low monthly | Upfront + rack fee | No upfront, highest monthly |
| Local AI inference | Yes, owned GPUs | Yes, owned GPUs | Rented or via Swift |
| Data sovereignty | Highest | High | Lowest |
Six server roles behind one gateway.
Same names on-premises, in colo, and in the cloud. Runbooks and monitoring work identically everywhere. Avalon holds the ArcVault root key from day one in every option. Swift's access is scoped, logged, and removable at any time.
| Role | What it does |
|---|---|
| ArcGate | Firewall, VPN, network zones, DNS |
| ArcHelm | Kubernetes, Avalon web and API, Surface |
| ArcData | Postgres (client and stylist profiles), Neo4j (knowledge graph), ClickHouse (session analytics), object storage (hair assets, renders) |
| ArcVault | Keys, secrets, Ledger. Avalon holds root key from day one in every option. |
| ArcRig | GPU inference: hair visualization rendering, texture transfer models, style recommendation, fine-tuning |
| ArcBuild | CI runners, preview environments, agent build lanes |
Cloud infrastructure costs, billed direct, no markup.
These costs apply during the build phase for all options, and as the full ongoing cost for Option 3 (cloud-first). All accounts registered to Avalon. Figures verified against DigitalOcean and Cloudflare current rates (Sept 2026); re-confirm at proposal time.
| Cost item | Phase | Monthly | Who pays |
|---|---|---|---|
| Dev AI toolingAPIs, Claude Code, Copilot, CI, per developer on the engagement | During build | $1,000 / dev | Avalon |
| Cloud infrastructure (build phase)App/API, Postgres, Neo4j, ClickHouse, storage, CDN | During build | ~$695 | Avalon |
| Cloud infrastructure (post-launch)Scales with user base and rendering load | Post-launch | ~$1,300+ | Avalon |
On-premises and colocation hardware (Options 1 and 2).
Hardware is identical across on-prem and colo. Colocation adds a monthly rack fee; the client's building costs are removed. Get vendor quotes before any number goes into a proposal. GPU hardware is priced separately in Section 5.
| Tier | Users / Agent lanes | Server hardware | Colo monthly (half rack, 5 kW) |
|---|---|---|---|
| Small | Under 25 users, 1-2 lanes | ~60% of Standard | Market rate, 2-3 local quotes |
| Standard | 25-75 users, 3 lanes | $30,000-$91,000 | Market rate, 2-3 local quotes |
| Large | 75+ users, 6+ lanes | ~175% of Standard | Market rate, 2-3 local quotes |
GPU options for the Hair Intelligence Engine.
GPU hardware powers Avalon's Hair Intelligence Engine: real-time visualization rendering, texture transfer model inference, style recommendation, and fine-tuning on Avalon's style catalog. GPU prices must be re-verified the week each proposal is sent.
| GPU memory | Runs well (4-bit quantized) |
|---|---|
| 64 GB (2x RTX 5090) | 70B-class models: style recommendation, cataloging, structured drafting |
| 96-192 GB (1-2x RTX PRO 6000) | Texture transfer models, 70B at higher quality, several models simultaneously |
| 384 GB (4x RTX PRO 6000) | Multiple large models serving many agent lanes, concurrent rendering, and fine-tuning in parallel |
Frontier API baseline: what the platform costs today.
What Avalon pays for AI before any owned inference hardware. Frontier API and SaaS tooling scale linearly with team and agent count. They do not decrease as usage grows; unlike owned hardware, they carry no fixed ceiling.
The ownership argument.
The core case for buying hardware rather than renting cloud GPUs indefinitely. Scenario: Standard ArcRig build vs. renting equivalent H100 compute from DigitalOcean through Swift.
| Comparison | DO base rate | 2x GPU 24/7 (base) | Cost to Avalon |
|---|---|---|---|
| H100 on-demand (DO) | $4.41/GPU/hr | $6,440/mo | $8,370/mo |
| H100 reserved 12-month (DO) | $3.26/GPU/hr | $4,760/mo | $6,190/mo |
| Standard ArcRig owned (2x RTX PRO 6000) | $39,000 one-time hardware | ~$1,100/mo amortized | |
Own or borrow from Swift: start anywhere, move anytime.
Avalon can borrow any component from Swift's Grid until usage justifies owning it. The software stack is identical regardless of which option is chosen. Moving from borrowed to owned requires no rebuild at any point.
| Component | Avalon owns | Borrowed from Swift |
|---|---|---|
| Brain (ArcRouter + models) | Runs on Avalon ArcRig; all client data stays in Avalon infrastructure | Avalon apps call Swift's Grid through ArcRouter; no GPUs needed |
| Vault (keys, secrets, Ledger) | Runs on Avalon ArcVault nodes | Swift hosts it; Avalon receives SDK and scoped keys |
| Surface workspace | Runs on Avalon ArcHelm | Workspace on Swift's Surface instance |
| Build pipeline | Runs on Avalon ArcBuild nodes | Builds run on Swift's runners, billed per use |
Proposal and re-quote rules.
Hardware costs are planning estimates; get vendor quotes before any number goes into a final proposal. Labor retainers are quoted separately.
| Item | Rule |
|---|---|
| GPU prices | Re-verify the week the proposal is sent. RTX PRO 6000 prices have been volatile; September 2026 figures are a floor, not a ceiling. |
| Server hardware | Re-confirm within 30 days. Get vendor quotes before any number goes into a final proposal. |
| Colocation rack fees | Get 2-3 local quotes per proposal. Rates vary by market and facility tier. |
| Cloud compute | Confirm ArcBuild node count against Avalon's actual agent lanes before finalizing. Section 3 figures are based on verified DO rates (Sept 2026). |
| Markup basis | Cloud accounts billed at vendor rate with no markup. Labor retainers are a separate line item in every proposal. |