Every article on Cloud Cost Room exists to help engineering and finance teams spend less on cloud without breaking what they run. To be worth trusting, it has to be written by people who do this work, checked against primary sources, and corrected when it is wrong. This page is how we hold ourselves to that.
Who writes our content
Our content is written by named practitioners at Cloud Cost Room — primarily our co-founders, Morten Andersen and Fredrik Filipsson, who each carry 20 years in IT and cloud cost optimization across AWS, Azure, Google Cloud and OCI. Every article carries a visible byline naming its author and linking to that author's profile, so you always know who stands behind what you are reading. We do not publish anonymous or ghost-bylined content.
Written by humans
Our articles are written by people, not generated by AI. The guidance reflects first-hand engagement experience — what actually moves a cloud bill — not machine-paraphrased documentation. We use ordinary writing and editing tools, but the analysis, judgment, recommendations and final words are human. If we ever change that, we will say so plainly on the relevant content.
How we research and write
We ground every claim in primary sources: the cloud providers' own pricing pages, documentation, and release notes; the FinOps Foundation framework; and our own hands-on engagement experience. Where a figure comes from a provider, we treat the provider's current page as authoritative. Where a number is an illustrative or typical result, we say so rather than presenting it as a guarantee — see our disclaimer.
Review before publishing
Before an article goes live it is reviewed for technical accuracy and for cost-math correctness against current provider pricing. Practitioner guides on commitments, rightsizing and pricing instruments — the areas where a wrong number costs real money — get the closest scrutiny. Our review reflects the firm's vendor-neutral standard: recommendations are made on the customer's behalf, never to favor a provider.
Dating and updating
Cloud pricing and instruments change constantly, so currency is part of accuracy. Every article shows a publish or "last updated" indication, and our structured data carries machine-readable datePublished and dateModified. We revisit content when a provider changes pricing or releases something that changes the advice, and we refresh, re-date, or retire pages that have gone stale rather than leaving thin or outdated guidance live.
Independence and disclosure
We are independent and vendor-neutral. We earn no affiliate commissions, referral fees, or sponsorship from any provider or vendor, and we do not publish paid or sponsored content. Our full standing disclosure is on the disclaimer and disclosure page. This independence is the reason our recommendations can favor the reader's bill over any vendor's roadmap.
Corrections policy
We correct verified factual errors promptly. If you find a figure, claim or detail that is wrong or out of date, tell us through the contact page with the page and the specifics. When we confirm an error that affects the substance of a guide, we fix it, update the "last updated" date, and — for material corrections — note what changed. Typo-level fixes are made silently. We would rather be told we are wrong than leave a reader acting on a bad number.
Feedback
Suggestions, disagreements and "you missed X" notes are welcome through the same contact page. The library is better for them.
Spotted a mistake or a stale price? Send the page link and what is wrong via the contact page. We read every message and correct verified errors quickly.