Editorial standards
How everything on this site gets written, checked, and corrected.
Who writes here
Posts carry the name of the person who wrote them. Today that is Abdelrahman Essawy, who builds the platform. Changelog entries are written in the company voice because they describe shipped work rather than an argument, and each one maps to a real merged change.
We only announce what is live
A changelog entry is written the day the change reaches production, and it is dated that day rather than the day it was written. Nothing is announced as available while it is still behind a flag, on a branch, or on the roadmap. If a capability needs a paid plan, the entry says so.
Numbers are measured, not estimated
Benchmarks, file sizes, latencies, and prices come from real runs and real config. When a figure is approximate it is written as approximate. When it depends on your input or plan, the post says what it depends on. Competitor pricing is dated, sourced from public pages, and re-checked rather than remembered.
Comparisons name the losses
Comparison pages say where a competitor is the better choice. A comparison that finds no case against us is marketing wearing a table, and developers see through it immediately.
Corrections
When something published here turns out to be wrong, the page is fixed and its modified date changes. Corrections that alter a conclusion are noted in the page rather than quietly edited away. Mail [email protected] if you find one.
AI assistance
Drafting tools are used the way any other tool is used here. Nothing publishes without a human reading it, checking the claims, and putting a name on it. The judgment, the numbers, and the accountability are human, and that is the part that matters.