How we write and check our content
Last updated
Plutonapps publishes articles, guides, comparisons and glossary entries for founders taking AI-built apps to production. This page explains who writes them, where their facts come from, how we keep them current and how to tell us when something is wrong.
Who writes our content?
Every article, guide, comparison and glossary entry on this site carries one byline: Irfan Habib, co-founder of Plutonapps, who leads the company's engineering. His author page lists the articles, guides and glossary entries published under his name.
Where do the facts come from?
Most facts come from the organization that owns them: a vendor's own documentation or pricing page, such as Lovable's, Supabase's or Stripe's; a regulator or standards body, such as the FTC, HHS or the W3C; or the text of the law.
Our articles end with a Sources list that names where each fact comes from, with its web address, and the day we checked them. The same day appears under the article's title as "Sources checked", and an automated test in our code fails if the two ever disagree. Figures that can change, such as a price or a plan limit, are given as of that day.
How do we keep pages current?
When we review a page, we re-open every source on its list. We change a fact only when a source shows it is out of date, and we cite that source. Then we move the "Sources checked" date, and the "Updated" date if any words changed. A date never moves without the check.
Pages whose facts go stale on a clock state their own review cycle. Our guide to the most advanced AI models says it is reviewed every 30 days, and an automated check in our code flags it the day after a review falls due.
How do we keep our prices consistent?
Our own plan prices are never typed into an article by hand. Every page that quotes them reads the figures from our pricing data, so a price change is made there and not page by page. An automated test fails if a price is written into a page directly.
Is this legal advice?
No. Our pages on compliance, such as HIPAA, accessibility and the ADA and which rules your product must meet, summarize what regulators and standards bodies publish and link to their pages. They are general information, not legal advice, and each says so. Laws have thresholds and exceptions a general page cannot cover, so ask a lawyer which ones apply to your product before you rely on any of it.
Where do our cover images come from?
Article cover images are either AI-generated illustrations, captioned "AI-generated illustration" under the image, or photos from Unsplash credited to their photographer.
How do I report a mistake?
Email [email protected] with the page's address and what you think is wrong, with a source if you have one. You can also write to us through our contact page.
If a source shows we got something wrong, we correct the page, cite that source and update the page's date.