Editorial methodology
How CloudArch Pro writes, sources, dates and corrects cloud architecture and pricing content.
Who writes the content
Ankit Mehta writes the technical library and the consulting pages. The author name on each article is the person who is accountable for the published text. CloudArch Pro does not publish anonymous technical articles.
Technical review
When a second qualified person reviews an article, that name appears as the technical reviewer and in structured data. When the author is also the person who checked the sources, the page says the article was written and technically verified by that person. It does not present self-review as an independent second reviewer.
Review means the named person checked the claims against the cited official documentation and against the stated assumptions. It does not mean a provider, a customer, or a certification body signed the page.
Accepted source types
- Current official provider documentation and pricing pages
- Provider regional-services or products-by-region lists
- Standards bodies and the FinOps Foundation for operating-practice definitions
- First-party operating experience, labelled as such when it is used
Secondary blogs, social posts and unsourced latency ranges are not accepted as evidence for a technical claim.
Provider-documentation verification
Technical articles name the product and the documentation date they apply to. Commands, console paths and service names are taken from the cited page, not from memory of an older UI. If a document has moved, the source URL is updated and the verification date changes.
Pricing verification
List prices and SKU availability change. Calculators use formulas plus rates you enter, or example rates with a source URL and a last-verified date. An estimate is not an invoice and is not a guaranteed saving. Re-check numbers against:
First-party experience
When a recommendation comes from work Ankit or the VigilesHQ consulting team has done, the page says so. First-party experience is not invented. Customer names, savings percentages, incidents and certifications are not fabricated to illustrate a point.
When judgment is used
Architecture pages include engineering judgment: which account split, which hub primitive, which region pair. Those recommendations are written as decisions for a named situation, with the provider differences and the limits stated on the same page. Preference is not presented as a vendor rule.
AI-assisted drafting
Drafts may be prepared with AI assistance. Every published page is reviewed by the named author against official provider documentation before it goes live. Invented customers, savings, incidents and unsourced measurements are not published.
Corrections
Factual errors are listed on the corrections page after they are fixed. The article’s last-verified or updated date changes when the correction affects a technical claim.
Update frequency
Documentation-dependent pages are re-checked when a source URL breaks, when a provider changes a named product, or when a reader reports an error. There is no claim that every page is re-read on a fixed calendar. Treat a last-verified date as the last time the cited sources were checked, not as a warranty that the provider UI is unchanged today.
How to report an error
Use the consultation form and describe the page URL, the claim, and the official source that contradicts it. You can also write to the contact method listed on the About page.