AI-Native Provisioning
Provision approved cloud resources from a governed catalog — no consoles — with approval workflows and Whale AI sizing. AWS is live today, with Azure and GCP catalog items.
- 0
- AWS services provisioned from the catalog today — EC2 · S3 · RDS · VPC · EFS
- Auto-approve
- Low-risk items within policy; everything else routed to an approver
- Every request
- Written to the audit log and the ITSM change record
The challenge
Self-service provisioning usually means console sprawl and inconsistent sizing, with no guardrails and no record of who provisioned what.
- 01
Engineers hold broad console rights because the alternative is a ticket queue.
- 02
Instances are sized by habit, so over-provisioning is baked in from day one.
- 03
Nobody can say who approved a resource, or whether it was approved at all.
How it works
The data path, end to end
- Step 1:
Teams browse a catalog of approved resources — no cloud console needed.
- Step 2:
Whale AI recommends a size from your inventory and cost history before the request is submitted.
- Step 3:
Approval policy routes the request by cost, environment or resource type; low-risk items auto-approve.
- Step 4:
AWS resources are provisioned live; Azure and GCP items are fulfilled from the catalog.
- Step 5:
Every provisioned resource lands in the unified inventory, cost tracking and the audit trail.
Who it's for
Platform engineering teams and cloud operations who want governed self-service.
Related solutions
Questions
Questions teams ask in the evaluation
Scope, permissions, integrations and what is live today.
01Does this replace Terraform?
No. The catalog is for day-to-day requests that should not need a pipeline change. Foundations and workloads defined as code stay in Terraform — Landing Zone Builder generates the foundation.
02Which clouds can be provisioned today?
AWS: EC2, S3, RDS, VPC and EFS. Azure and GCP catalog items are available for request and approval, with provisioning coverage expanding by resource type.
03Can we keep our existing approval process?
Yes — approval policy is configurable by cost, environment and resource type, and changes sync to ServiceNow or Jira if that is where approvals live today.
Next step
AI-Native Provisioning, on your own estate.
Bring one cloud account or one on-prem site. We connect it read-only during the session, walk this workflow on your real resources, and leave you with the export.