Plan the budget. Define the scope.
Explore hosting and project scenarios, then work with an engineer to confirm requirements and obtain a written quotation.
Three planning scenarios. One scoped proposal.
Tell us your workload — we'll size your tier.
Sliders & toggles below. The tier card highlighted in the section below auto-updates as you choose.
Review workload measurements, licensing, security requirements and recovery objectives with an engineer.
Illustrative monthly budget
Example capacity and scope to discuss
- 2 vCPU · 4GB RAM · 50GB NVMe
- Deployment region to confirm
- Identity and access requirements to review
- TLS, edge and backup requirements to review
- Support channels and response targets to agree
- Tenancy requirements to discuss
- Regulatory requirements to review
- Accelerator requirements to discuss
Illustrative monthly budget
Example capacity and scope to discuss
- 16 vCPU · 64GB RAM · 1TB NVMe
- Network isolation and tenancy to scope
- Segmentation and access controls to design
- Encryption and backup policy to agree
- Support coverage and response targets to agree
- Failover design and recovery testing to scope
- Regulatory requirements and evidence to review
- AI integration requirements to scope
Illustrative monthly budget
Example capacity and scope to discuss
- 64 vCPU · 256GB RAM · 4TB NVMe
- Multi-site resilience requirements to review
- Workload isolation and access policy to design
- Private connectivity requirements to scope
- Key ownership and encryption design to review
- Service-level terms agreed per engagement
- Monitoring coverage and escalation plan to agree
- GPU requirements and availability to confirm
- Compliance requirements scoped per engagement
- Service review cadence to agree
- Service ownership and contacts to agree
Got a number in mind?
Explore an illustrative configuration for your monthly budget. Modelled capacity and workload fit need engineering validation; this tool does not reserve resources or provide a quotation.
Project budget examples.
Ranges are planning examples. Delivery dates, scope, hardware and third-party costs require a written proposal.
| Engagement | Illustrative range |
|---|---|
| Marketing / lead-gen site | $6,500 — $14,000 |
| Customer portal | $18,000 — $55,000 |
| AI-powered application | $25,000 — $75,000 |
| Migration off public cloud | $9,800 — $48,000 |
| Azure Local deployment | $185k — $720k |
Pricing, answered.
No. The amounts and configurations are illustrative planning examples, not quotations or approved offers. A written proposal confirms price, capacity, availability, scope and commercial terms.
Bandwidth allowances, transfer charges and overage handling must be confirmed in your written proposal. This page does not establish a zero-egress-fee commitment.
The proposal and signed agreement define term length, billing, renewal, cancellation and handover. Confirm these terms before committing.
A useful comparison needs your workload, utilization, licensing, support, migration and transfer costs. We can assess those inputs with you; no savings percentage or performance parity is promised here.
Hardware, licensing and bundled solutions need a current quotation. Confirm availability, specification, lead times and support before procurement.
Get a number tied to your project.
Use the estimator to prepare a planning scenario. An engineer will validate the requirements before issuing a quotation.