# KimaAI business model: free with branding, pay to remove (BM)

Research date: 13 November 2026. Prices are as shown on the linked pages on that date. Anything not confirmed on a source is marked [unverified].

## Decision

Owner delegated, my recommendation (2026-11-13): option b now, c later. Implemented in track BM (BM-2 to BM-5); setting up an Agency plan or a price in Freemius stays with the owner.

## Summary

- A plugin hosted on WordPress.org cannot ship "free with branding, pay to remove" as a plugin feature. Guideline 10 says every "Powered by" credit must be opt-in and off by default, and guideline 5 forbids locking features (including the off switch) behind payment.
- The products that run this model and sit on WordPress.org (Tidio, tawk.to, Crisp, CookieYes) all do it through a **hosted service**. The branding belongs to the service's output, which guideline 10 explicitly allows.
- **KimaAI today breaks guideline 10.** `poweredBy` defaults to `true` in free code (`app/Admin/config/chatbot.php`, line ~775), the link has no `nofollow`, and the readme does not mention it. This needs fixing whatever model is chosen.
- Recommendation: fix compliance now, ask for the credit in the setup wizard (opt-in), and sell white-label as part of a paid Agency plan. Only make every feature free once there is a hosted KimaAI service that earns the money (option c).

## 1. Products using "free with branding, pay to remove"

