All applications583

Find your application

583 applications

Open full catalog

Browse applications by category or open the full catalog.

Cloud Cost Management
Start now
More

Features

Industries

Reference

More

Cloud Cost Management · Available now

Trace cloud spend from cost line to reviewed action.

Cloud Cost Management brings daily cloud charges, account ownership, cost center allocation and service context into one working record. A cloud finance analyst can review spend by provider, account, service and usage date, then connect an unusual charge to an incident for investigation.

Start now Download Proto
  • No per-user fees
  • Manual work is free
  • Configure it in Proto
OverviewActive Service Requests
Cloud Cost Management · Service requests

Active Service Requests

Service requests in one list

New service request
Service requests in view
6
Submitted
2
Approved
2
In progress
2
Submitted2
COST-2026-1041Cost allocation review
04 Nov
ALERT-2026-0736Unused asset cleanup
30 Oct
Add
Approved2
INC-2026-0382Budget threshold change
20 Oct
CHG-2026-0168Savings validation
27 Oct
Add
In progress2
ASSET-2026-0214Resource rightsizing
19 Oct
REQ-2026-0557Account tag correction
15 Oct
Add
COST-2026-1041Service requests · SR-79894
Submitted
Request typeCost allocation review
Requested at04 Nov
Due at10 Nov
RequesterEvan Mensah
ServiceIdentity gateway
Approve changeSR-79894 · COST-2026-1041

Change Approver records the decision and reason.

Waiting for Change Approver
ApproveReturn
Example screen with sample data
Tables, ready to use
53
Saved views
16
Roles with set permissions
7
Reports and dashboards
8
Features

See each charge in context

Every feature works on the same records. Pick one to see the screen your team works in.

Spend evidence

Review daily cloud charges by account, service, cost center and usage date.

  • Daily evidence
  • Allocation context
  • Exception trail
  • Cloud cost lines
  • Cloud accounts
  • Account cost centers
  • Cost center allocations
  • Incidents
Explore spend evidence
OverviewDaily Cloud Cost Lines
Cloud Cost Management · Spend evidence

Daily Cloud Cost Lines

Cloud cost lines

New
IdProviderCloud accountService nameUsage dateCost center
COST-2026-1041Northstar CloudCore productionCheckout API compute, 15 Oct21 OctCC-410 Platform
INC-2026-0382Cedar ComputeCore stagingAnalytics storage, 15 Oct18 OctCC-420 Data services
ASSET-2026-0214Bluehaven InfrastructureData productionBilling database, 15 Oct19 OctCC-430 Customer apps
ALERT-2026-0736Ridgeway HostingShared networkingSearch index nodes, 15 Oct23 OctCC-440 Security
CHG-2026-0168Harbor GridDeveloper toolsIdentity gateway traffic, 15 Oct18 OctCC-450 Internal tools
6 of 6 records
COST-2026-1041Cloud cost lines · CCL-31806
ProviderNorthstar Cloud
Cloud accountCore production
Service nameCheckout API compute, 15 Oct
Usage date21 Oct
Cost centerCC-410 Platform
Example screen with sample data
Process

Follow the cost question to an outcome

Cost incident to verified action ships ready to use. One step needs a named approval before the work moves on: Approve change (Change Approver).

Drag a card to another stage, or focus it and use the arrow keys. It updates to match the stage.

  1. Detect

    Find the charge, alert or anomaly that needs review.

    COST-2026-1041SR-79894 · Cloud Cost Analyst
    DetectBy Cloud Cost Analyst

  2. Acknowledge

    Give the incident an owner and record the response.

    COST-2026-1041SR-79894 · Cloud Cost Analyst
    AcknowledgeBy Cloud Cost Analyst

  3. Investigate

    Check the service, asset and dated cost evidence.

    COST-2026-1041SR-79894 · Cloud Cost Analyst
    InvestigateBy Cloud Cost Analyst

  4. Approve change

    Review the plan, risk and rollback before work begins.

    COST-2026-1041SR-79894 · Change Approver
    Approve changeBy Change Approver
    ApprovalChange Approver records the decision and reason.

  5. Implement

    Record what was applied to the service.

    COST-2026-1041SR-79894 · Cloud Operations Engineer
    ImplementBy Cloud Operations Engineer

  6. Verify

    Compare the later cost result with the target.

    COST-2026-1041SR-79894 · Service Owner
    VerifyBy Service Owner

Start with Spend review

Inside a record

Check the source of every charge

Open any service request to see the roles that work on it, its process stages and its approvals on one page.

  1. 1
    Record details

    Request type, Requested at, Due at and Requester.

  2. 2
    Linked records

    Records linked to this service request.

  3. 3
    Who works on it

    Service Owner, each with their own permissions.

  4. 4
    Process stages

    Every status change, in order.

  5. 5
    Approvals

    Approve change, with who decides.

