CloudKnifeCloudKnife
PlatformCore Optimization Intelligence

Optimisation that’s easy to review and safe to approve.

CloudKnife turns usage signals into a clear queue of optimisation opportunities, from rightsizing and cleanup to scheduling, commitments, and service-fit, built for governance and human control.

ModeRead-only first
ControlHuman-approved
GovernancePolicy-aware
What you get
A prioritised queue of opportunities, each with impact, risk, and rationale.
What it looks like

A review-first optimisation queue

Clear outcomes, ownership, and guardrails, built for engineering and finance.

Recommendations queue

One queue for opportunities, decisions, and follow-up.

Designed for change management

Recommendations are opt-in, reversible, and aligned to policy boundaries.

Ownership stays visible

The right people get involved early, fewer dead ends, faster approvals.

High-level on the website, detailed evidence inside the product.
Capabilities

Coverage across the optimisation surface

Show the breadth without exposing the how.

Capacity & Waste
Right-size capacity to real demand

Reduce over-provisioning while keeping safety headroom. Designed for review and approval, not blind automation.

Eliminate idle & orphaned resources

Find unused spend with accountability context, so teams can confirm intent and ownership before acting.

Architecture & Placement
Service selection & architecture fit

Suggest better-fitting services or SKUs when a workload’s needs and constraints indicate a mismatch.

Region & placement optimisation

Highlight placement opportunities while respecting governance rules, policy boundaries, and latency expectations.

Commitments & Scheduling
Align runtime with predictable usage (scheduling)

Propose opt-in schedules for predictable patterns. Reversible changes, with clear impact expectations.

Reservations & committed discounts

Identify commitment opportunities with break-even clarity, so finance and engineering can decide confidently.

Safety

Governance-friendly by default

Guardrails, ownership, and approval-first workflows.

Evidence view

Rationale and expected impact, built for decision-making.

How it stays safe

Start by observing and recommending. You choose what to approve and when.

Every item includes clear reasoning and expected impact so review is fast and consistent across teams.

Recommendations can be aligned with environment rules (prod vs non-prod, critical workloads, change windows).

Route decisions to the right owners so actions happen with the right context and responsibility.

Keep website messaging high-level; keep the proof inside the product.
Workflow

From signals to safe action

A lightweight process teams can adopt quickly.

1
Observe

Ingest usage signals and environment context.

2
Prioritise

Rank opportunities by impact and review effort.

3
Review

Teams approve items with rationale and guardrails in view.

Platform
Get optimisation clarity before touching production

Start read-only. Review opportunities with guardrails and ownership in view, then approve what makes sense.