Bring AWS, Azure, Google Cloud, OVHcloud Public Cloud, Scaleway and Scalingo together to track organisation spending. Review their place in your budget without conflating their sources, periods, credits or level of detail.
01 — SeeIllustrative product scene · Six NovaRetail clouds · Fictional November 2026 data
Fictional observed spending
21,840 €
Fictional month-end forecast
43,680 €
Fictional global budget
45,000 €
Fictional amounts. Sources and credits differ; Google Cloud uses a BigQuery export, OVHcloud is Public Cloud only, and Scalingo has an estimated current month and a token not restricted to read-only access.
01See
A shared view. Every source stays visible.
The consolidated view brings together authorised connections and collected cost periods. Return to an available provider, account, project or application to examine each contribution rather than comparing totals with different scopes.
Google Cloud needs a populated BigQuery export, which determines available history. OVHcloud coverage is Public Cloud; Scalingo separates closed invoices from the current estimate. Sources and granularity remain specific to each connection.
Actual product screenshot — AWS, Scalingo and OVHcloud recommendations using fictional NovaRetail data. Potential savings are estimates to review and do not constitute a promise of savings.Enlarge to explore
6providers, each with its own sources and limits
1workspace for spending, budgets and follow-up
Your choicea shared AI policy for the organisation
A decision example
Compare clouds while retaining their differences.
Illustrative workflow using the fictional NovaRetail data above; no customer results or guaranteed savings.
Before
Six consoles separate spend from your organisation’s responsibilities and budgets.
The review
In NovaRetail, start with the consolidated view, then filter a provider to find its sources, period and level of detail.
The next action
A global budget sets the framework; provider budgets and allocation available on your plan help each team make its decision.
Centralization does not make every API identical. Detail, freshness and credit treatment must inform your comparisons.
A common view that preserves data limitations
Provider or scope
Data and coverage limits
AWS and Azure
AWS Cost Explorer supplies costs by account, service and region; Azure Cost Management supplies costs for authorized subscriptions. Inventory and recommendations depend on additional permissions.
Google Cloud
Cost tracking relies on your BigQuery billing export. Without a populated export, spend cannot be inferred; history depends on the data already present in that export.
OVHcloud Public Cloud and Scaleway
OVHcloud coverage is for its Public Cloud projects. Scaleway uses consumption and billing data with their project and product detail. These scopes do not cover every product sold by each group.
Scalingo
Closed months use invoices. The current month is estimated from active resources and their prices; it does not reconstruct every scaling change during the month.
Credits, discounts, taxes and periods follow different conventions across providers. Consolidated spend is not a price comparison of two equivalent architectures.
02Anticipate
The budget is global. The deviation has a source.
Set a monthly global envelope or provider budgets with their thresholds and recipients. Follow deviations using synchronised data, then return to the source to understand consumption and the forecast available for the scope concerned.
Credits, discounts, taxes and periods follow different conventions. A consolidated sum does not measure the price of equivalent architectures; review coverage and billing rules before concluding that one provider offers an advantage.
Track a global monthly envelope and provider budgets. Project or account scopes are available according to supported data.
02
Organization permissions
The owner, administrators, editors and readers have distinct responsibilities. Access to figures and configuration actions follows those permissions.
03
Governance according to your plan
Extend tracking with the modules available to your plan: cost allocation, unit economics, governance, maturity or Showback. Their use also depends on collected data and your configuration.
NovaRetail Cloud · Fictional global budget · November 2026
Observed€21,840
Budget€45,000
Forecast€43,680
Collected spendForecast
Fictional data. Estimates evolve as data is collected and according to each provider’s billing rules.
03Act
Multiple clouds. Coordinated decisions.
Review the recommendations actually available, confirm their context with authorised members and assign follow-up. Organisation roles distinguish reading from configuration; your teams retain the decision and carry out changes within each cloud.
Inventory and recommendations depend on permissions and do not have identical coverage across providers. Allocation, unit economics, governance, maturity or Showback require the appropriate plan and activation; the AI policy remains a separate owner decision.
Grant the necessary provider access from the console. FinOps performs reads; options to restrict credentials differ, particularly for the Scalingo token.
02
Consolidate spend
After synchronization, review costs in the overview and your dashboards, with the available scopes, periods and currency conversions.
03
Spot spending drift
Set a global or provider budget and alert thresholds. Return to the accessible detail to understand the source of a deviation.
04
Prioritize actions
Review available recommendations and coordinate follow-up with authorized members. Changes remain under your teams’ control at each provider.
From a signal to a tracked action.Illustrative workflow · Subject to plan and permissions
01 / Review
A finding. Its context.
Check conditions and available data
To review
02 / Decide
A decision. A priority.
Confirm usage and dependencies
To qualify
03 / Track
A team. A tracked action.
Assign follow-up to an authorised member
In progress
A plan for your scope
From your first cloud to teamwork.
Choose according to tracked spend and team needs, rather than the number of providers alone.
Standard
€69excl. VAT / month
For a small team’s cost and budget tracking.
Up to €5,000 in tracked cloud spend per month
3 connections · 2 members · 5 dashboards
800 AI credits / month, if AI is enabled
Budgets, alerts and direct cost allocation
Pro
€249excl. VAT / month
For tracked actions, measured savings and responsibilities.
Up to €20,000 in tracked cloud spend per month
10 connections · 5 members · 20 dashboards
1,500 AI credits / month, if AI is enabled
Savings Tracker, Slack, Teams, Jira, GitHub and GitLab
Starter — free, up to €1,000 tracked spend / month and 1 connection. Without a subscription after the trial, the organisation continues on Starter, within its limits.
Connect your European environment with hyperscalers
01
Distributed workloads
Track Scalingo applications alongside OVHcloud Public Cloud and Scaleway projects, with the detail each connection can collect.
02
A hybrid environment
Add AWS, Azure or Google Cloud spend to the same workspace to examine its share of your overall budget, without requiring a single provider.
03
Limits that inform decisions
Provider-specific recommendations do not promise parity with other providers. Check permissions, the latest synchronization and coverage before drawing conclusions.
Collect costs and use views, budgets and rule-based recommendations without enabling an AI model.
02
Sovereign AI
European mode follows the documented EU and EFTA processing scope and has no fallback to Standard mode. Some provider technical metadata may be handled outside that region.
03
Standard AI
This optional mode uses a provider established in the United States. Analyses follow your organization’s policy and the documented data minimization measures.
The application is hosted in France. That alone does not describe the residence of all processing, metadata and integrations you enable.
Review each provider’s permissions and billing source.
02
Bring the data together.
After synchronisation, check the periods and coverage actually available.
03
Frame the decisions.
Set budgets and choose recommendations to review with your team.
Before you begin
The right questions.
Do I need to use all six providers?+
No. Start with your organization’s providers, then add connections according to your needs and plan limits. Each connection needs the required permissions and billing sources.
Does every connection have read-only access?+
FinOps reads data and does not operate your cloud resources. AWS, Azure, Google Cloud, OVHcloud and Scaleway let you restrict access to appropriate read permissions. Scalingo does not offer an API token limited to reading: the supplied token has broader rights and must be protected and revoked in Scalingo when necessary.
Are data comparable across providers?+
You can review spend in a common workspace with the available currency conversions. Credits, discounts, taxes, periods and dimensions vary by source. Compare consistent scopes; the total does not prove that moving from one architecture to another would cost less.
Why can current-month Scalingo costs change?+
They are estimated from active resources and prices because current consumption is not exposed as a final invoice. Closed months use the available invoices. Past scaling changes and some overages can explain differences.
Why can Google Cloud be connected without showing costs?+
A connection can be validated before the first BigQuery export rows arrive. The billing export must exist and receive data; Google’s delays and the export’s history determine what is available.
Does consolidation require AI?+
No. Financial collection and consolidation, budgets and rule-based recommendations do not depend on AI. AI-assisted features are optional and follow the policy, limits and availability of the mode chosen by your organization.