Who writes here
Articles identify their author or publishing organization in the byline. An AFFiNE team byline identifies the publisher; it does not, by itself, mean that every product mentioned was tested or that a particular person reviewed the article. Named contributors, qualifications, and review credits should be used only when their involvement can be verified.
Information about AFFiNE is available on about us. For comparison hub content such as /vs, the article should explain the basis for its product claims and recommendations.
How we research, test, and compare
- Distinguish source research from hands-on testing. A comparison may be based on official documentation without being a hands-on review. Its method note should say which evidence was used. When an article reports hands-on testing, it should identify the tested product, version or plan, date, environment, tasks, and relevant evidence. Untested behavior must not be presented as an observed result.
- Date pricing and plan information. Pricing claims should link to the vendor's pricing page or another attributable source and state when they were checked. Comparisons should distinguish billing periods, currencies, user roles, plan limits, and optional charges. An article's update date is not proof that every price was rechecked; the article should state the scope of its review.
- Tie feature claims to appropriate sources. Product documentation, release notes, and version-specific license files are preferred sources for feature and licensing claims. A vendor's description of a feature should be distinguished from our own observations and from an editorial judgment about where it may fit. Source claims should not be extended to untested plans or deployment configurations.
- Make analysis and examples inspectable. When an article publishes measurements or calculations, it should identify the inputs, method, conditions, and limitations. Downloadable templates and fictional examples should be labeled as such. A blank evaluation sheet, mock scenario, or conceptual diagram is not evidence of a completed product test or customer outcome.
Conflict of interest disclosure
AFFiNE is a commercial product that competes with some of the tools we cover. The following standards apply to comparisons:
- Identify our relationship to AFFiNE. Articles discussing our product should make the publishing relationship clear so readers can distinguish a vendor-authored guide from an independent review.
- Disclose commercial relationships. Sponsored content, contributed placements, and affiliate relationships must be clearly identified where they apply. A commercial relationship is not evidence of product quality and must not be presented as an independent endorsement.
- Explain meaningful tradeoffs. Comparisons should describe the requirements that favor each relevant option, including cases where another product or retaining an existing tool may be appropriate. Claims that something is best or faster need supporting evidence and a defined scope.
- Include AFFiNE only where it is relevant. Product mentions and links should help the reader complete the task discussed in the article. They should not substitute for an answer or imply that AFFiNE meets requirements that have not been verified.
Updates and review scope
- Review claims when the underlying evidence changes. Product releases, pricing changes, license changes, and verified reader feedback are reasons to revisit affected passages. No fixed testing period or universal update schedule should be inferred from this policy.
- Separate publication from revision. Preserve the original publication date and update the revision date when the content changes. A material correction should identify what changed; a new date alone must not imply that the entire article was retested.
- State unresolved limits. If a plan, feature, migration path, or configuration has not been checked, the article should say so and identify what the reader needs to verify before relying on it.
Corrections and reader feedback
To report an error — such as an outdated price, a misattributed feature, a broken link, or a misleading conclusion — email contact@affine.pro with the article URL, the specific claim, and supporting evidence where available. Reports should be assessed against the relevant sources; material corrections should be recorded on the affected article. This policy does not promise a response or correction deadline.
A vendor's disagreement is not by itself a reason to change a comparison. Factual corrections should follow the evidence, and editorial judgments should explain their criteria and limitations.
Sources and production methods
- Vendor product documentation, pricing pages, release notes, and license files for the version being discussed
- Hands-on observations and test artifacts, where testing was actually performed and documented
- Attributable research, standards, and other primary sources appropriate to the subject
- Community reports as contextual evidence, clearly separated from verified product specifications
AI and other tools may assist with research, organization, and drafting. Their output is not a primary source for product facts or a substitute for testing. Articles should explain material production methods where that context helps readers assess the work, and should not invent author credentials, customer stories, or review results.
License and openness claims
AFFiNE's licensing depends on the release and component. The root LICENSE file and the relevant component's license are the authoritative starting points. The linked canary branch changes over time; deployment decisions should use the files from the exact release being deployed.
- Editor and client components. AFFiNE includes MIT-licensed editor and client code. Check the chosen release's root license and any component-specific notices before describing a particular component's terms.
- Server components. Server releases may include open-source CE components and components under AFFiNE Enterprise Edition terms. Do not describe the entire backend as a single license without checking the selected release. Review the server license and any applicable commercial agreement for the intended use.
- Third-party components. Bundled dependencies retain their applicable upstream terms. Check their notices alongside AFFiNE's own licenses.
Open-source licensing, source availability, a free usage allowance, and self-hosting describe different things. Enterprise Edition terms should not be presented as an OSI-approved open-source license, and self-hosting should not be described as an unlimited free license or a guarantee that every feature works offline.
What this policy covers
These standards apply to comparison pages under /vs, guides and evaluation content under /blog, and related editorial materials. Product pages such as /ai and /whiteboard are marketing pages; their claims should still accurately describe the available product. This policy is a statement of standards, not evidence that a particular article completed every type of review. Consult each article's method note and sources for its actual scope.