Editant Pro

The complete content review system for serious teams

Multi-reviewer workflows, cryptographically signed approvals, a tamper-evident audit trail, per-link access controls, and an AI review assistant that uses your own provider key. Self-hosted on your own WordPress site, built on the Editant Free Core you can install today.

Available now. From €79 a year for a single site, with a 7-day free trial and a 14-day money-back guarantee on your first purchase.

See pricing

Installation guide

What Editant combines that nothing else does

Most content review tools cover one or two of the following. Editant covers all of them on the same self-hosted stack.

Login-free reviewer access. Reviewers click a link and review. No accounts, no SaaS dependency, no third party in the loop. Already in Editant Free Core.
Cryptographically signed approvals with external attestation. Every reviewer decision is Ed25519-signed and the audit-trail head hash is published outside the database so log completeness is end-to-end verifiable.
Per-link access control. Passwords, IP allow-lists, view-once links, and fine-grained expiry on every reviewer link.
Bring-your-own-key AI. Connect your own OpenAI, Google or Anthropic account through WordPress Connectors. No proxying through us, and no AI charges from us.
Signed webhooks. HMAC-signed webhooks for integration recipes, so your own tooling can follow every review event.

Access control

The Editant Free Core gives you tokenised preview links with expiry and revocation. Pro adds the access gates that regulated teams need before a link leaves the building.

Password-protected links. Set a password at link-creation time; the reviewer enters it before name and email. Hashed with Argon2id; the plain password is shown to the link author exactly once and never persisted.
IP allow-list. Restrict a link to specific IPv4 or IPv6 addresses, or to CIDR ranges. Misses are blocked at 403 and recorded in the audit log.
View-once links. The link burns after the first successful preview load. The original reviewer’s session continues to work for the rest of the link’s expiry; fresh sessions are refused.
Fine-grained expiry. Cap by maximum views, by hard datetime, or both together. Use for patterns like “this link lasts 24 hours or 5 views, whichever comes first”.
Anonymous review links. Let a reviewer skip the identity step where a name and email are not needed, per link.

Workflow and collaboration

Free Core’s per-post comments and binary approve / changes-requested decisions are enough for solo reviewers. Pro adds what real multi-reviewer cycles need.

Inline commenting. Comments anchor to specific blocks or to text ranges within a block, not just to the post as a whole. The anchored text is highlighted for the reviewer and in the editor, and anchors survive editing through block-id, block-path, and selection-text fallbacks.
Tracked-changes suggestions. Reviewers propose edits; the author accepts or rejects each one, from the sidebar or directly on the tracked change in the editor. Each suggestion has its own lifecycle: pending, accepted, rejected, or withdrawn.
Reviewer invitations. Invite a reviewer by email from the editor, with a reviewer directory so regular reviewers are one click away.
Multi-reviewer quorum. Configure how many of N assigned reviewers must approve before publish unlocks. The WordPress Publish button is gated server-side until quorum is met.
Deadlines and reminders. Set a per-post deadline; configurable reminder cadences fire automatically before, on, and after the deadline. Per-link override available where reminders should go to a single lead reviewer.
Comparison view. Block-aware diff showing what changed between the current post and the last signed snapshot. Side-by-side or inline, your choice.

AI review assistant

Bring your own key from OpenAI, Google or Anthropic through WordPress Connectors (WordPress 7.0 or later). Requests go straight from your site to your provider. Nothing passes through us, and every AI action is recorded in the audit log.

Comment to edit. Turn a reviewer’s comment into a concrete tracked-changes suggestion you can accept or reject like any other.
Contradiction detection. Find where reviewers disagree with each other, or with the text, before you start reconciling feedback.
Feedback-thread summaries. A long comment thread reduced to what was asked and what is still open.
Change summaries. A plain-language account of what changed since the last approved version, ready to send with a re-review request.
Article audit. A pre-publish readiness check against the context you set for the site: audience, tone, and house rules.

Compliance

If your team needs to prove the review actually happened, not just say so, this is the section to read. These features are bundled into every Pro tier. The price of compliance evidence is the same whether you are a solo consultant or a hundred-site network.

Signed approvals. Every reviewer decision is cryptographically signed with Ed25519. Public-key verifiable by any external party without sharing secrets. Exportable as JSON for machine verification or PDF for a court bundle.
Hash-chained audit trail. Tamper-evident, append-only event log. Every state-change (link created, comment posted, decision recorded, suggestion accepted, retention sweep applied) writes a row whose SHA-256 hash chains to the previous row. Alter any row after the fact and the chain breaks at that point and every point after it.
External attestation. The chain-head hash is published outside the database itself: scheduled email digests to a recipient list, plus webhook POSTs to a customer-supplied URL. Closes the wholesale-deletion gap that an internal-only log cannot.
Configurable retention. Per-site defaults with per-post overrides. Separate retention windows for comment content, reviewer personal data, content snapshots, and suggestion text, each with optional auto-purge. The audit log itself and the signed approval rows are never purged – their integrity is the chain.

How the audit chain actually works

The audit chain is a strictly-monotonic per-site sequence over a hash-chained event log. Each row records the event type (for example link.created, decision.recorded, retention.applied), the actor (WordPress user, anonymous reviewer, or system cron), a SHA-256 hash binding the row to the previous one, and a timestamp in UTC.

Verification is a single-pass walk. A third-party auditor can recompute every SHA-256 hash in the chain from the event payload and confirm the final value against the latest external attestation digest. No vendor-locked verification tooling, no need to share private keys, no need to trust the database operator.

Signed approvals work on the same principle. The signed payload is a canonical JSON document covering the post-content hash, the reviewer identity, the decision, the timestamp, and the link context. Anyone with the site’s public key can verify a signed approval, including legal counsel, regulators, and external auditors. The private signing key never leaves the site.

Integration and extension

Editant is built to fit your stack, not replace it.

Webhook event bus. Every state-change event can dispatch an HMAC-signed HTTP POST to customer-supplied URLs. Use it to feed Slack notifications, GRC tool ingestion, custom dashboards, or your own automation.
White-labelling. Replace Editant branding on reviewer-facing pages and notification emails with your own logo, colours, and sender name, and edit the email wording itself. The reviewer experience reads as yours, not ours.

Pricing

Three tiers on an annual subscription, priced by how many sites you run Pro on. Every tier has every feature.

Solo. €79 a year for one site.
Studio. From €325 a year for 5 sites, scaling to 30.
Network. €1,999 a year for unlimited sites.

Every subscription starts with a 7-day free trial, and your first purchase carries a 14-day money-back guarantee. The first 100 Solo customers can take a lifetime licence for €237 instead.

See pricing and buy

What’s next

Beyond this release, one thing is already designed and queued.

MCP integration for AI agents. Editant exposes its full reviewer surface over the Model Context Protocol so AI agents – Claude Desktop, in-house bots, CI pipelines – can drive review sessions from outside the dashboard. Ships as a separate add-on.