Liquid Web Killed StellarWP. The Plugins Survived. The Trust Didn’t.

Liquid Web Killed StellarWP. The Plugins Survived. The Trust Didn’t. ![rw-book-cover](https://digisavvy.com/wp-content/uploads/2026/10/lwks.webp) 🔗 **Source:** [Liquid Web Killed StellarWP. The Plugins Survived. The Trust Didn’t.](https://digisavvy.com/liquid-web-killed-stellarwp/) > [!note]+ Document Notes > tags: [wordpress-plugins, stellarwp, liquid-web, plugin-pricing, vendor-trust] > author: Alex Vasquez > source: DigiSavvy > reference: https://digisavvy.com/liquid-web-killed-stellarwp/ > date created: 2026-10-19 16:20 > > > [!info] Generated analysis — not the author's words. Sections below are machine-written > > from the captured source. Only text inside `> [!quote]` blocks is verbatim from the author. > > Do not quote or attribute any other line to the named author. > > # 🏷️ Title: Liquid Web Killed StellarWP. The Plugins Survived. The Trust Didn’t. >  ## 🧭 Table of contents - [📝 Summary](#-summary) - [📖 Main content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning styles assessment](#-learning-styles-assessment) - [📊 Accessibility assessment](#-accessibility-assessment) - [🌍 DEIB assessment](#-deib-assessment) - [✅ Logical validity](#-logical-validity) - [🛡️ DARVO analysis](#️-darvo-analysis) - [🎯 Conclusion](#-conclusion) - [🔄 Refactor appendix](#-refactor-appendix--liquid-web-killed-stellarwp-the-plugins-survived-the-trust-didnt) ## 📝 Summary This is a descriptive reading of an opinion post about vendor pricing and communication, not legal, financial or purchasing advice. DigiSavvy (digisavvy.com), a WordPress services business, published it under the page author Alex Vasquez. The captured text carries no publication date. Its internal references (an October 14 town hall, an October 15 post on X, "this month" releases) place it after October 15, 2026. Paragraph numbers (¶n) in this file come from splitting the source text on blank lines, so headings and the table rows each count as a paragraph. The source has 46 paragraphs. The post is commentary and advocacy written by a party with a commercial interest. The author discloses in ¶3 that DigiSavvy builds on LearnDash and has client sites running these plugins, and ¶30 and ¶42 add that DigiSavvy sells LearnDash consulting and website maintenance, with public pricing. Every claim below about Liquid Web, Nexcess, Awesome Motive, Give, Kadence, LearnDash or any other company is the author's account, or the author's quotation of a vendor page, unless stated otherwise. This analysis checked none of those pages. - **What happened.** Per the author, Liquid Web retired the StellarWP brand in May 2026, and on October 14 told customers that renewals on or after November 16 move into one bundle of Kadence, LearnDash, The Events Calendar and Give at $350 a year for one site (¶2, ¶10, ¶24). - **The claim.** The author argues that the bundle, the pricing changes and the way customers learned of them cost trust, even though the plugins still ship releases (¶2, ¶28-¶30). The author quotes a vendor FAQ saying a customer can't buy a single product (¶15) and lists list prices from vendor pages and archived copies (¶19-¶24). - **What the author calls out as limits.** The author says the price table isn't like-for-like, that no actual renewal invoice has been seen, and that a clean LearnDash "before" price couldn't be verified (¶25). The author also says the bundle can be cheaper for someone using all four products (¶26). - **Why it matters.** The author says businesses build on these plugins and now have to guess the vendor's plan, and asks readers to check renewal dates before November 16 (¶30, ¶37-¶43). - **Key stakeholders.** Liquid Web and its Nexcess brand, owner One Equity Partners and the holding company CloudOne Digital, Awesome Motive (a competing vendor group), Kadence lifetime owners, agencies running many sites, and DigiSavvy and its clients. - **Risks and tradeoffs.** The post is one customer-side vendor's view. It names no Liquid Web response to its criticism. It contains figures drawn from archives and vendor pages, with the capture dates in the link URLs (see References). The author says no renewal invoice has been seen (¶25). - **Bottom line.** The post documents a sequence of public vendor statements with links and flags its own caveats. Its strongest sourced point is the gap between the May wording on plans and the October FAQ. Its weakest points are the unquantified "trust" claim in the title and a generalization in ¶27 that the author's own table partly contradicts (see Logical validity). ## 📖 Main content **The framing and the disclosure (¶1-¶4).** The post opens with a mock obituary for StellarWP (¶1) and states in ¶2 that this isn't a rant about dead code. It is about trust, pricing and how customers found out. ¶3 discloses the author's business stake. ¶4 admits the author read the original acquisition press releases fast and with too much faith. **The timeline (¶5-¶11).** The author lists four dated events, each with a link in the captured markup. In May 2021 Liquid Web bought GiveWP and launched StellarWP, and the announcement (per the author) said GiveWP would continue as an independent unit. In April 2023 One Equity Partners completed its acquisition of Liquid Web and formed CloudOne Digital. On May 12, 2026 the product sites for GiveWP, LearnDash, Kadence and The Events Calendar started redirecting to Liquid Web pages, and an announcement said SolidWP, Iconic, Restrict Content Pro and MemberDash are no longer sold as standalone products (the link goes to an archive capture dated 2026-05-14). The author cites Search Engine Journal for the backlash, including Kadence lifetime owners who couldn't find their downloads. On October 14 a town hall announced the bundle, which the recap calls the Nexcess plugin stack, starting with renewals on or after November 16. The author's own judgment in ¶11 is that this is a long way from an independent unit. **The wording comparison (¶12-¶17).** The author quotes the May 12 text (the page still carried it in an archive dated October 6): current plan, pricing and tools remain the same unless a customer chooses to upgrade, and the change is not a forced migration (¶13). The author then quotes the FAQ on the package page: no, a customer can't buy just one product, every plan includes all four starting at $350 a year for one site, and doing nothing moves the customer at the next renewal (¶15). For customers with several subscriptions, the recap says the first renewal to come up becomes the stack and the others are canceled when it is applied (¶16). The author concedes in ¶17 that the May promise was about plan and price while a subscription is active, so the two statements are technically consistent, and leaves the judgment to the reader. **The prices (¶18-¶27).** The author gives three rows from vendor pages and archives, each with a link. Give's entry paid tier went from $149 a year (Basic, March 2026) to $199 (Essentials, May 12) and then $399 (Pro) as the lowest tier shown now. Kadence's Pro tier went from $219 a year (May 12) to $299 a year (October 1). The stack is $350 a year for 1 site, $599 for 10 and $999 for 100. The author says tier names and contents changed, so it isn't like-for-like (¶25). The fairness note (¶26) grants that the bundle can be cheaper for someone using all four, calls the 100-site price a real deal for an agency, relays Liquid Web's argument that one version of each product gets fixes out sooner, and says some plans are exempt (Kadence subscriptions, Restrict Content Pro and lifetime licenses). ¶27 says that for someone using one of the four, the math runs the other way. **What the author says isn't the complaint (¶28-¶31).** Give 4.19.0, The Events Calendar 6.18.2 and Kadence Blocks 3.8.0 shipped this month, each linked to a WordPress.org plugin page, and the recap says roadmaps are public again. The author's complaint is uncertainty. The author says retired features and bundles get critical security patches only through April 2027, linked to the May 14 archive. ¶31 ties this to an earlier DigiSavvy post about Automattic: vendors get bought, so plan like they will. **Awesome Motive (¶32-¶36).** The author credits Awesome Motive with moving fast and says WPBeginner's May 15 piece "StellarWP Is No More" calls Liquid Web the parent that owns Nexcess. The author notes that the replacements the guide recommends for GiveWP, LearnDash and Restrict Content Pro (Charitable and MemberPress) sit in Awesome Motive's portfolio, linked to the portfolio page, and calls the guide a sales page. The author also describes an October 15 post on X by Awesome Motive's founder that blanked competitor names as [REDACTED], and notes that Charitable Pro costs $199 the first year and renews at $399, the same as Give Pro now. **The checklist (¶37-¶46).** Five steps before November 16: check the renewal date, audit which of the four products are used, export data, license keys, invoices and plugin zips, don't let the subscription lapse (the FAQ says the site won't break but support, automatic updates and security patches stop), and test alternatives on staging. The author lists alternatives by use case, labels which are Awesome Motive's, says every vendor on the list has a price page and an owner (¶45), and asks readers what their renewal email said and whether anyone warned them first (¶46). ## 🗒️ Notes Paragraph scheme: ¶n is the n-th blank-line-separated block of the source text. Headings and the table rows count. #### 📄 ¶1-¶4 Obituary opener and disclosure - ¶1 is a satirical obituary. It claims the rebrand was announced in a blog post that never once said the brand's name. No link sits beside that claim in the captured markup. ¶9 links the May announcement. - ¶2 states the scope: the plugins are still shipping, so the post is about trust, pricing and how customers found out. It gives the two dates that drive the post, May (brand retired) and October 14 (bundle announced for renewals from November 16). - ¶3 discloses that DigiSavvy builds on LearnDash and has client sites on these plugins, and describes the author as a customer with a stake, not a competitor. - ¶4 is a self-correction about reading acquisition press releases too fast and with too much faith. #### 📄 ¶5-¶11 Timeline of ownership and brand changes - May 2021: Liquid Web buys GiveWP and launches StellarWP. The author quotes the announcement's independent-unit wording (¶7, linked to a liquidweb.com press release). - April 2023: One Equity Partners completes its acquisition of Liquid Web and forms CloudOne Digital (¶8, linked to a oneequity.com news item). - May 12, 2026: four product sites redirect to Liquid Web pages, and an announcement says SolidWP, Iconic, Restrict Content Pro and MemberDash are no longer sold as standalone products (¶9, archive capture dated 2026-05-14). Search Engine Journal covered the backlash. - October 14, 2026: a town hall announces the bundle for renewals on or after November 16 (¶10, linked recap). ¶11 is the author's judgment that this is a long way from independent. #### 📄 ¶12-¶17 Wording in May versus October - ¶12-¶13 quote the May 12 text as still present in an October 6 archive capture: plan, pricing and tools stay the same unless a customer upgrades, and it isn't a forced migration. - ¶14-¶15 quote the package-page FAQ: no single-product purchase, all four products from $350 a year for one site, and a default move at the next renewal. - ¶16 quotes the recap on multiple subscriptions: the first renewal becomes the stack and the others are canceled when it is applied. - ¶17 concedes the statements are technically consistent, because May spoke to an active subscription and the change lands at renewal. The author then uses a film quotation as a joke and tells the reader to judge. #### 📄 ¶18-¶25 Price table and its caveats - ¶19 says the prices are list prices from vendor pages and archived copies, which the links support (March 2026 and May 12 archives, a vendor page for Pro, an October 1 Kadence archive). - ¶20-¶24 hold the table: Give $149 to $199 to $399, Kadence Pro $219 to $299, and the stack at $350, $599 and $999 for 1, 10 and 100 sites. - ¶25 lists three caveats: tier names and contents changed, no actual renewal invoice has been seen, and no clean LearnDash "before" price could be verified, so none is given. #### 📄 ¶26-¶27 Fairness note and the single-product case - ¶26 grants the bundle can be cheaper for anyone using all four, repeats Liquid Web's reasoning about faster fixes, and lists exempt plans (Kadence subscriptions, Restrict Content Pro, lifetime licenses). No link sits beside the exemptions or the faster-fixes statement in the captured markup. - ¶27 says the math runs the other way for a customer using one product, because the FAQ says it can't be bought alone. The table's own Give Pro row ($399 against the $350 stack) cuts against this for Give-only customers (see Logical validity). #### 📄 ¶28-¶31 Plugins aren't dead, uncertainty is the issue - ¶29 lists three current releases (Give 4.19.0, The Events Calendar 6.18.2, Kadence Blocks 3.8.0), each linked to its WordPress.org page, and quotes the recap that roadmaps are public again. - ¶30 states the complaint: widely used products that businesses are built on, and users guessing the vendor's plan. It says retired features and bundles get critical security patches only through April 2027 (linked to the May 14 archive) and points to DigiSavvy's LearnDash hiring and consulting pages. - ¶31 links an earlier DigiSavvy post on Automattic and states the lesson: vendors get bought, so plan for it. #### 📄 ¶32-¶36 Awesome Motive - ¶33 credits Awesome Motive for moving fast and cites WPBeginner's May 15 piece, which per the author calls Liquid Web the same parent that owns Nexcess. - ¶34 says the piece recommends Charitable and MemberPress, both in Awesome Motive's portfolio (linked), and calls the guide a sales page, while saying that isn't necessarily wrong. - ¶35 describes an October 15 post on X by Awesome Motive's founder (linked) that blanked the competitor names. The author found it funny. - ¶36 notes that Charitable Pro is $199 for the first year and renews at $399 (linked), the same as Give Pro, and says to read the renewal line on every pricing page. #### 📄 ¶37-¶45 Pre-deadline checklist and alternatives - ¶39 gives dates: emails went to customers renewing from November 16 to December 1 the week of October 12, the portal shows the new plan from November 3, and per the recap a customer can cancel any time before renewal. The recap link sits in ¶10, not in this paragraph. - ¶40-¶41 say to audit which of the four are used and to export data, license keys, invoices and plugin zips. - ¶42 says not to let the subscription lapse, because the FAQ says the site won't break but support, automatic updates and security patches stop. It offers DigiSavvy's website maintenance, with a link to the pricing page. - ¶43-¶45 say to test alternatives on staging and name them by category: Charitable and Paymattic for donations, MemberPress, Paid Memberships Pro, Tutor LMS and LifterLMS for courses and memberships, Sugar Calendar for events. The author flags which are Awesome Motive's, links Paymattic's own page and a DigiSavvy comparison, and says every listed vendor has a price page and an owner. #### 📄 ¶46 Closing question - The author asks readers what their renewal email said and whether anyone warned them before it arrived. The captured text shows no comments section, so the question has no visible answers. ## 📚 References The link list has 29 anchors. Every link below comes from it, and anchor text is the author's. Several point to web.archive.org captures. The capture timestamp is in the URL (YYYYMMDDhhmmss), and a capture date is not the same as the date a page was published. This analysis fetched none of them. **Article** - [Liquid Web Killed StellarWP. The Plugins Survived. The Trust Didn’t.](https://digisavvy.com/liquid-web-killed-stellarwp/), DigiSavvy, page author Alex Vasquez. The captured text has no publication date. Reader doc id 01m5awbme0j1vfvn5gezmkhbdn. **Primary vendor and ownership sources (¶7-¶10, ¶12, ¶14)** - GiveWP acquisition press release (anchor: independent-unit quote, ¶7): https://www.liquidweb.com/press-releases/liquid-web-acquires-givewp/ - One Equity Partners announcement of the Liquid Web acquisition and CloudOne Digital (¶8): https://www.oneequity.com/news/one-equity-partners-acquires-cloud-services-provider-liquid-web-and-forms-new-holding-company-cloudone-digital/ - Liquid Web new-software announcement, archive capture 2026-05-14 06:04:21 UTC (¶9, and again for the April 2027 security-patch claim in ¶30): http://web.archive.org/web/20260514060421/https://www.liquidweb.com/blog/new-software/ - Same page, archive capture 2026-10-06 20:54:32 UTC, cited for the May wording still being present (¶12): http://web.archive.org/web/20261006205432/https://www.liquidweb.com/blog/new-software/ - Search Engine Journal on the backlash (¶9): https://www.searchenginejournal.com/liquid-web-wordpress-plugin-rebrand-triggers-backlash/574828/ - October 2026 Nexcess software town hall recap (¶10): https://www.liquidweb.com/blog/webinar-recap-live-replay-nexcess-software-town-hall-october-2026/ - Package-page FAQ (¶14) and the price source for the stack row (¶24): https://explore.nexcess.com/software-packages **Pricing sources (¶22-¶24)** - Give pricing, archive capture 2026-03-17 (the $149 Basic row): http://web.archive.org/web/20260317145608/https://givewp.com/pricing/ - Give on liquidweb.com, archive capture 2026-05-12 (the $199 Essentials row): http://web.archive.org/web/20260512105617/https://www.liquidweb.com/software/give/ - Give on liquidweb.com, live page for the $399 Pro tier: https://www.liquidweb.com/software/give/ - Kadence on liquidweb.com, archive capture 2026-05-12 (the $219 row): http://web.archive.org/web/20260512065531/https://www.liquidweb.com/software/kadence/ - Kadence on liquidweb.com, archive capture 2026-10-01 (the $299 row): http://web.archive.org/web/20261001004626/https://www.liquidweb.com/software/kadence/ **Release and roadmap sources (¶29)** - Give 4.19.0: https://wordpress.org/plugins/give/ - The Events Calendar 6.18.2: https://wordpress.org/plugins/the-events-calendar/ - Kadence Blocks 3.8.0: https://wordpress.org/plugins/kadence-blocks/ - Liquid Web webinar recap behind "Roadmaps are public again": https://www.liquidweb.com/blog/webinar-recap-whats-coming-across-kadence-learndash-the-events-calendar-and-give-2026/ **Awesome Motive and competitors (¶33-¶36, ¶44)** - WPBeginner, "StellarWP Is No More": https://www.wpbeginner.com/news/stellarwp-is-no-more-whats-changing-for-givewp-learndash-solidwp-and-your-site/ - Awesome Motive portfolio: https://awesomemotive.com/investments/ - October 15 post on X (anchor: an October 15 post on X): https://x.com/syedbalkhi/status/2110771739651178979 - Charitable page on what happened to GiveWP, cited for $199 first year and $399 renewal: https://www.wpcharitable.com/what-happened-to-givewp/ - Paymattic page on what is happening to GiveWP: https://paymattic.com/whats-happening-to-givewp/ **The author's own DigiSavvy pages (commercial interest, ¶30, ¶31, ¶42, ¶44)** - Hiring a LearnDash developer: https://digisavvy.com/hiring-a-learndash-developer/ - LearnDash consulting: https://digisavvy.com/services/learndash-consulting/ - Website maintenance: https://digisavvy.com/services/website-maintenance/ - Pricing: https://digisavvy.com/pricing/ - Earlier post on Automattic: https://digisavvy.com/your-wordpress-site-doesnt-care-who-runs-automattic/ - Comparison of membership site builders: https://digisavvy.com/best-7-wordpress-membership-site-builders-in/ **Image.** The imgs file lists one image whose alt text repeats the article title. The captured text does not describe what the image shows. **Claims with no link beside them in the captured markup.** ¶1's statement that the rebrand post never said the brand's name. The StellarWP brand retirement in May (¶2, though the ¶9 link covers the May announcement). The October 14 customer notice as an email (¶2, ¶39). The Kadence lifetime-owner download problem beyond the Search Engine Journal link (¶9). The exempt plans and the faster-fixes argument (¶26). The renewal-email timing, portal date and cancel-any-time statement (¶39), which the author attributes to the recap linked in ¶10. The FAQ statement that a lapsed site loses support, updates and patches (¶42) sits on the package-page FAQ linked in ¶14. The rest of the author's claims are opinion. ## 🗣️ Paraphrase The author of this DigiSavvy post says Liquid Web retired the StellarWP brand in May 2026 and, on October 14, told customers that renewals from November 16 move into a single bundle of Kadence, LearnDash, The Events Calendar and Give, starting at $350 a year for one site. The author says the plugins keep shipping releases, so this isn't about dead code. It's about trust, pricing and how customers learned of the change. The author lines up the vendor's own statements: a 2021 line about independence, a May line saying plans and pricing stay the same unless a customer upgrades, and an October FAQ saying a customer can't buy one product alone. The author concedes the May and October texts are technically consistent. The post gives a price table from vendor pages and archives, lists its own caveats, and says the bundle can be cheaper for heavy users. It then tips a hat to Awesome Motive for moving fast, flags that the guide it published recommends its own products, and ends with a five-step checklist and a question for readers. The author discloses a business stake in LearnDash and sells consulting and maintenance. ## 📰 Newsletter **A WordPress vendor changed how it sells four plugins. Here's what one agency says and what it can't show.** DigiSavvy's Alex Vasquez writes that Liquid Web retired the StellarWP brand in May and announced on October 14 that renewals from November 16 move into one $350-a-year bundle of Kadence, LearnDash, The Events Calendar and Give. The post says the package FAQ rules out buying a single product, and quotes a May statement that plans and pricing stay the same unless a customer upgrades. The author calls the two statements technically consistent and still the trust problem. The post gives list prices drawn from vendor pages and archives (Give from $149 to $399 across tier names, Kadence Pro from $219 to $299) and says up front that tier names changed and that no actual renewal invoice has been seen. DigiSavvy sells LearnDash consulting and website maintenance, which the post mentions in passing. If you hold any of these licenses, the post's practical advice is to check your renewal date, audit which plugins you use, export your data and license keys, and test alternatives on staging. Read the original and its linked vendor pages before acting: [DigiSavvy](https://digisavvy.com/liquid-web-killed-stellarwp/). ## ✅ Action items These items concern the reader's own documentation, community and vendor-risk practices. They don't assess any company's pricing decisions. #### DevRel - Developer advocacy: if you cite this post, attribute prices and quotes to the author and the linked vendor pages, and note the author's commercial interest. - Education: draft a short explainer on checking a vendor change against its archived announcements, using the web.archive.org timestamps the way this post does. - Developer experience: document where your own plugin or product states what happens at renewal, and put it where customers see it before they pay. - Developer marketing: when you announce a bundle, say in the first paragraph whether a single product stays available. The FAQ wording in ¶15 is the example of what customers read as the answer. - Community management: no direct action from this source; nearest relevance is ¶46, a question to customers about whether anyone warned them. - Internal/external: route pricing and contract questions to the vendor or counsel and cite only what the vendor pages say. #### OSPO - Policy and governance: record which third-party plugins your organization depends on, who owns each vendor, and the ownership-change history, since ¶31 treats vendor acquisition as a planning input. - License compliance: check whether any license you hold is a lifetime or exempt license with terms that differ from the new package. - Security management: for each dependency, record the vendor's stated security-patch window. ¶30 reports April 2027 for retired features and bundles, linked to a May archive page. - Software inventory: list each of these plugins by site, with renewal date and license holder. - Developer support: prepare a plain answer for users who ask whether a lapsed license breaks the site, citing the FAQ's own wording in ¶42. - Community engagement: no direct action from this source. - Strategic alignment: no direct action from this source; nearest relevance is budgeting for renewal changes. #### Community - Maintainers: if you publish a commercial plugin, publish your bundling and renewal rules on the pricing page and keep archived copies of the old wording. - Contributors: no direct action from this source. - Sponsors: model ¶3, a one-paragraph disclosure of a business stake at the top of an opinion post. - Ecosystem: note ¶36's point that every pricing page, including the rescuing vendor's, has a renewal line worth reading. #### WordPress - Core: no direct action from this source. - Core Performance: no direct action from this source. - Core AI: no direct action from this source. - Core Program Team: no direct action from this source. - Mobile: none. - Playground: none. - Community: none directly; see the Community headings above. - Training: if you teach site ownership, add a lesson on vendor ownership changes and renewal terms, using ¶37-¶43 as an outline. - Marketing: none. - Support: keep a short answer ready for site owners asking whether their Give, LearnDash, Kadence or Events Calendar license is affected, and point them to the vendor's own FAQ. - Design: none. - Documentation: no direct action from this source. - Photos: none. - TV: none. - Polyglots: none. - Accessibility: none from this source. - Meta: none. - CLI: none. - Hosting: none directly; Nexcess is a hosting brand in the story, and the post makes no claim about hosting service quality. - Tide: none. - Openverse: none. - Themes: none; the post concerns plugins. - Plugins: where plugin authors sell premium add-ons, state at purchase whether a future bundle change can alter the plan. #### The WPOCC - Programs: no direct action from this source. - Projects: no direct action from this source. - Funding experiments: none; nearest relevance is that vendor-owned plugins can change commercial terms with private-equity ownership as background (¶8), a point the author raises without evidence of cause. ### FAIR - Technical independence: this post concerns commercial plugin licensing, not distribution architecture. Nearest relevance is that a license-dependent update channel gives the vendor control over who gets patches (¶42), which FAIR-style distribution aims to make portable. - Policies and covenants: no direct action from this source. - Productized governance artifacts: no direct action from this source. ## 🧪 Hypotheses 1. Among customers on the four products, the share who can state the new renewal terms correctly within one week of the October 14 notice is below 50%. 2. For a customer using one of the four products, the bundle at $350 costs less than that product's current lowest paid tier for Give and more for Kadence, which would show that ¶27's generalization depends on the product. 3. The May 12 wording on plans and pricing, if shown without the October FAQ, leads a majority of readers to expect a single-product option to remain. 4. The share of readers who treat this post as neutral drops once the commercial-interest disclosure appears in the first paragraph, compared with ¶3 alone. 5. The 100-site price of $999 undercuts the combined standalone prices for an agency using all four products on 100 sites. 6. Recommendation lists on vendor-owned or services-business sites favor the author's own portfolio or services more often than independent lists do. ## 📊 Methodology - **H1.** Survey a sample of license holders drawn from a plugin-support forum or a maintainers' channel, with consent. Show the October notice text and ask for the renewal date, price and what happens to additional subscriptions. Score answers against the FAQ and recap. - **H2.** Build a table from the same vendor pages and archive captures the author cites. For each product, record every tier name, price and capture date. Compare each to $350 for one site and report the sign of the difference. Flag tiers whose contents can't be matched. - **H3.** Randomize readers into two groups. One sees only the May 12 text and the other sees both texts. Ask what they expect on renewal and compare the share expecting a single-product option. - **H4.** Run a between-groups reading test with the disclosure moved to the top for one group. Measure perceived neutrality on a fixed scale. - **H5.** Collect the standalone list prices at the same capture date for all four products at 100-site tiers. Sum them and compare with $999. State which tiers couldn't be priced, since ¶25 says LearnDash's before price couldn't be verified. - **H6.** Sample 20 alternatives-to-a-product posts from vendor, services and independent sites. Code each recommended product by relationship to the publisher, and report the share that includes an affiliate, portfolio or service tie. ## ❓ Questions - What did the October 14 notice say about prior commitments, and does the May 12 text still appear on the live page, as the October 6 archive suggests? - What is the LearnDash price before and after, and does the bundle price beat it for a LearnDash-only customer? - What does "critical security patches only through April 2027" in ¶30 apply to, given the linked May announcement names SolidWP, Iconic, Restrict Content Pro and MemberDash? - How many customers fall into the exempt groups in ¶26 (Kadence subscriptions, Restrict Content Pro, lifetime licenses), and what is each group's renewal path? - Does the Give $399 Pro tier remain the lowest tier shown on the live page, and does an Essentials tier still exist? - What did Liquid Web say in response to the backlash coverage and this post, if anything? - Did DigiSavvy's clients receive renewal emails the week of October 12, and did those emails match the recap's description in ¶39? - Does DigiSavvy receive any compensation from the vendors, alternatives or services it lists in ¶44? ## 🔮 Future research - **Renewal-term communication.** Compare how software vendors announce a move to bundled renewals across a sample of recent acquisitions, using archive captures to date each statement. - **Archive-based audits.** Test how reliably archive timestamps match the date a vendor page was published, since this post relies on captures dated May 14 for a May 12 announcement. - **Acquirer-driven pricing.** Study price changes after private-equity acquisitions of plugin vendors, with a method for matching tiers, since this post compares across renamed tiers. - **Vendor-rescue marketing.** Measure how "alternatives" articles from competitors differ from independent reviews in the products they recommend. - **Disclosure placement.** Test whether a commercial-interest statement at the top of an opinion post changes how readers weigh its criticism of a competitor's marketing. ## 💡 Implications - **Practice.** Archive vendor pricing and terms pages when you sign up and at each renewal. This post's case rests on archive captures, which exist only if someone saved the page. - **Policy.** Vendors who say a change is not a forced migration should state in the same place what happens at renewal. The two texts the author compares are consistent only once the renewal clause is read. - **Security.** A lapsed license can stop support, automatic updates and security patches while the site keeps running (¶42, per the FAQ). Sites that take payments need a patching owner before a lapse. - **Education.** The post works as a case for teaching tier mapping, since the table's before and after rows use different tier names and the author says so. - **Funding.** The author raises private-equity ownership (¶8) as background and shows no evidence of its effect on pricing. Any link between ownership and price is the reader's inference. - **Legal and procurement.** This analysis is descriptive. Questions about contract terms, refunds or notice obligations go to the vendor, procurement or counsel. ## 🧠 Learning styles assessment - **Reading level estimate.** Flesch-Kincaid Grade Level of about 8 and Flesch Reading Ease of about 65, from a simple syllable heuristic on the 1,322-word body (87 sentences by punctuation, so list items and table rows pull sentence length down). The text uses short sentences and plain terms, with a handful of business terms (renewal, tier, bundle, staging). #### 👀 Visual learners - Present: one table (¶20-¶24) of before and after prices. The imgs file lists one image whose alt text repeats the title. - Improve: a dated timeline of the five events (May 2021, April 2023, May 12, October 14, November 16) would replace the date scattering across ¶7-¶10 and ¶39. #### 🔊 Aural learners - Present: no audio is referenced in the captured text. - Improve: an audio version of the checklist in ¶39-¶43 would serve listeners. #### 🗣️ Verbal learners - Present: short paragraphs, direct vendor quotes, and subheads phrased as questions or statements (¶5, ¶18, ¶28, ¶32, ¶37) make the text easy to follow in order. - Improve: define bundle, renewal and staging in one clause each for readers new to licensing. #### 🧩 Kinesthetic learners - Present: the checklist (¶39-¶43) gives concrete steps: check a date, audit use, export, don't lapse, test on staging. - Improve: add a template for the audit in ¶40, such as a table of plugin, site, renewal date and price. #### 🧠 Logical learners - Present: dated sequence, quoted vendor text beside the author's reading, and explicit caveats (¶25) invite checking. - Improve: show the arithmetic behind each comparison, such as the percentage change per row, so a reader can test ¶27's claim. #### 🧑‍🤝‍🧑 Social learners - Present: ¶46 asks readers what their renewal email said. - Improve: no comment thread or discussion link appears in the captured text. #### 🧘‍♀️ Solitary learners - Present: self-contained, with the context given in ¶5-¶11 and linked sources for each date. - Improve: add a one-line summary of the decision a reader has to make before November 16. #### 🌿 Naturalistic learners - Present: none; the content is commercial and organizational. - Improve: not applicable beyond the human story of customers handling a vendor change. ## 📊 Accessibility assessment Judged from the captured text, the link list and the imgs file only. Rendered contrast, focus order and the page's actual heading markup are unknowable from this capture. #### Screen reader semantics - Present: the capture shows five headings marked with ## (¶5, ¶18, ¶28, ¶32, ¶37), one ### heading (¶20, the word table) and a table whose header row reads Product, Before, After. The ### heading labeled "table" is a placeholder-like label, not a descriptive heading. - Improve: verify real heading elements and a descriptive table caption or heading (WCAG 2.2 AA 1.3.1 Info and Relationships, 2.4.6 Headings and Labels). The table needs header cells so each price is announced with its product (1.3.1). #### Keyboard navigation - Present: 29 links, all ordinary anchors as far as the capture shows. - Improve: not verifiable from text. Check 2.1.1 Keyboard and 2.4.7 Focus Visible on the rendered page. #### Contrast and readability - Present: unknowable from the capture. The paragraphs are short, and the text is plain. - Improve: verify 1.4.3 Contrast (Minimum) on body text, link color and the obituary-style opener, and check that blockquotes (¶1, ¶13, ¶15) are distinguishable without color alone (1.4.1 Use of Color). #### Text resizing and reflow - Present: text with one table. The table is the likeliest reflow risk on a phone. - Improve: verify 1.4.4 Resize Text and 1.4.10 Reflow at 320 CSS px and 200% zoom, with attention to the three-column price table. #### Media and captions - No media referenced in the captured text. The text mentions a town hall and a webinar recap by text link only, and nothing about captions or a transcript for the live event. - The imgs file lists one image whose alt text repeats the article title. An alt that repeats the headline gives no information about the image content (1.1.1 Non-text Content), and if the image is decorative the alt should be empty. The capture can't show which applies. #### Forms and interactions - Present: no form appears in the captured text. - Improve: if a newsletter signup or comment form exists on the page, check 3.3.2 Labels or Instructions. Not visible here. #### Standards reference - Likely gaps to verify against WCAG 2.2 AA: **1.3.1** for the table and headings, **1.1.1** for the title-repeating alt text, and **2.4.4** Link Purpose (In Context) for short anchors such as "source", "May 12", "March 2026", "October 1", "portfolio", "pricing" and "The recap", which pass only if the surrounding sentence gives each link's purpose. "May 12" appears as the anchor for two different pages (a Give archive and a Kadence archive) and is one of the weaker examples. Everything else needs the rendered page. ## 🌍 DEIB assessment #### Cultural breadth - Present: prices in US dollars, US-centric vendors and a US-based WordPress services audience. No regional pricing, tax or currency note appears. - Improve: one sentence on whether the prices are the same outside the US would help non-US readers. This is a context gap, not an error. #### Inclusive language - Present: plain wording throughout. The pop-culture references (the obituary frame in ¶1, a film quotation in ¶17) assume shared cultural context, and so does the idiom "squint" in ¶36 and ¶45. - Improve: replace the idioms with literal wording for readers of English as a second language, for example check the renewal line, in place of apply the same squint. #### Neurodiversity support - Present: short paragraphs, lists, a table and a dated sequence. The checklist in ¶39-¶43 is concrete. - Improve: the mock obituary and sarcasm ("I am altering the deal" as a joke in ¶17) can be hard to read literally. A one-line summary after ¶2 would help. #### Representation - Present: the post names companies and one founder by role in ¶35, and the page author by name. The text gives no gender or background detail for any person, and uses no gendered pronoun for anyone. - Improve: not applicable beyond noting the roster is vendors and a founder. #### Psychological safety - Present: the author names the vendor's own text beside each criticism, concedes consistency in ¶17, and states caveats in ¶25 and ¶26. - Improve: the post doesn't say whether Liquid Web or Awesome Motive was asked to respond. The mock obituary and "rant" label (¶2) set a sharp tone toward companies, though not toward named employees. ## ✅ Logical validity #### Strong reasoning - **Sourcing, ¶7-¶10, ¶12, ¶14, ¶22-¶24.** Each dated claim about the vendor carries a link to a press release, an archive capture or a vendor page, so a reader can check wording and price. The Wayback URLs carry capture timestamps. - **Self-stated limits, ¶25.** The author says tier names and contents changed, that no renewal invoice has been seen, and that a LearnDash before price wasn't verified and so isn't invented. - **Concession, ¶17.** The author grants that the May promise covered plan and price during an active subscription, so the statements are technically consistent. - **Fairness note, ¶26.** The author relays Liquid Web's own reasoning (one version of each product, faster fixes) and the case where the bundle is cheaper. - **Disclosure, ¶3.** The commercial stake is stated up front, with more detail at ¶30 and ¶42. - **Symmetry, ¶36 and ¶45.** The author applies the renewal-line check to the rescuing vendor and says every listed vendor has a price page and an owner. #### Fallacies No formal fallacy runs through the post, which mixes sourced reporting with opinion. What I checked: whether each conclusion follows from the cited sources, whether the table supports the text around it, and whether the author applies one standard to every vendor. These points are about reasoning gaps: - **Generalization against the author's own table, ¶27 versus ¶22-¶24.** ¶27 says that for someone using one of the four, the math runs the other way. The table shows the stack at $350 and Give Pro, the lowest Give tier shown now, at $399, so a Give-only customer would pay less for the stack than for Give Pro. The claim holds against Kadence Pro at $299 and against the $199 Give Essentials price from May 12. It is untested for LearnDash and The Events Calendar, since no prices are given. *Fix:* say the single-product math depends on the product and the tier, and show the comparison per product. - **Title claim without a measure, title and ¶2.** The title’s claim that trust didn’t survive is an assertion. The post shows no survey, no count of customers, and no complaint data beyond a Search Engine Journal link about downloads. The author's own evidence is the wording comparison and the price table. *Fix:* write that the author lost trust and show what customers said. - **Different standard for the competitor's marketing, ¶34 versus ¶42 and ¶44.** The author calls the WPBeginner guide a sales page because its recommendations sit in the publisher's portfolio, and says that isn't necessarily wrong. The post itself recommends DigiSavvy's website maintenance at ¶42, points to DigiSavvy's pricing, and links a DigiSavvy comparison at ¶44. ¶45 says every vendor on the list has a price page and an owner, but the list excludes DigiSavvy. The author discloses the stake at ¶3, so this is a framing gap, not concealment. *Fix:* add DigiSavvy to the squint in ¶45. - **Insinuation by omission, ¶29.** The author quotes that roadmaps are public again and wonders what they were for a while. The recap, as quoted, implies roadmaps weren't public, but the post gives no evidence of what happened in between. *Fix:* state what the author observed. - **Comparison across five years, ¶7 versus ¶11.** The independent-unit line dates from May 2021 and the bundle from October 2026, after an ownership change in April 2023. The post treats the gap as a contradiction without saying whether the statement was meant to be permanent. ¶17 partly offsets this for the May 2026 text. *Fix:* say what the 2021 text promised and for how long. - **Applicability of a date, ¶30.** The April 2027 critical-security window is linked to the May 14 archive page, whose quoted scope in ¶9 covers SolidWP, Iconic, Restrict Content Pro and MemberDash. The captured text doesn't show that the window applies to any of the four products in the bundle. *Fix:* quote the line that names the products covered. - **Success asserted without data, ¶33.** "It worked" for the Awesome Motive campaign has no figure or source in the captured text. The author's characterizations are labeled as such: "rant" (¶2), "technically consistent" (¶17), "sharp marketing" (¶33) and "a sales page" (¶34) are opinion. The vendor quotes in ¶13, ¶15 and ¶16 are presented as quotations of vendor pages. #### Tone of voice - Conversational, sardonic and first-person, with an obituary conceit and humor aimed at companies (¶1, ¶17, ¶35). It loosens into plain, practical instruction in ¶37-¶43. The author's stated mood is cranky (¶3). The post is advocacy from a vendor-adjacent customer: it argues a position, discloses a stake and sells related services. Instruction-style text addressed to an AI or to the reader as an assistant: none found in the article or link list. ## 🛡️ DARVO analysis Not applicable to this source in the usual sense. DARVO (Deny, Attack, Reverse Victim and Offender) describes a response pattern to an accusation. This post makes criticisms instead of answering one, so each prong is checked for the rhetoric of the author and the quoted vendors, with no verdict on anyone's intent. - **Deny.** The author denies the framing that the code is dead (¶2, ¶28-¶29) and denies that this is a competitor taking shots (¶3). The quoted May text (¶13) denies a forced migration, and the October FAQ (¶15) is the text the author sets against it. The post does not say whether Liquid Web has denied or answered anything since. - **Attack.** The author criticizes vendor communication (¶1, ¶11, ¶17), and criticizes Awesome Motive's guide and X post as marketing (¶34-¶35). The criticism is aimed at companies and their statements, not at named employees. The Awesome Motive criticism rests on cited material (the portfolio page, the post on X). - **Reverse victim and offender.** The author casts customers as the affected party and describes DigiSavvy as a customer with a stake (¶3), while DigiSavvy also sells services to customers in the same situation (¶42). The author partly defuses this by naming the stake. The post does not claim that anyone acted in bad faith. - **Vendor voice.** The only vendor voice is quoted text from vendor pages and a recap, not a reply to the author. The post reports no response from Liquid Web, Nexcess or Awesome Motive to its criticism. ## 🎯 Conclusion The post is an opinion piece by a WordPress services business that depends on LearnDash. It says Liquid Web retired the StellarWP brand in May 2026 and announced on October 14 that renewals from November 16 move into one $350-a-year bundle of four plugins. The author supports the timeline with links to the vendor's press releases, archive captures and pricing pages, and says plainly that the price table isn't like-for-like, that no renewal invoice was seen, and that a LearnDash before price wasn't verified. What the post does not establish: customer sentiment (the title's trust claim), what the vendor said in response, whether the April 2027 patch window applies to the four bundled products, or the single-product price comparison for LearnDash and The Events Calendar. ¶27's single-product claim is partly contradicted by the author's own table for Give. The author discloses the LearnDash stake and sells maintenance and consulting, which the reader should weigh against its criticism of a competitor's sales page. **Next steps for readers:** open the archived vendor pages and compare the May text with the October FAQ yourself. Check your own renewal date and email against the recap. Run the product-by-product price comparison for the products you actually use. Treat the author's price figures as the author's reading of list prices on the capture dates. This analysis is descriptive and is not purchasing, legal or financial advice. ## 🔄 Refactor Appendix — Liquid Web Killed StellarWP. The Plugins Survived. The Trust Didn’t. > Density: 2–5 Literature atoms (H3 pad), 0–3 Permanent candidates (H4 pad). > Emitted: 5 Literature, 2 Permanent. Resonance filter applied: the specific price points and > release numbers were dropped as figures that will date quickly. > > Konik claim-header rules: present tense, declarative, ≤10 words, searchable, unique. > > Atomicity: one declarative sentence per atom. "and"/"also" → split. > > Tag pool: #bmf · #addendum · #xref · #articleseed · #storystem · #share · #aphorisms ### 📚 Literature Split Pad #### [H1] A vendor FAQ rules out single-product renewal > [!quote] [¶15] > Can I still buy just one product? No. Every plan now includes all four products, starting at $350 a year for one site. **Context & use**: - ¶15, the author's quotation of the FAQ on the package page. It is the vendor's wording, as the author reproduces it, and the link to the page sits in ¶14. - Set against the May text in ¶13 to show the gap the post is about. The same FAQ says the default move happens at the next renewal. **Tags**: #xref #articleseed  #### [H2] The author admits no renewal invoice was seen > [!quote] [¶25] > I also haven’t seen anyone’s actual renewal invoice, so I can’t tell you what your renewal will say. **Context & use**: - ¶25, one of three stated limits on the price table. - It bounds every price claim in the post to list prices from vendor pages and archives. **Tags**: #xref  #### [H3] The author discloses a business stake > [!quote] [¶3] > DigiSavvy builds on LearnDash, and we have client sites running these plugins. **Context & use**: - ¶3, the opening disclosure. ¶30 and ¶42 add that DigiSavvy sells LearnDash consulting and website maintenance. - Read with H5. The disclosure is partial, since ¶3 doesn't name the services the author sells. **Tags**: #xref #share  #### [H4] The author calls a competitor's guide a sales page > [!quote] [¶34] > I’m not saying that’s wrong. I’m saying that guide is also a sales page. **Context & use**: - ¶34, about WPBeginner's guide recommending products in Awesome Motive's portfolio (portfolio link in ¶34). - The author applies a source-interest test here. The same test applies to the post itself. **Tags**: #xref #articleseed  #### [H5] Every vendor on the list has an owner > [!quote] [¶45] > Everyone on that list is also a vendor with a price page and an owner, so apply the same squint to all of them. **Context & use**: - ¶45, the author's closing standard for the alternatives list. - The list in ¶44 doesn't include DigiSavvy, which sells maintenance in ¶42. The standard covers the list, not the author. **Tags**: #xref #aphorisms  ### 🧠 Atomic Split Pad #### [P1] Check who profits from the advice **Claim** (one sentence, Courtney's voice): When a guide recommends products, I check who owns them and who sells what, and I do the same for the guide that tells me to check. **Evidence pointer**: [[#H3]] · [[#H4]] · [[#H5]] **Scope & conditions**: Holds for vendor-adjacent guides, comparison posts and services businesses. A disclosure lowers the concern without removing it. Weakens when the recommendation is checkable against independent sources, such as a public price list. **Links**: - [[Source interest in recommendation content]] — because extends - [[Disclosure placement and reader trust]] — because applies-in opinion posts by services businesses - [[Vendor rescue marketing]] — because contrasts on who benefits from a vendor's trouble  #### [P2] A price comparison needs a tier map **Claim** (one sentence, Courtney's voice): A before and after price table only means something when each row maps one tier to one tier, and a note says where it doesn't. **Evidence pointer**: [[#H1]] · [[#H2]] **Scope & conditions**: Holds when vendors rename tiers or change contents. Doesn't apply to a single unchanged plan. The post's own table mixes Basic, Essentials and Pro, and the author says so, which makes the caveat the useful part. **Links**: - [[Reading vendor pricing pages]] — because extends - [[Archive captures as evidence]] — because evidence-for with the capture timestamps in the Wayback URLs - [[Bundle pricing and single-product customers]] — because contrasts on who pays more  ### ✏️ Fleeting Queue - [F1] Compare the May 12 announcement text with the live package-page FAQ and record the differences — https://digisavvy.com/liquid-web-killed-stellarwp/ #fleeting #inbox - [F2] Build the product-by-product price comparison for the four products I actually use, with tier names and capture dates #fleeting #inbox - [F3] Open question: does the April 2027 security-patch window apply to any of the four bundled products? #fleeting #inbox - [F4] Article seed: *Archive captures as evidence in vendor disputes,* using the Wayback timestamps in this post #fleeting #inbox #articleseed - [F5] Note the ¶3 disclosure as a model, and add the sold-services line it lacks #fleeting #inbox ### → Things 3 (max 2 actions) - [ ] Check my renewal dates for these four plugins and save the vendor pages to an archive before November 16 — research, 20 min #things - [ ] Build the per-product price comparison from the vendor pages the post links and check ¶27 against it — research, 30 min #things  📄 **Full text:** [[Full Document Contents/Articles/Liquid Web Killed StellarWP. The Plugins Survived. The Trust Didn’t..md|Liquid Web Killed StellarWP. The Plugins Survived. The Trust Didn’t. by Alex Vasquez]] ## Highlights - Quick disclosure before I get cranky: DigiSavvy builds on LearnDash, and we have client sites running these plugins. That’s why I care. This isn’t a competitor taking shots. It’s a customer with a stake and a bad mood. ([View Highlight](https://read.readwise.io/read/01m5awmx3jy01dscw81vcdbfk2)) - Note: [H3] The author discloses a business stake - Tags: atom/literature/h3 - Can I still buy just one product? No. Every plan now includes all four products, starting at $350 a year for one site. ([View Highlight](https://read.readwise.io/read/01m5awmqxj61qgtnvadb0aqkep)) - Note: [H1] A vendor FAQ rules out single-product renewal - Tags: atom/literature/h1 - Caveats, because I’d want them if I were reading this: tier names and contents changed along the way, so it’s not a perfect like-for-like. I also haven’t seen anyone’s actual renewal invoice, so I can’t tell you what your renewal will say. And I couldn’t verify a clean “before” price for LearnDash, so I’m not going to make one up. ([View Highlight](https://read.readwise.io/read/01m5awmts0p1szj1khcj38rvba)) - Note: [H2] The author admits no renewal invoice was seen - Tags: atom/literature/h2 - It’s sharp marketing, and it worked. It’s also funny that the replacements it recommends for GiveWP, LearnDash and Restrict Content Pro are Charitable and MemberPress, both of which sit in Awesome Motive’s own portfolio. I’m not saying that’s wrong. I’m saying that guide is also a sales page. ([View Highlight](https://read.readwise.io/read/01m5awmzdtwjggs4h5ar8be2vr)) - Note: [H4] The author calls a competitor's guide a sales page - Tags: atom/literature/h3 - Everyone on that list is also a vendor with a price page and an owner, so apply the same squint to all of them. ([View Highlight](https://read.readwise.io/read/01m5awn1zh7dtqyfhxjsprr63k)) - Note: [H5] Every vendor on the list has an owner - Tags: atom/literature/h3