Active Service RequestsCOST-2026-1041
Cloud Cost Management · Service requests

COST-2026-1041

Cost allocation review · Submitted

Log activity
1
Record details
Request typeCost allocation review
Requested at04 Nov
Due at10 Nov
RequesterEvan Mensah
3

Who works on it

  • Service OwnerManage Services, service requests, account onboarding requests…
5

Approvals

  • Approve changeChange Approver
    Approved
Example screen with sample data
Approvals

Record the decision behind change

A Change Approver records the decision; Cloud Operations Engineer records the deployment outcome.

OverviewApprovals
Cloud Cost Management · Overview

Approvals

Signed in as Change Approver

Waiting for you

4 To review1 Overdue2 Decided todayOnly mine
0 selectedApproveReturn
  • CHN-82853COST-2026-1041
    Staging compute spend rose 82%Requested by Cloud Cost Analyst
    Low1dActions
  • CHN-74636INC-2026-0382
    Remove unused analytics snapshotsRequested by Cloud Cost Analyst
    Medium2dActions
  • CHN-16659ASSET-2026-0214
    Search nodes scaled beyond demandRequested by Cloud Cost Analyst
    High4dActions
  • CHN-36925ALERT-2026-0736
    Reserve capacity for billing databaseRequested by Cloud Cost Analyst
    Low5dActions

Who approves what

DecisionApprover
Approve changeReview the plan, risk and rollback before work begins.Change Approver
Approve ChangesChange Approver
2 approval rules · set per role in Proto
Example screen with sample data
Who can approve what
Roles

A workspace for each role

Everyone opens Cloud Cost Management to the work that is theirs. Pick a role to see what it starts with.

Cloud Cost Analyst

Investigates spend evidence, anomalies and cost incidents.

This is the first screen this role sees.

OverviewOpen Incidents

Open Incidents

Incidents · Cloud Cost Analyst

Low2
COST-2026-1041Staging compute spend rose 82%
28 Oct
CHG-2026-0168Unallocated traffic charge found
27 Oct
Add
Medium2
INC-2026-0382Remove unused analytics snapshots
26 Oct
REQ-2026-0557Idle worker pool ran overnight
16 Oct
Add
High1
ASSET-2026-0214Search nodes scaled beyond demand
11 Oct
Add
Critical1
ALERT-2026-0736Reserve capacity for billing database
12 Oct
Add
Example screen with sample data

Roles and permissions

Reports

Compare spend and measured savings

Read spend, anomaly, savings and data quality measures from operating records.

Overview
Cloud Cost Management · Overview

Cloud Cost Management dashboard

This quarter

Changes in view
6
Approved
3
Implementing
3

Service requests by status

How far records got this quarter

StageReachedStep
Submitted40
Approved1230%
In progress542%
Completed240%

Number of service requests by status

Sample counts per stage

0
-50Submitted
-60Approved
-20In progress
-50Completed
-60Rejected
Example screen with sample data
  1. 01Daily spend by account and service

    Sum cloud cost line amount USD by cloud account, service name and usage date.

  2. 02Cost center spend

    Sum cloud cost line amount USD by cost center and usage date.

  3. 03Open anomaly exposure

    Sum cost anomaly event estimated excess cost for events without cleared at.

  4. 04Recommendation savings

    Compare optimization recommendation estimated monthly savings with verified savings by Status.

  5. 05Ingestion outcomes

    Count cost ingestion runs by Status and ingestion pipeline.

  6. 06Alert volume

    Compare spend alert match count by Status and window start.

  7. 07SaaS seats and cost

    Compare saa S subscription licensed seats and monthly cost by application name.

  8. 08Change outcomes

    Count Changes by Risk and Status, with change approval review decision linked to each change.

All reports and dashboards

Who it's for

Fit your cloud operating model

See how Cloud Cost Management fits your kind of team.

Cloud platform teams

Give platform owners a charge trail from provider account to service change.

SaaS operations

Review paid subscriptions, seat use and renewal ownership alongside cloud spend.

Multi-account enterprises

Keep account, cost center and service owners aligned across cloud estates.

Controls

Keep approval and result together

Each stage of cost incident to verified action names the role that acts and the status it records, so a change is never anonymous.

OverviewCost incident to verified action
Cloud Cost Management · Process

Cost incident to verified action

Each stage, the role that acts and the status it records

