Track OVHcloud Public Cloud and Scaleway projects alongside Scalingo applications. Review spending in one workspace while distinguishing consumption sources, closed-month invoices and the estimate for the current month.
01 — SeeIllustrative product scene · European NovaRetail scope · Fictional November 2026 data
Fictional observed spending
3,640 €
Fictional month-end forecast
7,280 €
Providers in this scene
3
OVHcloud Public Cloud only. Scalingo: estimated current month, invoiced closed months and a token not restricted to read-only access. History and detail vary.
01See
Three clouds. Each with its context.
Start with the projects and applications your connections can actually read. OVHcloud provides Public Cloud consumption, Scaleway provides project consumption and Scalingo provides application costs. Return to the available detail to understand each provider’s breakdown and how its spending evolves.
OVHcloud coverage does not extend to every offering. History, inventory and recommendations depend on the source and permissions; Scalingo’s token is not restricted to read-only access, although FinOps only uses it to read.
Actual application screenshot — an OVHcloud Public Cloud project dashboard for a fictional organisation. Only this scope is illustrated; coverage and data differ by provider.Enlarge to explore
3European providers brought into one workspace
Public Cloudthe OVHcloud scope covered by this connector
EstimateScalingo’s current month, distinct from invoiced months
A decision example
Three providers, with periods you can explain.
Illustrative workflow using the fictional NovaRetail data above; no customer results or guaranteed savings.
Before
OVHcloud Public Cloud or Scaleway consumption and a Scalingo invoice do not always cover the same period.
The review
In NovaRetail, compare projects and applications over a closed month, then distinguish Scalingo’s current-month estimate.
The next action
Set a budget per provider and return to the available source before qualifying a variance.
Shared dashboards do not make the APIs identical. These differences matter before connecting your accounts.
Three providers, distinct sources.
Provider or scope
Data and coverage limits
OVHcloud Public Cloud
Consumption collected by Public Cloud project, with up to six months of history and OVHcloud’s forecast. Available inventory recommendations depend on resource families actually read. This scope does not cover every OVHcloud product.
Scaleway
Project consumption by product and resource type, with up to twelve months of history. Billing, project and inventory permissions are distinct; resource recommendations depend on granted permissions.
Scalingo
Invoices provide closed-month costs, with up to twelve months of history depending on access. The current month is estimated at catalogue prices from the current container and add-on configuration, without reconstructing past size changes. Views follow applications; recommendations use available app, container and add-on data.
History and detail remain subject to APIs, permissions and available data. Recommendation coverage is not identical across providers.
Set a global or provider budget and choose alert recipients. Compare that envelope with collected data while keeping the period, latest synchronisation and type of amount visible: consumption, a received invoice or an estimate.
Scalingo’s current month is estimated at catalogue prices from the current container and add-on configuration, without reconstructing past size changes. The final invoice may differ; periodic collection is not a real-time meter.
Compare collected spending against provider, project or application budgets where supported. Configure recipients for threshold and overrun alerts.
02
Review recommendations
Rules look for situations that can be checked in collected data: unused resources, non-production environments or configurations to investigate, depending on the provider. Validate context before acting.
03
Allocate and share
Use team roles and allocation or governance modules included in your plan. Advanced functions require the relevant plan and, for some modules, activation.
Use project and application detail to investigate flagged resources or configurations. Confirm usage with authorised members, organise follow-up on available recommendations and decide which provider-side changes to make while accounting for operational dependencies.
Recommendations depend on resource families read and permissions, without identical detection coverage across clouds. Allocation and governance depend on the plan; the AI policy remains separate from the European providers you connect.
Follow invoiced spending by application and keep the current-month estimate distinct from billed months. Set budgets suited to the data available.
02
Bring OVHcloud and Scaleway together
Combine Public Cloud and Scaleway project costs, then filter spending. Take differences in history and scope into account when comparing.
03
Extend the view to hyperscalers
Add AWS, Azure or Google Cloud to bring spending into the same workspace. Dimensions and sources remain specific to each connector; consolidation does not remove those differences.
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.
Requested access is read-only. At Scaleway, permission sets on the organisation and projects determine available billing and inventory data.
02
The Scalingo token exception
Scalingo does not offer a read-only API token. The token you provide may grant broader rights; the FinOps connector only uses it to read. You can revoke it at Scalingo.
03
Periodic collection
Frequency depends on your plan, from weekly to several synchronisations per day. Providers may publish billing data with a delay; FinOps is not a real-time meter.
04
Amounts in context
Scalingo’s estimate can differ from its final invoice. History and billing rules vary; use source details when interpreting comparisons between providers.
The application is hosted in France. Your cloud provider alone does not determine processing by AI or integrations you enable.
01
AI disabled
Keep cost tracking, budgets, alerts and deterministic recommendations without new external AI calls.
02
🇪🇺 Sovereign AI
Requests processed in the European Union and EFTA, subject to availability. The service’s technical metadata may be processed outside that region; no fallback to Standard AI.
03
🇺🇸 Standard AI
Optional AI features using minimised data, with possible processing in the United States. The owner chooses the organisation’s policy.
OVHcloud and Scaleway request read permissions. Scalingo’s token is not read-only, although FinOps only uses it to read.
02
Collection has a cadence.
Frequency depends on your plan and the provider making billing available. This is not a real-time meter.
03
A separate AI policy.
The application is hosted in France. The owner chooses AI independently from the cloud being tracked; other processing locations still need review.
Bring your European cloud spending into a shared view.
Your European environment. Finally in the same frame.
Start by exploring the screens or creating your organisation, then connect the providers within your scope. Access and limits remain explicit at each step.
Identify the Public Cloud projects, Scaleway projects and Scalingo applications to track.
02
Review permissions.
Check the requested rights, especially those granted by the Scalingo token.
03
Read the sources together.
After synchronisation, distinguish consumption, closed invoices and estimates.
Before you begin
The right questions.
Are all OVHcloud products covered?+
No. This connector tracks OVHcloud Public Cloud projects. That does not imply coverage of every OVHcloud offering. Inventory and recommendations depend on resource families actually read and available permissions.
Is the Scalingo token restricted to read-only access?+
No. Scalingo does not offer a read-only token. FinOps only uses it to read, but its permissions at Scalingo can be broader. You can revoke it directly at the provider.
Why is Scalingo’s current month estimated?+
Closed months use received invoices. The current month is estimated at catalogue prices from the current container and add-on configuration, without reconstructing size changes that have already occurred. The final invoice may also include adjustments or discounts.
How often is data updated?+
Automatic synchronisation depends on the plan: weekly for Starter, daily for Standard, every twelve hours for Pro and every six hours for Enterprise. This frequency does not guarantee that the provider has already published recent billing data.
Can I add AWS, Azure or Google Cloud?+
Yes, within your plan’s connection and tracked-spending limits. Costs join the same workspace, using the dimensions, histories and billing conventions specific to each provider.
Does using a European cloud require AI?+
No. The AI policy is a separate choice made by the organisation’s owner. AI can be disabled; when enabled, processing locations and the selected mode’s limits are described in the Security and data part of the documentation.