Kelune CRM – Contact Management, Email Marketing, Newsletter & Marketing Automation

Description

Kelune CRM is a self-hosted CRM and marketing platform for WordPress. Manage your contacts, organize them with tags and lists, design emails with a drag-and-drop builder, run campaigns, and automate follow-ups with a visual automation builder — all from your WordPress admin.

Every feature listed below is included and fully functional. Kelune CRM stores your data in your own WordPress database and works offline by default: aside from the avatar WordPress itself already loads for the logged-in user, it only contacts an external service when you explicitly enable and configure one (see the “External services” section below).

Core features

• Contacts — full CRUD, activity timeline, custom meta, and notes.
• Tags & Lists — organize contacts and drive audience selection.
• Custom Fields — single-line and multi-line text, number, email, URL, phone, select, radio, checkbox, date, and datetime.
• Email Templates — drag-and-drop builder with automatic CSS inlining.
• Email Providers — send via SMTP, Amazon SES, Mailgun, or SendGrid, or the default WordPress mailer.
• Email Logs — open/click tracking, stats, and CSV export.
• Campaigns — scheduler, sending queue, and open/click tracking.
• Visual Automation — trigger, delay, and action steps on a flow canvas.
• Incoming Webhooks — create/update contacts and manage tags/lists from external systems.
• Double Opt-in — confirmation flow and per-contact subscription status.
• Settings — business identity, global email and footer, WordPress user sync, signup/comment opt-in, and email-provider configuration.

Source Code

The admin dashboard is built with React and TypeScript (Vite). The only compiled files in this plugin are the five in assets/admin/dist/. All of its PHP, and its remaining CSS, are plain and human-readable.

The full, unminified source of those files, together with the build configuration (assets/admin/vite.config.js), the dependency manifest (assets/admin/package.json) and the lock file that pins every installed version (assets/admin/yarn.lock), is published at:

https://github.com/devitemsllc/kelune-crm

Each release is tagged there, so the sources matching this exact version are at the 1.0.0 tag.

To rebuild the bundle from that source (requires Node.js 20 or newer and Yarn 1.x — run corepack enable or npm install -g yarn):

1. cd assets/admin
2. yarn install
3. yarn build

That one command writes all five files. The output filenames are fixed — no content hash, no code splitting — so the build is reproducible and the plugin enqueues each file by its literal name through wp_enqueue_script() and wp_enqueue_style(), cache-busted with the plugin version as ?ver=. Because nothing is code-split, no part of the bundle is fetched from a remote server at runtime.

The build writes kelune-crm-admin.js and kelune-crm-admin.css for the application itself, plus three scripts holding the third-party libraries: kelune-crm-admin-antd.js, kelune-crm-admin-charts.js and kelune-crm-admin-editors.js. React is not bundled — react, react-dom and react-jsx-runtime are declared as dependencies of each script, so the copies WordPress ships are the ones used.

The build does not modify any third-party code, and no code is obfuscated.

The rich-text editor uses WordPress core’s own bundled TinyMCE from wp-includes/js/tinymce/, enqueued through core’s wp-tinymce script handle; no TinyMCE library code is included in this plugin. No other files in this plugin are compiled, minified, or obfuscated.

Bundled Libraries

The files in assets/admin/dist/ are produced by the build described above from the third-party packages listed below. Each is compiled into the shipped scripts — none is fetched at runtime.

• React and ReactDOM (react, react-dom) — MIT; not bundled, the copies WordPress ships are used, which is why React is pinned to the 18.x line core provides.
• Ant Design (antd) — MIT; only the locale pack matching your site language is loaded.
• Ant Design Icons (@ant-design/icons) and Ant Design Charts with AntV G2 (@ant-design/charts) — MIT.
• React Router (react-router-dom) — MIT.
• Redux Toolkit and React Redux (@reduxjs/toolkit, react-redux) — MIT.
• React Flow (reactflow), used by the automation canvas — MIT.
• dnd kit (@dnd-kit/core, @dnd-kit/modifiers, @dnd-kit/sortable, @dnd-kit/utilities), used by the email builder — MIT.
• CodeMirror (@uiw/react-codemirror, @codemirror/view, @codemirror/lang-html), used by the HTML editor — MIT.
• juice (juice), which inlines CSS into email HTML — MIT.
• Axios (axios) — MIT, Day.js (dayjs) — MIT, and react-responsive (react-responsive) — MIT.

