Commento solves comments.
VeloCMS solves the rest.
Commento genuinely wins on embed weight (~12KB), open-source transparency, GDPR-by-default, and threaded discussions. The gap: it's a comment widget on top of your existing stack. VeloCMS wraps native comments in a full CMS with members, newsletter, AI editor, and flat pricing.
Commento vs VeloCMS — platform snapshot
| Dimension | Commento | VeloCMS |
|---|---|---|
| Primary focus | Privacy-first commenting platform built as a lightweight Disqus alternative. Open-source (MIT-licensed Go backend, available on GitHub). The embed is approximately 12KB — roughly 20x lighter than Disqus. No behavioral tracking, no cross-site cookies, no ad revenue model. Hosted version at commento.io is $10/mo. Self-hosted version is free but requires operating a Go binary, PostgreSQL database, and your own domain with TLS. Threaded comment discussions with nested replies. Commenter authentication via email, Google OAuth, or Twitter. Comment moderation dashboard. Upvotes on comments. Spam filtering via Akismet integration. No native CMS, no newsletter, no member paywall, no e-commerce — Commento is a comment widget you embed on a blog you're already running elsewhere. | CMS-first content platform with native commenting built into the same stack as posts, members, and newsletter. TipTap block-based blog editor with per-post SEO, JSON-LD schema, and AI drafting via Gemini. Native member system with free and paid tiers, magic-link reader authentication, and member-only post gating. BYOK Resend newsletter. BYOK Stripe for member subscriptions at 0% platform fee. 30+ themes. Comments integrated directly with the member system — comment authors are your members with accounts tied to your platform. No separate comment SaaS bill. No devops overhead. Commenting, blogging, memberships, and newsletter in one admin. |
| Pricing | Self-hosted: free (you run the Go binary + PostgreSQL + TLS + domain). Hosted: $10/mo flat regardless of comment volume — no per-commenter pricing. Commento hosted is a comment-only SaaS. You still need a separate CMS ($10–30/mo), separate email/newsletter service ($0–30/mo depending on volume), and separate member paywall if you want reader subscriptions ($25–49/mo). The $10/mo hosted Commento is genuinely fair for what it does — the issue is that it's one piece of a bolted-together stack that costs $50–100/mo in total. | Flat monthly regardless of comment volume. Free tier (single blog, VeloCMS subdomain, basic commenting). Pro $9/mo annual (full block editor, BYOK newsletter, AI drafting, 30+ themes, custom domain, native comments included). Business $29/mo annual (all Pro + member tiers, BYOK Stripe digital products at 0% platform fee). No ads. No comment-count ceiling. No separate comment SaaS. Comments in your PocketBase database — self-hostable if you want full infrastructure ownership. |
| Comments owned by | It depends on which Commento you use. Self-hosted Commento: comments live in your PostgreSQL database on your server — you own them fully. Hosted Commento ($10/mo): comments are stored on Commento's servers. You can export your data but the live system depends on Commento's infrastructure. Either way, Commento is better than Disqus on data ownership — self-hosted is the gold standard, and even hosted Commento has no ad-tracking revenue model around your comment data. | You. Comments stored in your PocketBase instance (SQLite, self-hostable). Comment authors are your members — accounts tied to your platform, not an external commenting network. BYOK architecture: if you self-host PocketBase, the database is literally on your server. No third-party dependency for the comment layer. Migrating away requires no data export negotiation — you already own the database. |
| CMS + blog | Not included. Commento is a comment widget — you embed it in a blog you're already running on WordPress, Ghost, a static site, or any other CMS. You need a separate CMS subscription. The Commento embed integrates via a JavaScript snippet and auto-discovers posts from your page URLs. There is no blog editor, post management, theme system, or content admin inside Commento. | First-class. VeloCMS includes a TipTap block-based editor, post management admin, per-post SEO with JSON-LD, AI drafting via Gemini, 30+ first-party themes, and ISR rendering for sub-1s LCP on blog pages. You don't need a separate CMS — this is the CMS. Comments are one feature inside it, not a widget bolted on. |
| Member-only comments | Not natively supported. Commento commenter authentication is via email, Google OAuth, or Twitter — these are Commento accounts, not member accounts tied to your blog. You cannot gate comments to paid members via Commento's native tooling. If you run a member paywall separately (Memberful, Ghost memberships, etc.), there is no native connection between that member tier and Commento comment permissions. | Native. You can configure any post to allow comments from: everyone, free members only, or paid members only. A paid member commenting is identifiable as a subscriber in your member dashboard. Commenter identity is their member account — same account they use to access gated content, receive newsletters, and manage their subscription. |
| Moderation | Moderation dashboard inside Commento admin. Pre-moderation mode to hold comments for approval. Akismet integration for spam filtering. Comment flagging by readers. Comment deletion and editing. Shadow-ban equivalent (approve/pending/spam states). Moderation is entirely within Commento's interface — separate from wherever you manage your blog content. Two separate admin logins if you use hosted Commento + a CMS. | Moderation in the same VeloCMS admin where you manage posts, members, and newsletter. No context-switching. Spam filtering via configurable keyword rules. Member-based auto-approval: established members with prior approved comments can auto-approve; new commenters queue for manual review. All moderation data in your database. |
| Page weight | Approximately 12KB compressed JavaScript embed — genuinely lightweight. This is Commento's strongest differentiator against Disqus (~250KB) and most other comment platforms. The 12KB embed renders the comment thread and form with minimal browser overhead. No third-party tracking scripts, no ad network code, no cross-site behavioral analytics embedded in the widget. For LCP-focused publishers, this is a meaningful advantage over heavier comment embeds. | Comments rendered as Server Components in the initial HTML — the comment list has no separate JS bundle. The comment submission form hydrates client-side only when the reader scrolls to it. Total comment-layer JS overhead is comparable to or smaller than Commento's 12KB embed since most of the comment rendering happens server-side rather than in a client-loaded widget. No third-party script load from a separate domain. |
| Owned data | Self-hosted Commento: full data ownership — PostgreSQL on your server, you control backups, migration, and retention. Hosted Commento ($10/mo): data on Commento's servers, exportable but dependent on their infrastructure. Commento has no ad-revenue motive to retain your data — unlike Disqus (Zeta Global), Commento's business model is the $10/mo subscription, not data monetization. The privacy posture is genuinely better than Disqus regardless of which Commento deployment you choose. | Full data ownership. PocketBase SQLite file is self-hostable — you can run VeloCMS on your own server if you want the database on your infrastructure. On Railway-hosted VeloCMS, the PocketBase volume is your data. No third-party data company involved. No ad targeting. Comment data, member data, and post data are in the same owned database. |
Where Commento leaves gaps
Commento is a well-designed privacy-first comment system. These are the structural gaps that appear when you need more than a comment widget bolted onto a separate CMS, email, and membership stack.
Commento solves comments. Your blog still needs a CMS, email, and membership on top.
Commento hosted is $10/mo for a comment widget. Your WordPress or Ghost blog is another $10–30/mo. Your newsletter service is another $0–30/mo depending on list size. Your member paywall (Memberful, Ghost native, etc.) is another $25–49/mo. The individual tools are all reasonable priced — the problem is you're paying for four separate services, logging into four separate admin panels, and getting zero native integration between them. A member who comments has two unrelated accounts: one on your paywall platform, one as a Commento commenter. There's no way to gate comments to paid members via Commento without custom code.
Self-hosting Commento is free, but free here means devops.
Commento's self-hosted path requires deploying a Go binary, provisioning a PostgreSQL database, configuring TLS, managing a domain, keeping the binary updated, and handling database backups. For developers who already manage servers, this is a half-hour setup. For bloggers who write about food, travel, finance, or their niche — managing a Go service in production is a genuine burden. The “free” in self-hosted Commento refers to the software license, not to the operational cost of running it. There's a real skill and time requirement that the $10/mo hosted plan removes, but at $10/mo you're back to paying for a comment-only SaaS on top of your other tools.
Commento's 12KB win is real, but the full-stack comparison is different.
Commento's ~12KB embed is a genuine win against Disqus (~250KB) or other heavy comment SaaS. For a blog post page where the comment widget is one of many elements, 12KB is minimal. But when you compare full-stack LCP — CMS-rendered blog post pages with server-side comments vs. a separately-hosted CMS + Commento embed — the picture changes. VeloCMS Server Components render comment threads in the initial HTML on Railway's edge. No separate embed domain to load, no DNS lookup for commento.io, no client-side JS for the comment list. The page weight and LCP comparison is closer than “12KB vs everything else” suggests.
Three bloggers evaluating Commento
Privacy-focused bloggers already on Commento, Disqus escapees comparing lightweight alternatives, and self-hosting indie bloggers who want everything in one deployment.
The privacy-focused blogger using Commento on an existing site
You switched from Disqus to Commento because you cared about your readers' privacy. Commento's ~12KB embed, no behavioral tracking, and GDPR-by-default design are exactly what you wanted, and it's working. The question is whether you want to keep paying $10/mo for comments alongside your CMS subscription, or whether you want comments folded into the same platform as your blog. If you're happy with your current CMS and not looking to consolidate, Commento is doing its job. The comparison becomes relevant when you're also evaluating your CMS, considering a member paywall, or looking for AI writing assist — at which point the full-stack math shifts toward VeloCMS.
The Disqus escapee evaluating lightweight comment alternatives
You've decided Disqus is done — the ads, the data ownership, the 250KB embed. You're comparing Commento, Cusdis, and native options. Commento is the most full-featured of the lightweight privacy alternatives: open-source, threaded discussions, upvotes, Akismet spam filtering, and genuinely small embed footprint. If your evaluation is “which comment widget should I bolt onto my Ghost/WordPress/Astro blog,” Commento is a strong contender. If your evaluation is wider — “do I also want to rethink my CMS, start a newsletter, or add a paywall” — VeloCMS handles comments as part of that broader platform decision. See VeloCMS vs Disqus for the full Disqus comparison.
The self-hosting indie blogger who wants everything on one server
You self-host your blog. You value software ownership, dislike SaaS subscriptions, and can operate a server. Commento self-hosted gives you a free privacy-first comment system on your own infrastructure. VeloCMS is also fully self-hostable — PocketBase plus the Next.js service can run on a $5 VPS if you want. The difference is scope: self-hosted Commento gives you a comment widget. Self-hosted VeloCMS gives you the comment widget plus the CMS editor, themes, member system, newsletter, AI integration, and admin dashboard. One self-hosted deployment vs two (CMS + comment system). See how VeloCMS is built for developer bloggers.
Feature parity grid — what each covers
Honest grid. Commento leads on embed weight, open-source, and Akismet spam filtering. VeloCMS leads on full-stack CMS, member integration, newsletter, AI editor, and flat single-tool pricing.
| Feature | Commento | VeloCMS |
|---|---|---|
| ~12KB lightweight embed (comment widget only) | ✓ | — |
| Open-source (MIT license, auditable codebase) | ✓ | — |
| GDPR-by-default (no behavioral tracking, no third-party cookies) | ✓ | ✓ |
| Threaded comments with nested replies | ✓ | ✓ |
| Self-hostable comment data | ✓ | ✓ |
| Upvote reactions on comments | ✓ | ~ |
| Zero ad revenue model (no ads on readers, ever) | ✓ | ✓ |
| Native CMS blog editor (TipTap, SEO, AI) | — | ✓ |
| Member paywall integration with comments | — | ✓ |
| Member-only comment gating | — | ✓ |
| Newsletter blast (BYOK Resend) | — | ✓ |
| AI writing assist in editor | — | ✓ |
| 30+ themes with per-tenant customization | — | ✓ |
| Single admin for posts + comments + members | — | ✓ |
| No separate CMS required | — | ✓ |
✓ native ~ partial/limited — not available
Pricing breakdown — the full stack comparison
Commento hosted is $10/mo for comments only — you still need a CMS, email service, and member paywall. Self-hosted is free but requires devops. VeloCMS includes comments in the flat CMS plan — no separate comment SaaS.
Commento — comment widget on top of your stack
- Commento Self-HostedSoftware license free. Go binary + PostgreSQL + TLS + domain = devops overhead.Free
- Commento HostedComment widget only. No CMS, no members, no newsletter included.$10/mo
- Your CMS (separate)WordPress, Ghost, Squarespace — not included in any Commento tier.$10–30/mo
- Newsletter service (separate)Mailchimp, Kit, Resend — depends on list size. Not included.$0–30/mo
- Member paywall (separate)Memberful, Memberstack — no native Commento integration.$25–49/mo
Commento Hosted ($10/mo) + a mid-tier CMS ($20/mo) + newsletter ($15/mo) = $45/mo for a blog with separate admin panels for each tool and no integration between commenter identity and member tier.
VeloCMS — CMS + comments + members in one
- VeloCMS FreeSingle blog, VeloCMS subdomain, basic editor, native comments included.$0
- VeloCMS ProAnnual — full editor, BYOK newsletter, AI assist, 30+ themes, custom domain, native comments.$9/mo
- VeloCMS BusinessAnnual — all Pro + member tiers with member-gated comments, BYOK Stripe, 0% platform fee.$29/mo
- VeloCMS AgencyAnnual — unlimited tenant blogs on custom domains, all including native comments.$69/mo
- Member subscriptions (BYOK Stripe)Your own Stripe account — standard 2.9%+$0.30, 0% VeloCMS cut.0% platform fee
VeloCMS Pro at $9/mo covers the CMS blog, native zero-ad comments, and BYOK newsletter. No separate comment SaaS. VeloCMS Business at $29/mo adds member-gated commenting and BYOK Stripe — cheaper than the Commento + CMS + paywall stack.
Worked example — Commento Hosted + CMS + newsletter vs VeloCMS all-in
Commento Hosted + typical blog stack
- Ghost Pro Starter (blog): $9/mo
- Commento Hosted (comments): $10/mo
- Kit (newsletter, 1k subscribers): $15/mo
- Memberful Starter (paid memberships): $25/mo
Total: ~$59/mo
Four separate admin panels. Commenter identity in Commento, member identity in Memberful — no native connection between them. No member-gated comments without custom code.
VeloCMS Business (all-in)
- VeloCMS Business (CMS + comments + members + newsletter): $29/mo
- Resend (BYOK newsletter, included in plan): from $0/mo
Total: ~$29/mo
One admin for posts, comments, members, and newsletter. Member-gated comments native. No separate comment SaaS. $30/mo cheaper than the bolted-together stack.
Commento's $10/mo is fair for a privacy-first comment widget. The issue is that it's always additive — on top of your CMS, email, and membership tools. VeloCMS comments are included in the platform price, not a separate line item.
Migration from Commento — 5-step path
Migrating off Commento means exporting comment history, mapping threads to your post slugs, setting up VeloCMS native comments, and removing the Commento embed script. The 14-day migration support covers each step.
- 1
Export your Commento comment history
From Commento's admin panel (or from your PostgreSQL database directly if self-hosted), export your comment data. Commento stores comment threads with post URL identifiers, comment text, commenter names and email addresses, timestamps, and parent-child thread relationships. If you're on the self-hosted version, you can also export directly from the PostgreSQL database with a standard SQL dump — the schema is well-documented in Commento's open-source repository. Keep the export file — it's your complete comment archive before migration.
- 2
Import comment history into VeloCMS native comments
Use VeloCMS's comment importer in the admin tools section. The importer maps Commento comment threads to VeloCMS post slugs by matching on post URL paths. Threaded relationships (parent comment ID to child comment IDs) are preserved. Commenter names, email addresses, and timestamps are imported. Readers whose email addresses match existing VeloCMS member accounts have their comments attributed to their member profile — readers without VeloCMS member accounts are imported as guest comments attributed by name. Upvote counts are imported as display metadata. Review the import summary and spot-check a few high-comment posts before proceeding.
- 3
Configure moderation and spam filtering
Set up VeloCMS comment moderation to match or improve on your Commento moderation setup. Decide whether new commenters require manual approval or whether registered members auto-approve. If you were using Commento's Akismet integration, configure VeloCMS's keyword-based spam rules as a replacement. For member-gated comments — if any posts should restrict commenting to paid members — configure those settings per post or as a global default. Set up email notifications for new comments requiring review.
- 4
Remove the Commento embed script
If you were embedding Commento via the standard JavaScript snippet, remove it from your CMS template or theme. In VeloCMS, native comments render automatically on blog posts — no embed code required. Once the Commento script is removed, the third-party JS load from commento.io (or your self-hosted domain) is eliminated. Run a Lighthouse audit to verify LCP and TBT haven't regressed — you should see the comment-layer load time improve since there's no longer a separate script fetch.
- 5
Notify regular commenters and rebuild community context
Existing Commento commenters used a Commento account (email, Google OAuth, or Twitter) to authenticate. After migration, their comment history will appear in VeloCMS, but they'll need to create a VeloCMS member account to comment going forward. Consider sending a brief email or publishing a blog post announcing the comment system change and explaining how existing readers can create a member account to continue participating. Readers who were using member-based paywalled content can use the same member account for commenting — one account instead of two.
Honest trade-offs
Commento's ~12KB lightweight embed, MIT open-source codebase, GDPR-by-default privacy design, threaded discussions, and zero-tracking architecture are genuine advantages — especially compared to Disqus's ~250KB embed and ad-revenue business model. For a blogger who already has a CMS they love, a newsletter service that works, and just needs privacy-respecting comments added on top, Commento self-hosted is an excellent choice: free software, your own server, full data ownership, lightweight embed. The open-source nature also means you can audit every line of code and run Commento indefinitely without depending on a vendor's pricing decisions.
The calculation shifts when you zoom out from “just comments” to the full publishing stack. If you also want to consolidate your CMS, newsletter, and member paywall — or if you're starting fresh and want one admin that handles everything — Commento's comment-widget scope becomes a liability rather than a feature. A bolted-together stack of WordPress + Commento + Kit + Memberful runs $50–100/mo with four logins, four separate databases, and no native integration between commenter identity and member tier. VeloCMS wraps all of that in a single platform where a person who comments is identifiably a member, a newsletter subscriber, and potentially a paying customer — one account, one database, one admin. If your only need is privacy-respecting comments on a site you're already running elsewhere, Commento self-hosted is excellent and you probably don't need VeloCMS for just that. If you want the full stack — CMS plus comments plus members — VeloCMS wins on integration and price.
Which archetype fits your situation?
The Commento vs VeloCMS decision comes down to whether you want a comment widget to add to an existing stack, or a full platform where comments are one first-class feature among many.
Privacy-Focused Blogger
Already on Commento for its ~12KB embed and GDPR design
You switched from Disqus to Commento specifically for privacy and page weight. The embed is tiny, the tracking is zero, and your readers' data stays clean. If you're happy with your current CMS and not considering a platform change, Commento is doing its job. The comparison becomes relevant if you're also reconsidering your CMS, starting a newsletter, or adding paid memberships — at that point, the full-stack cost and fragmentation is worth examining. See how VeloCMS compares for bloggers.
Stay on Commento if comments are your only need. Evaluate VeloCMS if you want to consolidate the full stack.
Disqus Escapee
Leaving Disqus and comparing lightweight privacy alternatives
You've decided to leave Disqus — probably the free-tier ads, the Zeta Global data provenance, or the 250KB embed. Commento is the most full-featured privacy alternative in the comment-widget category: open-source, threaded discussions, Akismet spam filtering, upvotes. If your decision is strictly “which comment widget to replace Disqus with,” Commento is a serious contender. If you're also questioning your CMS, newsletter, or membership setup at the same time, VeloCMS handles all of it in one platform. See VeloCMS vs Disqus for the full Disqus comparison.
Best Disqus replacement if you want a comment-widget swap. VeloCMS if you want the full platform.
Self-Hosting Indie Blogger
Wants everything on own server — CMS, comments, members
You self-host because you believe in software ownership and can manage infrastructure. Commento self-hosted gives you free comment software on your own server. VeloCMS is also fully self-hostable: PocketBase (SQLite, single binary) + the Next.js service on a $5–10/mo VPS gives you the CMS editor, themes, member system, newsletter, AI integration, and comments in one deployment. One binary pair vs one Go binary for comments alone. If you're self-hosting anyway, the question is whether you want a comment system or a full blog platform on that server. See how VeloCMS is built for developers.
Self-hosted Commento if you just need comments. Self-hosted VeloCMS if you want the full CMS stack.
Frequently asked questions
Frequently asked questions
Can I migrate my Commento comments to VeloCMS?
Yes. Commento provides a data export from the admin panel (or from your PostgreSQL database directly if self-hosted). The export includes comment threads, comment text, commenter names and email addresses, timestamps, and parent-child thread relationships. VeloCMS import tooling reads the Commento export format and maps comments to the corresponding blog post slugs. The 14-day migration support window covers the comment import, post slug mapping, and moderation queue rebuild. Upvote counts are imported as display-only metadata — voting state is not actionable post-migration since it was Commento-account-scoped.
Does VeloCMS support threaded comments like Commento?
Yes. VeloCMS native comments support threaded discussions with nested replies — a reply to a comment shows as a child thread under the parent comment, to configurable depth. This matches Commento's threading model. Both systems let readers reply directly to specific comments with indented threads. The difference is that Commento's commenter identity is a Commento account (or OAuth via Google/Twitter), while VeloCMS commenter identity is their member account on your platform — the same account they use to access gated posts and manage their subscription.
Is Commento really free to self-host?
The Commento software is free (MIT license). The infrastructure to run it is not — you need a Go binary deployment, a PostgreSQL database, a domain name, and TLS certificate setup. For developers comfortable with server management, this is relatively straightforward. For bloggers focused on content rather than infrastructure, the operational overhead is real. There's also ongoing maintenance: binary updates, database backups, and uptime monitoring. The $10/mo hosted Commento plan removes this overhead. VeloCMS is also self-hostable (PocketBase + Next.js), with the hosted Railway option eliminating infrastructure management.
How does VeloCMS handle spam filtering compared to Commento?
Commento integrates with Akismet for spam filtering — the same service WordPress uses. Akismet is well-established and has reasonable accuracy for spam detection, though it requires an Akismet API key (free for personal use, paid for commercial blogs). VeloCMS's spam filtering uses keyword rules plus member-trust-based auto-approval: established members with prior approved comments auto-approve, new commenters queue for review. Commento's Akismet integration is the more mature spam detection option today. VeloCMS's member-trust approach works well for communities where commenters register as members.
Can I restrict comments to paid members only on VeloCMS?
Yes, and this is one of the clearest functional gaps between Commento and VeloCMS. Commento's commenter authentication uses Commento accounts or OAuth — there's no connection to a member paywall on your blog. You can't restrict Commento comments to paid subscribers without custom code. VeloCMS comments are natively tied to the member system: you can set any post to allow comments from everyone, free members only, or paid members only. A commenter's identity is their VeloCMS member account — the same account they use to access paywalled content.
What's the actual page weight comparison between Commento and VeloCMS comments?
Commento's embed is approximately 12KB compressed JavaScript loaded from commento.io (or your self-hosted domain). This is the widget code that renders the comment list and form client-side. VeloCMS comment lists are rendered as Server Components in the initial page HTML — the comment list HTML is in the initial response, not loaded client-side. The comment submission form hydrates client-side only on scroll. On a direct comparison: Commento adds ~12KB JS per page load from a third-party domain. VeloCMS adds near-zero incremental JS for the comment list (it's in the initial SSR HTML). For LCP, no third-party comment domain DNS lookup is a meaningful win.
Is VeloCMS open-source like Commento?
VeloCMS is source-available but not open-source in Commento's MIT sense. Commento's MIT license means you can fork, modify, and run it for any purpose including commercial. VeloCMS has a self-hosted option with access to the source, but the licensing is different. If open-source as a philosophy (audit every line, fork freely, community contributions) matters to you, Commento's MIT license is a genuine advantage. VeloCMS's trade-off is a richer platform scope (CMS + members + newsletter + AI + e-commerce) at the cost of the broader open-source commitment.
What does VeloCMS offer that Commento doesn't?
VeloCMS leads on: native CMS blog editor with TipTap, per-post SEO tooling, AI writing assist via Gemini, 30+ first-party themes, native member system with free and paid tiers, member-gated comments (paid-member-only comment threads), BYOK newsletter, BYOK Stripe digital products at 0% platform fee, and a single admin for posts + comments + members. Commento leads on: ~12KB embed weight (no equivalent 'embed in existing site' mode in VeloCMS), MIT open-source license, Akismet spam filtering, upvote reactions, and the ability to add comments to any website without changing your CMS.
Founder note
“Commento got the philosophy right. Privacy-first, open-source, lightweight — everything Disqus should have been. The 12KB embed is a real engineering achievement. But comments live downstream of content, and content lives downstream of your whole publishing stack. Integrating comments natively means a commenter becomes a member, a member becomes a newsletter subscriber, and your community compounds in one place — not across four separate SaaS dashboards. That's the gap Commento can't close by design.”
VeloCMS native comments are first-class — same database as your posts and members, integrated with the member layer so commenting and membership are the same identity, visible to every reader regardless of privacy tooling, and included in the flat plan price.
Try VeloCMS free for 14 days
CMS blog, native privacy-respecting comments, BYOK newsletter, and member paywall — all in one admin. No separate comment SaaS bill. Comments in your database. If you're migrating from Commento, the trial includes 14 days of hands-on migration support.