AI-Native Provisioning replaces shared console access with a governed service catalog: teams request approved resources, Whale AI suggests a right size from your inventory and billing history, policy routes the request to the right approver, and the platform provisions with its own credentials. AWS provisioning is live for EC2, S3, RDS, VPC and EFS; Azure and GCP items are in the catalog for request and approval.
- 5
- 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
How it shows up
- Engineers hold broad console rights because the alternative is a ticket queue.
- Instances are sized by habit, so over-provisioning is baked in from day one.
- Nobody can say who approved a resource, or whether it was approved at all.
How it works
- 1
Step 1
Teams browse a catalog of approved resources — no cloud console needed.
- 2
Step 2
Whale AI recommends a size from your inventory and cost history before the request is submitted.
- 3
Step 3
Approval policy routes the request by cost, environment or resource type; low-risk items auto-approve.
- 4
Step 4
AWS resources are provisioned live; Azure and GCP items are fulfilled from the catalog.
- 5
Step 5
Every provisioned resource lands in the unified inventory, cost tracking and the audit trail.
What is included
- AWS provisioning live (EC2, S3, RDS, VPC, EFS)
- Azure & GCP catalog items with approval workflows
- Guardrails — approved sizes, regions and tags enforced before submit
- Whale AI sizing recommendations inside the request
Modules involved
Service Catalog
Provision approved cloud resources — no consoles.
Whale AI
A horizontal AI layer across every module — 50+ use cases, able to run fully offline.
Identity & Access
One identity fabric — federate your IdP and auto-provision access everywhere.
Editions and audience
Recommended editions: Standard and Enterprise.
Who it is for: Platform engineering teams and cloud operations who want governed self-service.
Questions teams ask in the evaluation
Does 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.
Which 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.
Can 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.