| Lang Forge |
- Manual post / page / CPT translation linking
|
- Usage telemetry is off until you switch it on: every send reads the site option `forge_telemetry_consent` first, and stops when it is not "1".
- With telemetry on, batches of events POST to https://api.avakode.com/telemetry/batch.
- The in-admin feedback form POSTs your rating and comment to https://api.avakode.com/feedback when you press Send.
- The Forge Suite dashboard health card GETs https://api.avakode.com/health.
|
- Pro is a separate plugin. With no Pro add-on loaded the plan is free, whatever is stored in the database.
- Licence activation and every AI request go to https://api.avakode.com.
- AI actions spend credits from your Avakode balance; the price per action is decided on the server (1 credit for a translation, 3 for a whole post).
- A request over 10,000 tokens costs a multiple of the base action price.
|
- Free features keep working. The wp.org base ships no licensing SDK: without the Pro add-on answering "pro" through the `forge_pro_plan` filter the plan reads free.
- When the paid ladder answers "free" in so many words, the stored grace marker `forge_license_last_pro_at` is cleared and Pro gates close on the next admin request.
- Pro keeps working for 24 hours of silence from the licence server — that window covers an outage, not a revoked licence.
- A lapse removes no data. Tables and options go away only when you uninstall the plugin.
|
- An export of translations from the admin screen.
- Pro exports the translation memory.
- Translations are kept until you delete them; there is no age-based retention or pruning window in the stored-translations table.
|
| Rank Forge |
- On the free tier, the 0-100 on-page score is computed locally from the post's own content (title, headings, keyword placement, length) with no network calls or database reads.
|
- Usage telemetry is off until you switch it on: every send reads the site option `forge_telemetry_consent` first, and stops when it is not "1".
- With telemetry on, batches of events POST to https://api.avakode.com/telemetry/batch.
- The in-admin feedback form POSTs your rating and comment to https://api.avakode.com/feedback when you press Send.
- The Forge Suite dashboard health card GETs https://api.avakode.com/health.
|
- Pro is a separate plugin. With no Pro add-on loaded the plan is free, whatever is stored in the database.
- Licence activation and every AI request go to https://api.avakode.com.
- AI actions spend credits from your Avakode balance; the price per action is decided on the server (1 credit for a translation, 3 for a whole post).
- A request over 10,000 tokens costs a multiple of the base action price.
|
- Free features keep working. The wp.org base ships no licensing SDK: without the Pro add-on answering "pro" through the `forge_pro_plan` filter the plan reads free.
- When the paid ladder answers "free" in so many words, the stored grace marker `forge_license_last_pro_at` is cleared and Pro gates close on the next admin request.
- Pro keeps working for 24 hours of silence from the licence server — that window covers an outage, not a revoked licence.
- A lapse removes no data. Tables and options go away only when you uninstall the plugin.
|
- Stored analyses are kept until the post is re-analyzed; there is no age-based retention window (one row per post, replaced in place on each analysis).
- Rank Forge does not export its stored analyses or reports; the only CSV export in the Forge Suite is the shared cross-product results summary, which Rank Forge does not feed data into.
|
| Form Forge |
|
- Usage telemetry is off until you switch it on: every send reads the site option `forge_telemetry_consent` first, and stops when it is not "1".
- With telemetry on, batches of events POST to https://api.avakode.com/telemetry/batch.
- The in-admin feedback form POSTs your rating and comment to https://api.avakode.com/feedback when you press Send.
- The Forge Suite dashboard health card GETs https://api.avakode.com/health.
|
- Pro is a separate plugin. With no Pro add-on loaded the plan is free, whatever is stored in the database.
- Licence activation and every AI request go to https://api.avakode.com.
- AI actions spend credits from your Avakode balance; the price per action is decided on the server (1 credit for a translation, 3 for a whole post).
- A request over 10,000 tokens costs a multiple of the base action price.
|
- Free features keep working. The wp.org base ships no licensing SDK: without the Pro add-on answering "pro" through the `forge_pro_plan` filter the plan reads free.
- When the paid ladder answers "free" in so many words, the stored grace marker `forge_license_last_pro_at` is cleared and Pro gates close on the next admin request.
- Pro keeps working for 24 hours of silence from the licence server — that window covers an outage, not a revoked licence.
- A lapse removes no data. Tables and options go away only when you uninstall the plugin.
|
- Entries download as CSV from the entries screen.
- Submissions are kept until you delete them; there is no age-based retention or pruning window in the submissions table.
|
| Field Forge |
- 32 field types, ACF-compatible
- ACF compatibility layer (import existing ACF groups + values)
|
- Usage telemetry is off until you switch it on: every send reads the site option `forge_telemetry_consent` first, and stops when it is not "1".
- With telemetry on, batches of events POST to https://api.avakode.com/telemetry/batch.
- The in-admin feedback form POSTs your rating and comment to https://api.avakode.com/feedback when you press Send.
- The Forge Suite dashboard health card GETs https://api.avakode.com/health.
|
- Pro is a separate plugin. With no Pro add-on loaded the plan is free, whatever is stored in the database.
- Licence activation and every AI request go to https://api.avakode.com.
- AI actions spend credits from your Avakode balance; the price per action is decided on the server (1 credit for a translation, 3 for a whole post).
- A request over 10,000 tokens costs a multiple of the base action price.
|
- Free features keep working. The wp.org base ships no licensing SDK: without the Pro add-on answering "pro" through the `forge_pro_plan` filter the plan reads free.
- When the paid ladder answers "free" in so many words, the stored grace marker `forge_license_last_pro_at` is cleared and Pro gates close on the next admin request.
- Pro keeps working for 24 hours of silence from the licence server — that window covers an outage, not a revoked licence.
- A lapse removes no data. Tables and options go away only when you uninstall the plugin.
|
- Pro serves field values over a headless endpoint, which is also how you take them out.
- Field values live in their own table but are deleted automatically when their post is deleted, so they live exactly as long as the post; there is no separate retention window.
|
| Guard Forge |
- Files judged against the official wordpress.org build
- An audit log chained row to row, and verifiable
- Core and wordpress.org plugins checked against the published build, not against yesterday’s snapshot
|
- Usage telemetry is off until you switch it on: every send reads the site option `forge_telemetry_consent` first, and stops when it is not "1".
- With telemetry on, batches of events POST to https://api.avakode.com/telemetry/batch.
- The in-admin feedback form POSTs your rating and comment to https://api.avakode.com/feedback when you press Send.
- The Forge Suite dashboard health card GETs https://api.avakode.com/health.
|
- Pro is a separate plugin. With no Pro add-on loaded the plan is free, whatever is stored in the database.
- Licence activation and every AI request go to https://api.avakode.com.
- AI actions spend credits from your Avakode balance; the price per action is decided on the server (1 credit for a translation, 3 for a whole post).
- A request over 10,000 tokens costs a multiple of the base action price.
|
- Free features keep working. The wp.org base ships no licensing SDK: without the Pro add-on answering "pro" through the `forge_pro_plan` filter the plan reads free.
- When the paid ladder answers "free" in so many words, the stored grace marker `forge_license_last_pro_at` is cleared and Pro gates close on the next admin request.
- Pro keeps working for 6 hours of silence from the licence server — that window covers an outage, not a revoked licence.
- A lapse removes no data. Tables and options go away only when you uninstall the plugin.
|
- Brute-force log rows are kept 30 days by default, the audit log 60; both are settings, 1–365 days.
- The audit-log retention setting is the second of the two, with the same 1–365 bounds.
- A report downloads as a file from the plugin screen; the Pro audit export is a separate download.
- Pro audit export.
|
| Velocity Forge |
- INP and LCP named down to the plugin
- The regression names the assets an update changed
- Recovery drill — a button that presses the escape hatches on a day when nothing is wrong: the panic constant, a probe write to the panic file's directory, a real loopback request to the secret panic route with the real secret, the safe-mode option's round trip, and the autoload backups table. Everything it touches is put back exactly as it was found, including the on-disk copy of the secret
|
- Usage telemetry is off until you switch it on: every send reads the site option `forge_telemetry_consent` first, and stops when it is not "1".
- With telemetry on, batches of events POST to https://api.avakode.com/telemetry/batch.
- The in-admin feedback form POSTs your rating and comment to https://api.avakode.com/feedback when you press Send.
- The Forge Suite dashboard health card GETs https://api.avakode.com/health.
|
- Pro is a separate plugin. With no Pro add-on loaded the plan is free, whatever is stored in the database.
- Licence activation and every AI request go to https://api.avakode.com.
- AI actions spend credits from your Avakode balance; the price per action is decided on the server (1 credit for a translation, 3 for a whole post).
- A request over 10,000 tokens costs a multiple of the base action price.
|
- Free features keep working. The wp.org base ships no licensing SDK: without the Pro add-on answering "pro" through the `forge_pro_plan` filter the plan reads free.
- When the paid ladder answers "free" in so many words, the stored grace marker `forge_license_last_pro_at` is cleared and Pro gates close on the next admin request.
- Pro keeps working for 6 hours of silence from the licence server — that window covers an outage, not a revoked licence.
- A lapse removes no data. Tables and options go away only when you uninstall the plugin.
|
- Field beacons are kept 30 days by default; the setting accepts 1–365.
- What `beacon_retention_days` counts changed in 1.1.0, and a one-time migration rewrote the stored value.
- Pro exports field data as a download.
|
| Draft Forge |
- Five checks before publish, and the fifth one reads
- The author generates, the editor approves
- The fifth check, and the only one that reads rather than counts. A body can clear every threshold above and still open with "In today's fast-paced world", promise to delve into its own title, and repeat one sentence shape forty times. The lint answers with findings instead of a score: a bundled list of 132 stock phrases measured as a density per 1000 words, four kinds of repetition, an introduction that only restates the title, a rhythm too even to have been written by a person, dates and figures that cannot be true, and text laid out as a list where it should be prose. Every finding quotes the sentence and says what is wrong with it, in the Queue tab and on the refresh review screen. Three strictness settings — lenient, standard, strict — decide which findings stop a draft; the checks themselves always run at all three. Free, and it costs no credits: the credits already paid for the draft
|
- Usage telemetry is off until you switch it on: every send reads the site option `forge_telemetry_consent` first, and stops when it is not "1".
- With telemetry on, batches of events POST to https://api.avakode.com/telemetry/batch.
- The in-admin feedback form POSTs your rating and comment to https://api.avakode.com/feedback when you press Send.
- The Forge Suite dashboard health card GETs https://api.avakode.com/health.
|
- Pro is a separate plugin. With no Pro add-on loaded the plan is free, whatever is stored in the database.
- Licence activation and every AI request go to https://api.avakode.com.
- AI actions spend credits from your Avakode balance; the price per action is decided on the server (1 credit for an outline, 5 for the body — about 6 for a draft).
- A request over 10,000 tokens costs a multiple of the base action price.
|
- Free features keep working. The wp.org base ships no licensing SDK: without the Pro add-on answering "pro" through the `forge_pro_plan` filter the plan reads free.
- When the paid ladder answers "free" in so many words, the stored grace marker `forge_license_last_pro_at` is cleared and Pro gates close on the next admin request.
- Pro keeps working for 6 hours of silence from the licence server — that window covers an outage, not a revoked licence.
- A lapse removes no data. Tables and options go away only when you uninstall the plugin.
|
- Generated drafts are ordinary WordPress posts with no automatic pruning.
- The credit-usage log behind draft generation drops rows older than a year via the shared daily cleanup job.
- There is no export of drafts or generation history.
- The only CSV-related feature in the plugin imports decline data from elsewhere, not the other way round.
- Uninstalling the plugin drops its table.
|
| Flow Forge |
- Twenty ready-made recipes, and no JSON to write
- Retry a failed run from the step it failed on
- Visual flow builder (form editor and drag-and-drop canvas), unlimited active flows
|
- Usage telemetry is off until you switch it on: every send reads the site option `forge_telemetry_consent` first, and stops when it is not "1".
- With telemetry on, batches of events POST to https://api.avakode.com/telemetry/batch.
- The in-admin feedback form POSTs your rating and comment to https://api.avakode.com/feedback when you press Send.
- The Forge Suite dashboard health card GETs https://api.avakode.com/health.
|
- Pro is a separate plugin. With no Pro add-on loaded the plan is free, whatever is stored in the database.
- Licence activation and every AI request go to https://api.avakode.com.
- AI actions spend credits from your Avakode balance; the price per action is decided on the server (1 credit for a translation, 3 for a whole post).
- A request over 10,000 tokens costs a multiple of the base action price.
|
- Free features keep working. The wp.org base ships no licensing SDK: without the Pro add-on answering "pro" through the `forge_pro_plan` filter the plan reads free.
- When the paid ladder answers "free" in so many words, the stored grace marker `forge_license_last_pro_at` is cleared and Pro gates close on the next admin request.
- Pro keeps working for 6 hours of silence from the licence server — that window covers an outage, not a revoked licence.
- A lapse removes no data. Tables and options go away only when you uninstall the plugin.
|
- Run history is kept 30 days by default; the setting accepts 1–365.
- A scheduled collector deletes runs past the retention setting.
- Pro downloads recipe packs as files.
- There is no export of run history itself; the only CSV export in the codebase is the suite's shared cross-product results summary, unrelated to individual flow runs.
|
| Clearway Forge |
- AI-traffic attribution & revenue
- Every AI visit and every order it leads to, attributed with first-party data.
- Estimates are labelled as estimates and reported separately from proven revenue
|
- Attribution is computed from your own site traffic and orders.
- Maintenance GETs the published IP-range lists of the AI crawlers it recognises and stores them in an option.
- Licence checks POST to https://api.avakode.com.
|
- Agent permissions, the journal and undo are Pro, in a separate plugin.
- The monthly digest email is Pro.
|
- An expired licence is a named outcome with its own message; the free attribution and llms.txt surfaces keep running.
- Expired and inactive are separate licence states, so a revoked licence is not read as a server hiccup.
- A lapse deletes no rows: options go away on uninstall.
|
- Attribution rows are kept 400 days by default.
- Maintenance never prunes below 30 days, whatever the setting says.
- Pro exports rows as CSV.
|
| Profit Forge |
- Evidence rows + fix steps in $
- Coupon stacking — an "individual use only" coupon that ended up combined with other coupons, and how much extra discount that gave away.
- Refund without restock — money refunded, goods never returned to stock, and the inventory value now missing.
|
- Findings are computed over your own WooCommerce tables; no order line is sent to Stripe.
- Pro reads payouts and fees from https://api.stripe.com/v1 with your key, read-only.
- Licence checks POST to https://api.avakode.com.
|
- Pro is a separate plugin under pro/; the free rules run without it.
- Reading Stripe payouts and fees needs your own Stripe key.
|
- The licence transport has an explicit expired outcome; Pro rules stop and the free ruleset keeps running.
- An expired licence is parsed as such rather than read as a network failure.
- A lapse removes no findings: the table survives until uninstall, and even then the `pforge_keep_data_on_uninstall` option keeps it.
|
- Uninstalling drops the findings table unless the option `pforge_keep_data_on_uninstall` is set to 1.
- Pro exports a report as CSV.
- Findings are kept indefinitely on a live site; the findings table is append-only and nothing prunes or expires old rows.
|
| Inclusive Forge |
- The WordPress plugin adds `<meta name="inclusiveforge-verify" content="…">` to your site head, from a value you paste in.
- With the licence key from your purchase e-mail, the plugin connects the store to your account and fills in the verification value and the webhook secret itself, so nothing has to be pasted by hand.
- Your last scan is rendered in wp-admin from what the plugin already stored.
- "Re-test now" is a request to the service, not a scan inside your install.
|
- Scanning runs on Cloudflare Workers with Browser Rendering and axe-core, not in your WordPress install: your page is fetched and rendered there.
- A scan of a site needs proof you own it, or an explicit request for a one-off public exposure check behind a rate limit and Turnstile.
- Ownership is proved by the verification meta tag on your home page, printed by the plugin or added to your theme by hand, or by a file at `/.well-known/inclusiveforge-verify.txt`.
- Scan traffic to your site happens only inside the scan pipeline, through Queues; a portal request makes no scan call of its own.
- Asking for a sign-in link does send one message out: your e-mail address goes to the mail provider Resend, in a POST to `api.resend.com`, because that letter carries the link.
- The one-off public exposure check posts your Turnstile token to `challenges.cloudflare.com` before the request is queued.
- When you connect a store with a licence key, and again when you press Check again or Refresh, the plugin sends the key and your site address to `app.inclusiveforge.com`. With a key stored in the plugin, opening the settings screen sends the same status request at most once every six hours.
- When a key is checked, on connecting a store or on `app.inclusiveforge.com/activate`, Inclusive Forge sends it to the Avakode licence service at `api.avakode.com`.
|
- Inclusive Forge is a hosted service: tenants, scans, findings and the journal live in D1, screenshots and evidence packs in R2.
- Findings are mapped axe → WCAG 2.1 AA → EN 301 549 by a table the service ships.
- There is no Pro add-on to install: the plan lives with your account, not on your site.
|
- A sign-in link you ask for works once and stops working after 15 minutes.
- The sign-in link in the e-mail that opens your account after payment works once and lasts 24 hours.
- A portal session lasts 30 days.
- Refunds: within 14 days of a payment you can ask for a refund in full, by email, the same 14 days as in Avakode's refund policy.
- When a licence is cancelled, refunded or expires, scans and re-tests stop, and the portal and the plugin say which of the three it is. A payment that is being retried does not stop them.
- Your findings, journal and evidence pack stay in the portal for as long as the account exists; access is not time-limited.
|
- Webhook deliveries that reached a settled status are deleted after a cutoff.
- Evidence packs and screenshots are stored in R2 and downloadable from the portal.
- Scans and findings are kept indefinitely; findings and the ledger are append-only and nothing deletes them.
- Screenshots are stored in R2 and nothing in the codebase deletes them.
- Export is the per-site journal page, printable from the browser; there is no bulk download across sites.
|
| Renew Forge |
- A compliance check of 14 items about your store: status, what was found, what to do.
- A one-click cancel button; the request is journaled before the status changes, and a second press never cancels twice.
- An evidence journal of every cancellation; IP address and browser are kept only as hashes keyed with this site's own salt.
|
- The free plugin makes no outbound requests: a package test fails on any wp_remote_*, curl or fsockopen call.
- Pro sends the licence key, product name and site address to api.avakode.com — on a Licence-screen button, once a day while a key is stored, and on deactivation to release the site; updates come from the same host only while the licence is active. Nothing about orders or customers.
- SMS is off until you pick Twilio or Vonage; then the reminder text and the customer's phone number go to that provider with your own credentials. A cooling-off refund goes through the order's own payment gateway.
|
- WooCommerce Subscriptions: without it the plugin shows a notice and touches no subscription.
- Renewal reminders need the separate Pro add-on with an active licence.
- SMS reminders need a licence plan that includes SMS (store-sms or agency) and your own Twilio or Vonage account.
|
- Reminder planning, the checkout acknowledgement and the cooling-off button switch off with the licence.
- A shop that cannot reach the licence server keeps working on the last known state; a stale state only triggers a re-check.
- A lapse deletes nothing: the retention purge, too, runs only while the licence is active.
|
- The journal is append-only — its store has no UPDATE and no DELETE — and exports to CSV exactly as stored.
- Deleting the plugin keeps the journal and settings unless delete-on-uninstall was ticked first.
- Pro deletes evidence older than the retention you set (six years by default; 0 keeps it) and journals each purge; Tools → Erase Personal Data unlinks the customer and strips phone numbers and e-mails from error texts — the rest stays.
|