Skip to content
Browse documentation

Costframe documentation.

Connect your cloud, get a first audit and use the results in your team's work. Choose a task below, or search for the exact operation you need.

Operating and reference guides

These pages explain how audits, scope selection, findings, cost figures, security checks and data freshness work.

Concepts

Audit run and export states

How Costframe represents queued, running, partial, failed, completed, report, PDF, and export states.

Operate

Scope selection and exports

How selected provider connections flow through dashboard pages, filters, and server-side CSV exports.

Concepts

How findings work

How Costframe labels estimate, proof level, target type, evidence contract, and verified realized savings.

Concepts

How Costframe calculates costs

Reconcile provider-billed net cost with list-price context, keep currencies separate, and distinguish modeled estimates from verified savings.

Trust

Security and governance checks

Understand what Costframe's security findings establish, how evidence gaps limit coverage, and why automated checks do not certify compliance.

Operate

Data sources and freshness

Check how provider billing, inventory, utilization, security, pricing, and recommendations are collected, dated, and marked missing or stale.

Operate

Troubleshooting

Safe next steps for failed audits, missing permissions, stale costs, PDF export failures, and empty reports.

Operate

Action lifecycle

How assignment, approval, external implementation, rollback planning, observation, and verification remain separate states.

Operate

Decision briefs

How Costframe turns authorized findings into executive drafts without losing evidence, confidence, limitations, ownership, or approval state.

Trust

AI governance

Review how AI explanations use permitted Costframe evidence, retain source limitations, and remain separate from customer decisions and verified outcomes.

Trust

Identity and access

Workspace identity, organization context, Microsoft Entra readiness, role gates, and platform-admin boundaries.

Trust

Roles and effective access

Current workspace roles, authoritative identity context, platform-admin boundaries, and intentionally unsupported access paths.

Operate

Integration delivery

Configure supported Slack, Microsoft Teams, and HTTPS webhook destinations, then interpret queued, attempted, accepted, uncertain, and failed receipts.

Operate

Notifications and delivery

Notification sources, read state, related-record links, and the difference between in-app state and external delivery.

Operate

Administrative audit log

Search, outcome filters, safe event detail, decision-chain inspection, CSV export, and the limits of the workspace administrative record.

Operate

Service health

How platform operators interpret service status, verification time, safe failures, impact, and recovery guidance.

Trust

Data lifecycle

Retention, export, deletion grace periods, legal holds, revocation, and evidence that may outlive workspace content.

Read-only security model ↗Trust Center ↗Provider readiness matrix ↗Plan entitlements and FAQ ↗Documented limitations ↗Choose a cloud-cost approach ↗Evidence-led findings ↗

Need a precise answer before connecting a customer tenant?

Billing questions live on pricing, trust questions live on security, and anything procurement-specific should go through the legal directory.