Process stages
10
Approval steps
1
Roles involved
4
Tables touched
13
Acknowledge
Cloud Cost Analyst
StatusOpen → Acknowledged
RecordsCost event log, Incidents
Investigate
Cloud Cost Analyst
StatusAcknowledged → Investigating
RecordsIncident updates, Incidents, Services
Recommend
Service Owner
StatusProposed → Reviewed
RecordsOptimization recommendations, Services
Cost incident to verified action
  1. Start
    AcknowledgeOpen → Acknowledged
    Cost event log
  2. Step
    InvestigateAcknowledged → Investigating
    Incident updates
  3. Step
    RecommendProposed → Reviewed
    Optimization recommendations
  4. Step
    Plan changeDraft → Review
    Services
  5. Approval
    Approve changeReview → Approved
    Change approval reviews
Example screen with sample data

See each stage in detail

AI agent

Ask about a specific cost case

Give an assistant a precise charge, incident or change question to investigate.

It can

  • Cloud Cost Analyst: Show open incidents assigned to me with the linked anomaly estimate and recent update.
  • Finance Manager: Compare daily charges by cost center and identify accounts whose allocation rule needs review.
  • Service Owner: Compare the recommendation, planned change and later savings result for a named service and period.
  • Cloud Operations Engineer: Find failed ingestion runs and rejected receipts for a source period.

Stays with a person

  • The assistant can assemble the working record, but a Change Approver makes the approval decision.
  • A service owner checks whether a deployment is safe for the workload, and Finance Manager decides whether the later cost period is representative.
  • Give the assistant a specific account, service or incident and ask it to cite the records it used.

Set up an agent

Integrations

Connects to the tools you use

Set up connections through ERP.AI and Proto workflows, with every change logged.

  • Cloud Cost Management
  • Cloud provider billing
  • Provider account console
  • Billing API source
  • Cost data store
Data model

Your data, in tables you can change

Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.

Browse all 53 tables
53tables
  • Spend evidence5
  • Accounts and allocation6
  • Cost incidents7
  • Optimization7
  • Changes and deployments5
  • Data operations8
Implementation

Roll out one team at a time

Start with one team and one process, then add the rest once the basics are running.

  1. Name owners

    Assign the people who own accounts, services, allocation and change decisions.

  2. Map source data

    Agree account names, usage dates, cost center codes and billing source checks.

  3. Load an operating slice

    Bring in an account, a service and a recent period of daily charges.

  4. Rehearse exceptions

    Open an anomaly case, record an incident update and review a saving change.

  5. Verify results

    Compare the deployment outcome and later cost with the original estimate.

Read the implementation plan

Pricing

$0per user

The base account and everyday work in the ERP.AI app are free, for every user.

  • No per-user or per-seat fees
  • Viewing, editing, approving and exporting records in the app is free
  • Pay only for machine work: API calls, imports, workflows and AI agents
  • Prepaid credits from $5. Purchased credits never expire

Pricing details

Machine work rate card Included per $1 of credit

Machine work rate card
UsagePer $1
Record reads (list, filter, get)20,000
Search or aggregate queries4,000
Record writes4,000
Imported or synced records200,000
Workflow runs2,000
AI agent runs2,000
Scheduled jobs or webhooks20,000
File uploads (MB)2,000
CSV or PDF exports100
FAQ

Questions, answered

Scope, rollout and pricing for Cloud Cost Management.

All questions
How do I get started?

Click Get started, then use Proto to configure Cloud Cost Management for your business. Begin with one account, one service, a recent billing period and the people who review its charges and approve changes.

What cost detail can we review?

Each daily cost line holds the provider, account, service name, usage date, cost center and US dollar amount. Use those fields to trace a movement to its source and owner.

How do we allocate shared account spend?

Record the cost center code, allocation rule and review cycle against the account. Agree the basis with the Cost Center Owner before publishing the rule.

How does an unusual charge become work?

Review its spend alert or anomaly event, then open an incident with a priority, service and assignee. The analyst records dated updates and cost events through resolution.

Who approves a saving change?

The Change Approver reviews the plan, risk, schedule and rollback approach, then records a decision and reason. An approved change can move to implementation.

Can we compare estimated and actual savings?

Yes. A recommendation records an estimate and verified saving. A verification record compares target with realized saving for a workload; a later reversal check compares baseline with actual cost.

How do we know billing data is current?

Check ingestion run outcomes and freshness checks for the source period. Rejected receipts and failed runs deserve investigation before a lower charge total is treated as a saving.

Can subscription spend be reviewed too?

SaaS subscription records hold monthly cost, licensed seats, renewal date and owner. Seat usage records show assignment, last activity and revocation dates.

What should we test before rollout?

Rehearse a charge review, a cost incident, an approved and rejected change, and a later savings comparison using a representative account and service.

Set up Cloud Cost Management your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

Start now Download Proto

How to get started

A personal agent for your business

Get started with Proto

Your app is selected. Download Proto, then open it with this context.

Selected appCloud Cost Management

Choose your computer’s platform.

Download Proto

Install Proto, then return to this panel.

Already installed? Open Proto

Free to use. Your own model provider may charge for usage.