They are distributed across the four scripts as follows:

kelune-crm-admin-antd.js — Ant Design, Ant Design Icons, Day.js.

kelune-crm-admin-charts.js — Ant Design Charts, AntV G2, html2canvas, Lodash.

kelune-crm-admin-editors.js — CodeMirror, juice.

kelune-crm-admin.js (the application bundle) — Redux Toolkit, React Redux, React Router, React Flow, dnd kit, Axios, react-responsive.

Every package above is MIT licensed; the dependencies they pull in are MIT, ISC, BSD or 0BSD. All of those are compatible with this plugin’s “GPLv2 or later” license. assets/admin/package.json declares the packages depended on directly, and assets/admin/yarn.lock pins the exact version installed for every package, including indirect ones such as AntV G2, html2canvas and Lodash; both files are published in the repository linked above.

No third-party PHP libraries are included at all: the plugin has no PHP dependencies, and its own classes load through the hand-written autoload.php at the plugin root.

External services

Kelune CRM works fully offline by default and stores all data in your own WordPress database. It connects to an external service only when you explicitly enable and configure that service, with one exception noted under Gravatar below. No data is ever sent to the plugin author.

SendGrid
Used to deliver email (campaigns, automations, and transactional mail) when you select SendGrid as your email provider and enter a SendGrid API key.
– Data sent: message content, subject, and recipient/sender email addresses. When you save the provider settings, only your API key is sent, to validate it against the SendGrid profile endpoint.
– When sent: each time the plugin sends an email through this provider, and when you save the provider settings.
– Service URL: https://api.sendgrid.com
– Terms of Service: https://www.twilio.com/en-us/legal/tos
– Privacy Policy: https://www.twilio.com/en-us/legal/privacy

Mailgun
Used to deliver email (campaigns, automations, and transactional mail) when you select Mailgun as your email provider and enter a Mailgun API key and sending domain.
– Data sent: message content, subject, and recipient/sender email addresses. When you save the provider settings, only your API key and sending domain are sent, to confirm the domain exists on your account.
– When sent: each time the plugin sends an email through this provider, and when you save the provider settings.
– Service URL: https://api.mailgun.net (or https://api.eu.mailgun.net if you select the EU region)
– Terms of Service: https://www.mailgun.com/legal/terms/
– Privacy Policy: https://www.mailgun.com/legal/privacy-policy/

Amazon SES
Used to deliver email (campaigns, automations, and transactional mail) when you select Amazon SES as your email provider and enter AWS credentials. No request is made to Amazon until you have selected SES and saved your credentials.
– Data sent: the raw message — recipient/sender addresses, subject, and content. Further calls send only your AWS credentials and no contact data: they read your account’s sending quota and list the sender addresses your AWS account has verified.
– When sent: each time the plugin sends an email through this provider; when you save the provider settings; and when you open the provider’s details screen.
– Service URL: https://email.{your-region}.amazonaws.com/ — for example https://email.us-east-1.amazonaws.com/
– Terms of Service: https://aws.amazon.com/service-terms/
– Privacy Policy: https://aws.amazon.com/privacy/

Gravatar
Used to display contact avatars when you enable the “Use Gravatar service” setting. Separately, and regardless of that setting, the dashboard greeting shows the logged-in WordPress user’s own avatar through WordPress’s built-in avatar system, which uses Gravatar by default; this is the same avatar WordPress already shows in the admin bar, and it follows the site-wide “Show Avatars” option under Settings > Discussion.
– Data sent: a SHA-256 hash of the email address, sent by the browser when the avatar image is loaded. With the setting disabled, no avatar URL is generated for contacts and nothing is sent.
– When sent: when a contact avatar is rendered with the setting enabled, and when the dashboard greeting renders the logged-in user’s avatar.
– Service URL: https://www.gravatar.com
– Terms of Service: https://wordpress.com/tos/
– Privacy Policy: https://automattic.com/privacy/

SMTP (your own mail server)
Used to deliver email when you select SMTP as your email provider. This is not a fixed third-party service: the plugin connects only to the mail server host you enter yourself.
– Data sent: message content, subject, and recipient/sender email addresses, plus the SMTP credentials you configure.
– When sent: each time the plugin sends an email through this provider.
– Service URL: the SMTP host you configure
– Terms / Privacy: governed by your own mail server provider