Discover

Overview

FinOps Move2Cloud brings the costs of your cloud accounts into one view and helps you reduce them: spend of the month, end-of-month forecast, 12-month history, budgets with alerts, priced savings recommendations, shared dashboards and PDF or CSV exports.

Enlarge

Overview: the month's indicators, the spend of the last 12 months and the breakdowns.

Actual sizeClose

The tool reads your costs and your inventory; it neither changes nor deletes anything at your providers.

Why FinOps Move2Cloud

Most FinOps tools were designed first for AWS, Azure and Google Cloud. FinOps Move2Cloud was designed for sovereign clouds, and positions itself as the reference for tracking and optimising their costs, without giving up the American clouds you also use.

• Sovereign clouds read natively: OVHcloud Public Cloud projects (instances, volumes, Kubernetes, managed databases), Scalingo apps and add-ons, Scaleway projects. At Scalingo, which does not publish its current consumption, the current month is estimated from the containers and add-ons running.
• Recommendations written for these clouds: non-production environments running permanently, Kubernetes pools without autoscaling, OVHcloud instances billed by the hour that would benefit from a commitment, oversized Scalingo containers, unused add-ons.
• A single view with AWS, Azure and Google Cloud: you compare what you spend with each, and follow the share of your budget entrusted to sovereign providers, region by region.
• A platform hosted in France: the application, its database and its backups at Scalingo, e-mails and exports at Scaleway, in Paris.
• Access verified then encrypted, read-only except at Scalingo, which offers none: in every case the tool only reads, it neither changes nor deletes anything at your providers.
• A French publisher, Move2Cloud, specialised in migrating to and running sovereign clouds: an interface and support in French and English, prices in euros.

Key features

• Overview: the month's spend to date, the end-of-month forecast, 12 months of history, and the breakdown by provider, service and project.
• Recommendations: the possible savings, priced per month and written for each provider, from environments left running to commitments worth taking.
• Budgets and alerts: an overall budget, a budget per cloud provider and a budget per project or app, with a threshold; an alert goes out at the threshold, when the forecast goes over the budget, and when it is exceeded.
• Dashboards: your own views, built by hand or described to the AI in one sentence, shared with the team or through a read-only public link.
• Exports: every view as PDF or CSV, kept in your generated files.
• Team: an owner, administrators, editors and readers, each with their rights, and two-factor sign-in mandatory for everyone.
• Cloud Intel: the articles and whitepapers Move2Cloud publishes, with a notification for each new one.

Enlarge

Recommendations → Follow-up: at the top, the potential, the savings committed and verified and what requires action; then each recommendation, with its priority, status and assignee.

Actual sizeClose

What is FinOps?

FinOps (a blend of “finance” and “DevOps”) is the practice that makes each team accountable for what the cloud it uses costs. In the cloud, spending is no longer an investment decided once a year: it is created every day, resource by resource, by the people who deploy. FinOps brings finance, engineering and the business together around the same figures, to decide quickly and knowingly.

The FinOps Foundation describes three phases, gone through in a loop:

• Inform: know what you spend, where, and on what, with costs allocated by project, team or environment;
• Optimise: reduce what is not used, resize what is oversized, commit to what runs permanently;
• Operate: set budgets, follow their gaps, and make the cost review a ritual, for example a monthly FinOps committee.

The goal is not to spend less at all costs, but to spend right: every euro should serve a use you have chosen.