| Product | Free tier | Branding | Cost to remove | Enforcement | On WordPress.org |
|---|---|---|---|---|---|
| [tawk.to](https://www.tawk.to/pricing/) | All features, "free for life" | "Powered by tawk.to", which the pricing page calls "tiny", in the widget footer. Also on emails, the chat page and the knowledge base ([help](http://help.tawk.to/article/setting-up-the-remove-branding-add-on)). Partners can swap in a referral link | "$29/month" per the pricing page. The help article says it is charged "per property". A WordPress.org reply quotes lower annual prices [unverified] | Hosted widget, branding switched on the server | Yes, [tawkto-live-chat](https://wordpress.org/plugins/tawkto-live-chat/), 100,000+ installs |
| [Tidio](https://www.tidio.com/pricing/) | 50 conversations, 10 seats, 50 Lyro AI conversations (lifetime) | Tidio branding in the widget (size and position [unverified]) | "No Tidio branding" listed as an "Add-on (16.67 USD/mo.)". The plan it attaches to is unclear [unverified]. "Custom branding" is in Plus, from $300/mo | Hosted widget, account plan | Yes, [tidio-live-chat](https://wordpress.org/plugins/tidio-live-chat/), 70,000+ installs |
| [Crisp](https://crisp.chat/en/pricing/) | Chat widget, inbox, 2 seats, no AI credits | Watermark "We run on Crisp" (position [unverified]) | White labelling is only in Plus, $295/month per workspace. Not included in Mini ($45) | Hosted widget, account plan | Crisp has a WordPress plugin (the pricing page says so). Its directory listing was not checked [unverified] |
| [Chatbase](https://www.chatbase.co/pricing) | No free plan shown, only a 7-day trial on Basic | "Powered By Chatbase" in the deployed agent | Add-on "Remove 'Powered By Chatbase'", $99/month | Hosted agent | Not checked [unverified] |
| [Botpress](https://botpress.com/pricing) | 100 conversations, 3 seats, 3 agents | Botpress branding in the webchat | "Whitelabel webchat" in Plus, $150/mo billed annually | Hosted webchat | Not checked [unverified] |
| [Jotform](https://www.jotform.com/pricing/) | 5 forms, 100 submissions/month, 5 AI agents | "Jotform branding included" | Bronze, $39/month ($34/month billed yearly) | Hosted forms | Has a WordPress embed plugin [unverified] |
| [CookieYes](https://wordpress.org/plugins/cookie-law-info/) | Banner, blocking, cookie manager (plugin). Scanner, consent log and policies need the free web app | "Powered by CookieYes" on the banner | Only on the Ultimate web-app plan (price [unverified]) | Service-side: paid features come from the CookieYes web app. Whether the plugin shows the credit without the web app [unverified] | Yes, 1+ million installs |
| [MailPoet](https://account.mailpoet.com/) | Starter: up to 5,000 emails/month through the MailPoet Sending Service | MailPoet branding in emails (wording [unverified]) | "Remove MailPoet branding" on Business (price not shown) | Sending service | Yes |
| [WPBot](https://wordpress.org/plugins/chatbot/) | WordPress AI chatbot, free core | Whether the free build shows a credit [unverified] | "White Labelling" in the Master Lifetime deal (price [unverified]) | Licence key, Pro code | Yes, 5,000+ installs |

The pattern: every WordPress.org plugin that brands by default is a thin client for a **hosted service**. WordPress-native chatbots (WPBot, and AI Engine as far as checked) sell white-labelling as a paid-tier feature instead.

## 2. WordPress.org rules

Source: [Detailed Plugin Guidelines](https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/).

### Guideline 10, no external links or credits without permission

- "All 'Powered By' or credit displays and links included in the plugin code must be optional and default to not show"
- "Users must opt-in to displaying any and all credits and links" through "clearly stated and understandable choices", not "buried in the terms of use or documentation".
- "Plugins may not require credit or links be displayed in order to function."
- "Services are permitted to brand their output as they see fit, provided the code is handled in the service and not the plugin."

The plugin team spelled this out further ([Make Plugins, 26 April 2017](https://make.wordpress.org/plugins/2017/04/26/reminder-google-hates-widget-links/)): "You cannot have them show by default, you cannot have them be opt-out, you cannot hide them in display:none code". An HTML comment such as `<!-- Powered by ... -->` is fine. Credit links should be `nofollow`.

### Guideline 5, trialware

- "Plugins may not contain functionality that is restricted or locked, only to be made available by payment or upgrade."
- "Paid functionality in services is permitted, provided all the code inside a plugin is fully available."

So a "remove branding" switch in the WordPress.org build that only works with a licence counts as locked functionality.

### Guideline 6, serviceware

- Allowed: plugins that are "an interface to some external third party service", including paid services.
- Not allowed: "a service that exists for the sole purpose of validating licenses or keys" while the plugin does everything locally, and "moving arbitrary code out of the plugin" to fake a service.

**Guideline 11**: upgrade prompts "must be limited in scope and used sparingly", ideally on the plugin's own settings page.

### How compliant plugins handle a credit link

- *The Events Calendar*: a "Show The Events Calendar link" checkbox under Settings > General > Viewing, `'default' => false`. The label reads: "If you're enjoying The Events Calendar, give us kudos by including a link in the footer of calendar views." (Verified in [the source on GitHub](https://github.com/the-events-calendar/the-events-calendar/blob/master/src/admin-views/settings/tabs/general/general-viewing.php).)
- *W3 Total Cache*: once had a "spread the word" footer-link option on its dashboard, which seems to have been removed ([WPMU DEV guide](https://wpmudev.com/blog/w3-total-cache-settings/)) [unverified current state].
- *Credits Shortcode & Block*: adds a credit only when the site owner inserts the block.
- *Hosted widgets* (Tidio, tawk.to, CookieYes): the branding comes from the service, not from plugin code.

## 3. Options for KimaAI

Freemius today: `has_premium_version` and `has_addons` are both `true`, and `/premium/` is stripped with `@fs_premium_only`. The premium code covers Embedding/RAG, FunctionCall, MCP, Eval, feedback analytics, HumanHandoff, PinnedAnswers, AnswerQuality, SourceTracker and the CF7, Gravity Forms, WooCommerce and ElasticPress integrations. KimaAI on WordPress.org: v1.5.13, fewer than 10 active installs.

### a) Everything free, opt-in credit, paid white-label licence

- **Freemius**: drop the premium version and sell a separate paid add-on, "KimaAI White Label" (an add-on product under the parent).
- **Code**: move `premium/app/*` into `app/` and remove the `can_use_premium_code` gates. Set `poweredBy` to default `false` and ask for it in the wizard. The add-on hides the credit setting, sets the admin white-label through `kimaai_settings_ui_config`, and adds a custom footer text and link.
- **Compliance**: fine, provided the add-on is not on WordPress.org and the free plugin is fully usable without it.
- **Revenue and risks**: on WordPress.org the credit is already off unless the owner switches it on, so the add-on can only sell admin white-labelling and agency use. That is a small market. Giving away RAG, MCP and Eval removes the main reason to pay. No published opt-in rates were found [source missing]. This model's realistic value is distribution, not revenue.

### b) Keep freemium, add white-label to a paid plan

- **Freemius**: keep Free and Pro and add an Agency plan (more sites plus white-label), or put white-label into Pro.
- **Code**: fix `poweredBy` (default off, `nofollow`, a wizard opt-in). Put white-label behind `is_plan__premium_only('agency')`: hide the credit option, custom footer text and link, admin white-label (`kimaai_settings_ui_config`).
- **Compliance**: fine. White-label lives only in premium code.
- **Revenue and risks**: keeps current revenue and adds an agency upsell, which matches WPBot. It does not change the funnel. Low effort.

### c) Hosted KimaAI service (credits) as main revenue, plugin fully free

- **Freemius**: the plugin is free with all features and a "KimaAI Cloud" provider next to OpenAI, Ollama and OpenRouter. Credits are sold as Freemius SaaS plans or subscriptions [unverified fit] or through kimaai.com.
- **Code**: a new provider in `app/Ai/Providers/` that calls a KimaAI API. Moving premium features into free code is fine here. The free tier can carry service-side branding (the API returns the branding to render), which is how Tidio and tawk.to stay compliant. Bring-your-own-key users must stay fully functional with branding opt-in.
- **Compliance**: guideline 6 is met because the service does real work (inference, embeddings). Whether branding that the plugin renders from an API flag counts as "handled in the service" is a judgement call by reviewers [unverified]. Ask plugins@wordpress.org before shipping.
- **Revenue and risks**: the only path to true "free with branding". It needs servers, model costs, billing, GDPR and AI Act data-processing terms, and abuse control. A large build.

### d) Dual distribution

The WordPress.org build stays compliant (opt-in). A "KimaAI Free+" build, downloaded from kimaai.com through Freemius and not WordPress.org, ships all features with a required credit and offers a paid white-label licence.

- **Compliance**: fine, because guideline 10 only covers directory-hosted code.
- **Revenue and risks**: the credit is enforceable only by licence key. Under GPL it can be removed by editing the code. Discovery outside WordPress.org is weak, and two builds double the release and support work.

## 4. Recommendation

Go with **b now and c later**. The "fully free with branding" model only works when the branding comes from a hosted service. Without one, the credit cannot be required on WordPress.org, and moving premium into free gives away the only paid product of a plugin with fewer than 10 installs. Fix the guideline 10 issue first, because it is a takedown risk on the next review.

Implementation track BM (commits):

1. `fix(chatbot): "Powered by KimaAI" off by default, nofollow link (BM-1)`: `default => false` in `app/Admin/config/chatbot.php`, `ChatbotPreview.jsx` fallback `false`, `rel="nofollow noopener noreferrer"` in `Composer.jsx`, plus a migration that turns it off on existing installs that never chose it. Verify with an e2e test that a new install shows no credit.
2. `feat(wizard): opt-in step for the KimaAI credit link (BM-2)`: an unchecked checkbox with plain wording, in the style of The Events Calendar. Verify that the setting is saved only when ticked.
3. `docs(readme): describe the optional credit link and the external services (BM-3)`.
4. `feat(premium): white-label for the Agency plan (BM-4)`: custom footer text and link, the credit option hidden, admin branding through `kimaai_settings_ui_config`, all in `premium/` behind the plan check. Verify that the free build contains no white-label code.
5. `chore(freemius): Agency plan and pricing page (BM-5)`: dashboard set-up and upgrade copy on the settings page only (guideline 11).
6. Separate discovery track for c: a KimaAI Cloud provider prototype plus a written question to the plugin review team about service-side branding.

## Sources

- WordPress.org Detailed Plugin Guidelines: <https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/>
- Make Plugins, "Reminder: Google hates widget links" (2017): <https://make.wordpress.org/plugins/2017/04/26/reminder-google-hates-widget-links/>
- tawk.to pricing: <https://www.tawk.to/pricing/>
- tawk.to Remove Branding add-on: <http://help.tawk.to/article/setting-up-the-remove-branding-add-on>
- tawk.to on WordPress.org: <https://wordpress.org/plugins/tawkto-live-chat/>
- Tidio pricing: <https://www.tidio.com/pricing/>
- Tidio on WordPress.org: <https://wordpress.org/plugins/tidio-live-chat/>
- Crisp pricing: <https://crisp.chat/en/pricing/>
- Chatbase pricing: <https://www.chatbase.co/pricing>
- Botpress pricing: <https://botpress.com/pricing>
- Jotform pricing: <https://www.jotform.com/pricing/>
- CookieYes on WordPress.org: <https://wordpress.org/plugins/cookie-law-info/>
- MailPoet plans: <https://account.mailpoet.com/>
- WPBot on WordPress.org: <https://wordpress.org/plugins/chatbot/>
- The Events Calendar credit setting (source): <https://github.com/the-events-calendar/the-events-calendar/blob/master/src/admin-views/settings/tabs/general/general-viewing.php>
- W3 Total Cache settings guide (WPMU DEV): <https://wpmudev.com/blog/w3-total-cache-settings/>
- Freemius software licensing: <https://freemius.com/help/documentation/wordpress-sdk/integration/software-licensing/>
- Freemius selling add-ons: <https://freemius.com/help/documentation/selling-with-freemius/selling-add-ons-extensions/>
- KimaAI on WordPress.org: <https://wordpress.org/plugins/kimaai/>
