Integrations
You don't write code — you tick a checkbox. Ready-made plugins wire modwall moderation into your platform: new images are scanned, suspicious ones go into the queue you already know, and the decision always belongs to a human. The plugins are free — they work with any plan, including the Free plan.
Chevereto
image galleries and photo hosting
New uploads are scanned automatically: safe ones are approved instantly, suspicious ones wait in Chevereto's native moderation queue.
- Replaces the ModerateContent integration that Chevereto is removing in V5.
- Two variants in one package: a docker-compose container (VPS) and a single PHP script + cron (shared hosting, no Docker).
- Fail-safe: if anything breaks, images simply wait for manual approval. Nothing is ever deleted automatically.
- Full taxonomy included in your plan: NSFW, weapons, violence — per your profile.
Requirements: Chevereto with „Moderate uploads” enabled + database access; PHP 7.4+ or Docker
Installation: Upload it, provide the API key and database credentials, enable dry-run mode — the whole thing takes about 10 minutes (README included).
WordPress
media, BuddyPress, WooCommerce reviews
Every image uploaded to the media library is scanned; suspicious ones are quarantined and wait for an administrator's decision.
- Quarantine instead of deletion: files disappear from public URLs, but the decision (restore/delete) always belongs to a human.
- A Modwall panel in the dashboard: preview held images, see model scores, Approve/Delete in one click.
- Moderator decisions from the modwall queue sync back automatically (WP-Cron).
- Dry-run mode to begin — a week of observation before anything changes.
Requirements: WordPress 6.0+, PHP 7.4+
Installation: A standard plugin: drop the directory into wp-content/plugins/, activate it, paste the API key in settings — no theme changes, no code.
phpBB 3.3+
forums and communities
Image attachments are scanned when a post is submitted; flagged posts go to the native approval queue (MCP) — moderators stay in their own panel.
- No new tools for moderators: decisions happen in the familiar MCP.
- A named trace of every scan in the admin log (file, results, decision).
- Fail-safe: when the API is unavailable, a post with an unscanned image waits in the queue instead of going public.
- Settings in the ACP: key, dry-run mode, failure behavior.
Requirements: phpBB 3.3+, PHP 7.4+
Installation: Drop the directory into ext/, enable it in ACP → Customise, paste the API key in ACP → Extensions → Modwall. Dry-run mode by default.
Every package includes a README with step-by-step instructions. All plugins start in dry-run mode — for the first week they only log decisions, changing nothing. You set thresholds, categories, and mode in the moderation profile pinned to your key — the plugin has no policy of its own, so nothing drifts out of sync.
Rules shared by every integration
A human decides
The plugin detects, scores, and routes to review. It doesn't remove content automatically — less legal risk and fewer angry users.
Fail-safe by design
API outage, exhausted quota, a dead connector? The content simply waits for approval. A failure never publishes an unscanned image.
The EU or your own server
The modwall cloud processes in the EU and stores nothing. The self-hosted option — images never leave your infrastructure at all. Every plugin has a configurable API URL.
Don't see your platform here?
Discourse — coming soon · Invision Community — coming soon · Your platform — get in touch — the connector contract is open
Every integration is a thin adapter over the same API — if your engine has an upload hook, you can wire up modwall yourself in an hour (quickstart, API reference), or get in touch — demand sets the order in which we build plugins.