Capacity request checklist

This page is the fastest way to get aligned. If you send us the information below, we can scope feasibility, identify the critical constraints (power, fiber, latency, security), and propose delivery milestones.

If you are coming from hyperscaler procurement, use the procurement-oriented wrapper here: /procurement/rfp-checklist/.

Who this is for

Enterprise and hyperscaler teams planning inference capacity
Investors and partners evaluating execution discipline and risk controls

Minimum requirements (send this)

Workload and performance

Inference workload: text / embeddings / image / video / agentic / mixed
Latency target: region(s) and any hard (p95/p99) requirement you have
Concurrency: expected QPS or concurrent sessions at peak
Burst behavior: expected spikes and ramp time

Data and networking

Ingress/egress: expected bandwidth and traffic shape
Connectivity needs: private connectivity vs public internet; preferred carriers (if any)
Data gravity: where your datasets live and how they must be accessed

Reliability and operations

Availability expectations: maintenance windows, acceptable downtime posture
Redundancy: single-site vs multi-site; N+1 expectations
Support model: preferred incident comms channel and cadence

Security and compliance

Tenant model: dedicated suite vs shared
Security controls: access requirements, audit logging expectations
Compliance targets: any requirements we must design toward (stated as targets)

Preferred (if you have it)

Region priorities: “must-have” vs “nice-to-have”
Contract shape: expected term length, ramp profile, and expansion options
Any hard constraints: export controls, data residency, supply constraints

Template you can copy/paste

company: ""
contact: ""
workload:
  type: "inference"
  modalities: ["text"]
  regions: ["EU", "APAC"]
  latency:
    priority: "low_p99"
    notes: ""
  concurrency:
    peak_qps: ""
    burst_profile: ""
networking:
  ingress_egress_gbps: ""
  private_connectivity: false
  data_residency: ""
reliability:
  redundancy: "n_plus_1_target"
  maintenance_windows: ""
  incident_comms: "email/slack/other"
security:
  tenancy: "dedicated_or_shared"
  audit_logging: ""
  compliance_targets: []
commercial:
  term: ""
  ramp: ""
  expansion: ""

What happens after you send this

Feasibility pass: identify constraints that will dominate schedule and cost.
Design targets alignment: map requirements to baseline targets.
Milestones proposal: phased delivery milestones tied to commissioning validation.
Next artifacts: requirements document, delivery plan, and an initial risk register.

How we define “ready”: /procurement/commissioning-gates/

Next: read the deployment model at /getting-started/navigation/.