The questions tenants ask first
Tenant FAQ.
Tenant FAQ.
Money, hardware, security, contracts.
Twenty-plus questions, organized by topic. If your question is not here, email Doug directly or fill the reservation form. Real person reply within two business days.
Pricing & capacity
How reservations and pricing work.
How is capacity priced?
Per-deal. Pricing depends on GPU SKU, term length, hub location, workload type, and your specific reservation profile. We do not publish hourly rates because two tenants reserving 64 GPUs for 3 years can land at meaningfully different prices. The reservation form gives us enough information to come back with a sized number within two business days.
What contract length is required?
Reservations start at 12 months. Most tenants reserve 24 to 36 months; multi-year terms earn meaningfully better unit economics. Hubs are not built for spot or short-burst usage; if you need 200 GPUs for an afternoon, an on-demand spot market is a better fit.
What capacity sizes can I reserve?
Standard reservation tiers are 8, 16, 32, 64, 128, and 256 GPUs at a single site. Larger reservations split across multiple hubs. Anchor sites support 320+ GPUs; smaller property hubs typically max at 128. We size to your workload during the reservation conversation.
Do reservations come with capacity guarantees?
Yes. ARO reserve up fronts the GPUs in your reservation; they are not shared in a multi-tenant pool. Performance is predictable, wait time is zero, and the capacity is dedicated for the term of the reservation.
What is the cancellation policy?
Reservations are commitments. Early termination terms are negotiated in the definitive agreement and typically require either a defined break fee or substitution of a comparable-value workload. We do not lock you into something untenable; we do require commitment proportional to the capacity we hold.
Can I get on a wait list for upcoming hubs?
Yes. If a hub at a specific location, vertical, or compliance posture is not yet online, the reservation conversation can include priority placement when matching capacity activates. Reach out and we will keep you in the queue.
Hardware
What runs in our hubs.
What GPUs does ARO offer?
The default GPU at every site is the NVIDIA RTX PRO 6000 Blackwell with 96 GB GDDR7. For training-class workloads at anchor sites we offer H100 and H200 nodes. Final SKU recommendation depends on your workload profile and is set in the Letter of Intent.
Can I run 70B-parameter models on a single GPU?
Yes. The Blackwell-class card has 96 GB of GDDR7 and native FP4 precision, enough for 70B-parameter inference on a single card with KV-cache headroom for production-realistic concurrency. No model-parallel sharding required for that class of workload.
What network performance can I expect?
100 GbE site backhaul with redundant fiber paths. NVLink high-speed fabric inside the rack. Sub-10 millisecond tenant-to-hub round-trip latency targets. We design for the workload type you're running and document the latency profile in your reservation.
What software stack runs on the hub?
Production stack supports TensorRT-LLM, vLLM, SGLang, NVIDIA Triton Inference Server, NVIDIA MONAI for healthcare, Kubernetes orchestration, and standard containerized inference workflows. Custom stacks are accommodated where the workload requires.
Is the hub single-tenant or multi-tenant?
Single-tenant by default. You receive dedicated nodes, not shared. Performance, security, and noisy-neighbor risk are bounded by your reservation. Multi-tenant configurations exist for smaller reservations on shared anchor sites; we will note that explicitly if your reservation lands there.
What about training versus inference?
ARO hubs are inference-optimized at most sites. Anchor sites with H100 or H200 fabric configurations can support training-class workloads at scale, but we are not built to compete with hyperscale training fabrics. If you are training a foundation model from scratch, CoreWeave or Lambda are likely a better fit. If you are fine-tuning, doing LoRA, or running production inference at scale, we are a strong fit.
Security & compliance
The compliance and security posture.
Is ARO SOC 2 compliant?
SOC 2 Type I is in flight, with the first report targeted alongside the first deployed hub. SOC 2 Type II is sequenced 12 months after Type I. ISO 27001 is sequenced for regulated and international workloads. Current security posture is documented and available under NDA on request.
Can ARO sign a HIPAA Business Associate Agreement?
Yes, on a per-deal basis. The hub architecture is HIPAA-ready by design (single-tenant, AES-256 at rest, TLS 1.3 in transit, audit logging). The BAA is executed alongside the tenant agreement for healthcare workloads.
What does single-tenant isolation mean in practice?
Dedicated GPU nodes physically reserved for your workload, private VLAN handoff at the demarc, no shared neighbors at the host level, encrypted storage, and access controlled by your IAM policies. Tenant separation is at the node level, not the workload level.
What encryption do you support?
AES-256 at rest for storage, TLS 1.3 in transit for network. Optional confidential-computing add-ons (TEE-protected GPU workloads) where the workload requires. Key management can be tenant-managed via your KMS or ARO-managed depending on the deal.
Will I have audit logs?
Yes. Audit logs are retained per the contract, can be forwarded to your SIEM, and are available for compliance review. Healthcare and regulated tenants typically receive immutable audit trails as part of the BAA or compliance addendum.
What about data residency and geographic constraints?
ARO hubs are deployed across a U.S.-distributed footprint. Tenants with residency requirements can specify the geographies in scope; ARO sites compute to qualifying hubs. International expansion follows tenant demand.
SLA & operations
Uptime, support, and what happens when things go wrong.
What SLA do you commit to?
Tier I sites target 99.671% availability, Tier II 99.741%, Tier III 99.982%. Each reservation is sized to a tier appropriate to the workload. The SLA is codified in the definitive agreement, not a marketing claim.
How do I reach support?
Through a real person. ARO operations is 24/7 monitoring; tenants reach a named account contact during business hours and an on-call contact off-hours. No support tickets, no chatbots, no support queue. Doug Brough or David Tyre answers commercial questions directly.
What happens if my workload is degraded?
ARO operations detects most degradation before tenants do. If you observe a problem, escalation is direct to the on-call engineer. Documented incident response, defined response times by SLA tier, and post-incident reports for tenants on request.
Will my workload be migrated if a hub fails?
For tenants with workload portability requirements, ARO supports failover to redundant hubs in the network. The failover model and recovery time depend on tier and reservation profile; documented in the agreement.
What hardware vendors stand behind the hubs?
Dell PowerEdge servers with Dell ProSupport and 5-year hardware warranty at every site. NVIDIA GPUs under standard manufacturer warranty. Motivair cooling under their own warranty. ARO is a single point of contact; we manage all vendor escalations.
Commercial & contracts
How agreements work.
What does the contract process look like?
Initial conversation, sized reservation proposal in two business days, Letter of Intent in five business days, definitive agreement in 30 to 60 days. Equipment ordering and capacity allocation follows the definitive agreement.
Can I negotiate terms?
Yes. Standard terms exist as a starting point; meaningful negotiation is normal for enterprise reservations. Material commercial points (SLA tier, payment terms, exit conditions, custom compliance language) are negotiated based on your specific requirements.
What payment terms apply?
Net 30 from invoice is standard. Annual or quarterly prepayment can earn additional discount. Custom payment structures (milestone-based, ramp-aligned) are negotiated for larger reservations.
Can I assign the contract to a successor?
Yes, with ARO consent (which is not unreasonably withheld). Tenant M&A is normal; the contract is structured to support successor entity assignment without renegotiation of material terms.
What if I need to expand mid-term?
Capacity expansion mid-term is supported subject to availability at your hub or in the network. Expansion can be added under the existing agreement; pricing reflects the marginal capacity added, not a renegotiation of the original.
Question not on the list?
Ask Doug or David directly.
If your specific question is not above, ask it on the reservation form or send it directly. Doug Brough or David Tyre answers personally within two business days. Real person, no chatbot, no support ticket.
- 2 business day responseReal person, every inquiry.
- Letter of Intent within 5 daysSized reservation if there's a fit.
- Direct phone access(303) 803-7355 reaches Doug.