Commento is a privacy-first commenting platform that embeds via a small script tag, with comment threads stored in Commento's own backend (self-hosted or managed). The WordPress plugin is responsible for inserting the embed, optionally per post type, and tracking which posts opt in. The default plugin screen exposes those options as toggles; what it does not expose is a per-post audit of where the embed actually runs.

SleekView reads wp_posts joined to wp_postmeta on commento_enabled and any related commento_* keys, and renders the configuration as a queryable grid. Filter to posts missing the embed to find rollout gaps, scope by author to spot writers who forget the toggle, or sort by enablement date to verify the migration window held. Saved per-role views give migration leads a rollout grid, editors an authoring audit and site ops a CPT coverage check.

Scope stays honest. SleekView does not mirror Commento's threads, votes or moderation actions, all of which live in the Commento backend and would only rot if duplicated. It charts the WordPress side of the bridge: which posts run the embed, when and where the gaps are.

Commento intentionally keeps conversation data off WordPress, which is a feature for privacy-conscious teams and a constraint for teams that want one place to see how the integration is performing. The data WordPress still owns is the embed footprint: which posts run the widget, when it was enabled and which authors and post types are in scope. The shape of the audit matters: a per-post grid of post_id, post_type, author, embed flag and enablement date shows whether the rollout is sticking, where it skipped post types and which authors quietly drop the toggle.

Same plugin options, same per-post meta, completely different posture toward the rollout. The grid renders the WordPress half of the integration as a row-level audit, which is the difference between assuming Commento is everywhere and proving it.