Service Catalog
Provision approved cloud resources — no consoles.
The Service Catalog lets teams request approved cloud resources without touching cloud consoles. AWS provisioning is live for EC2, S3, RDS, VPC and EFS, with Azure and GCP catalog items, approval workflows, governance guardrails and Whale AI sizing advice built into the request — so self-service and control stop being a trade-off.
- AWS live
- EC2 · S3 · RDS · VPC · EFS provisioned from the catalog
- Guardrails
- Approved sizes, regions and tags enforced before submit
- Whale AI
- Sizing recommendations inside the request form
Capabilities
What Service Catalog does
Governed self-service
Teams pick from catalog items you approve — with sizes, regions, tags and naming already constrained — instead of being handed console access.
Approval workflows
Route requests by cost, environment or resource type to the right approver; low-risk items can auto-approve, everything is recorded.
Whale AI sizing
The request form asks Whale AI for a right-sized recommendation grounded in your inventory and cost history, before a single instance is oversized.
Audit trail
Who requested, who approved, what was provisioned and where — every catalog action lands in the platform audit log and the ITSM change record.
How it works
3 steps, from first connection to steady state
Publish catalog items
Define the resources teams may request and the guardrails that apply to each.
Request and approve
A developer selects an item, gets a sizing suggestion, submits; the approval policy decides who signs off.
Provision and track
The platform provisions with its own credentials, tags the resource, and adds it to inventory and cost tracking automatically.
Where it fits
One module of one platform
Shared platform
Capabilities
- AWS provisioning live (EC2, S3, RDS, VPC, EFS)
- Azure & GCP catalog items
- Approval workflows & guardrails
- Whale AI sizing recommendations
Included in
Solutions that use it
Industries that rely on it
Also in Management & Delivery
Questions
Questions teams ask before turning it on
Scope, permissions and maturity — answered the way we answer them in an evaluation.
01Which resources can be provisioned today?
On 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.
02Can requests bypass approval?
Only if your policy says so — for example, dev-environment items under a cost threshold. Everything else routes to the approver you define, and every decision is logged.
03Where do provisioned resources show up?
In the unified inventory immediately, tagged with requester and workload, and in Whalenomics cost tracking from the first billing record.
See it on your data
Service Catalog, on your own estate — in one working session.
Bring one cloud account or one on-prem site. We connect it read-only during the call, walk the module on your real resources, and leave you with the export.