Improvement
This page is also available in Deutsch, Español, Français, Italiano, 日本語, and Português.
A perfect scale you can actually read
Numbers across PerfectScale now display the way your country writes them.
A scale is only useful if you can trust the reading. Until now, PerfectScale wrote every number the American way, whether you sat in Boise or in Berlin. If your country writes one thousand as 1.000 and one and a half as 1,5, that meant reading every dashboard in translation. A pod count, a CPU request, a savings figure, each one takes a small mental flip before it means what it says. Small flips add up, and in a cost review the price of getting one wrong is a number that's off by a factor of a thousand in front of your CFO.
Not anymore. Every number in PerfectScale now follows your convention, everywhere.
What you get
Numbers in your own format, consistently. If you're in Germany, you see 1.234,5 on every screen. If you're in the US, everything stays 1,234.5 and nothing changes for you. The rounding and the K/M/B shorthand you're used to are the same as before, only the separators moved.
Your exports and integrations are untouched. CSV files, YAML, and API responses keep the plain machine format they've always had, so nothing downstream needs to change. Costs still show in $/USD for now (but not for long).
Get started
There's nothing to set up. PerfectScale picks up the number format from your browser's language setting, the same one your banking site and spreadsheet already respect.
Want a different format, change that setting. If your team is spread across countries, look at your dashboards this week and tell us if any number still reads foreign. That's the feedback that gets the next one shipped.