Editorial model

Trust is a product requirement, not a footer link.

Portstack is useful only if buyers can see how information is sourced, where the gaps are, and how vendor influence is handled. The editorial model keeps the directory disciplined while it is still early.

sold editorial treatment
No
correction intake
Yes
unknown fields
Visible
Principles

Profiles should help a buyer make a defensible shortlist.

The editorial standard is intentionally practical. It does not try to mimic a newsroom manual; it defines the guardrails that keep a product directory trustworthy.

Use structured facts first

Category, deployment, integrations, pricing transparency, and capability fields are more useful than broad vendor positioning.

Avoid unsupported judgment

Portstack does not publish universal winners, star ratings, or unverified superlatives.

Keep buyer email first-party

Buyer communications should not become a hidden vendor channel without an explicit product decision.

Corrections

Vendors can challenge facts without owning the narrative.

Portstack should be easy to correct and hard to capture. A correction that points to a specific field and source is more useful than a rewrite request.

Accepted

Missing products, outdated product names, wrong category placement, incorrect links, and better public sources.

Reviewed

Capability claims, customer signals, integrations, and deployment statements are checked against available evidence.

Rejected

Requests to remove accurate but inconvenient information, hide uncertainty, or change comparison logic for positioning.

Commercial boundary

If monetization arrives, it must not rewrite the directory.

Sponsored placement may become a business model later, but it cannot change organic profile content, comparison rows, or whether a product belongs in a category.

Paid placement must be labeled

Buyers should never have to infer whether a placement is commercial.

Comparison rows stay editorial

Vendors do not buy better capability values, hidden gaps, or different field models.

Disputes need a trail

As volume grows, corrections should move from ad hoc intake to a clearer review workflow.

Correction path

Found something wrong or missing?

Send the page, field, and source. Precise corrections are the fastest way to improve the directory.