Base44 after Wix acquisition: what changed in 2026
Base44 after Wix acquisition is a more capitalized, more stable, and more expensive platform than it was as an independent startup. Wix bought Base44 for approximately $80 million in cash plus a milestone-linked earn-out in June 2025; the deal closed in early July 2025. The visible changes since closing have been three pricing adjustments (October 2025, March 2026, and a contract-only Enterprise tier in May 2026), a re-issued Terms of Service routing disputes to Wix's arbitration framework, an expanded sub-processor list under the new Data Processing Agreement, a slower cadence on platform-stability fixes, and a faster cadence on growth-aligned features. The founding team has stayed through the earn-out window and Base44 still ships under its own brand. The structural question for enterprise buyers is whether Wix ownership reduces vendor risk (yes, on solvency) or increases it (yes, on integration and forced migration risk over a 3-5 year horizon).
The Wix acquisition of Base44 closed on July 2 2025, fifteen days after the June 18 2025 announcement, for an approximate cash consideration of $80 million with an additional earn-out tranche tied to product and revenue milestones. The combined headline number that circulated in the press was $80 million, but the structure matters more than the headline. The cash component bought the company; the earn-out kept the team in place through the integration period.
Across the 30 audit engagements we have run for Base44 customers since the deal closed, roughly 18 percent had the acquisition itself on their risk register at the start of the engagement. By the end of the engagement, that figure was closer to 70 percent — not because the acquisition is uniformly bad news, but because most customers had not modeled the second-order effects on pricing, contracts, and roadmap.
This piece walks through the pre-acquisition state, the deal mechanics, the contractual changes that took effect, the product and pricing shifts since closing, the team retention picture, anonymized customer impact testimonials, and the structural question of whether Wix ownership is a net positive or negative for Base44 users in 2026.
Pre-acquisition state: Base44 in June 2025
Base44 in the months before the Wix deal looked like a typical Series A-stage AI startup, except that it had skipped most of the venture round mechanics. Founder Maor Shlomo built the company largely outside the standard VC fundraising cycle. By the June 18 2025 announcement, the company was approximately 14 months old, had a team of about 35 people, and was at an approximate $5 million annual run-rate revenue.
The product surface in June 2025 was narrower than it is today. The platform offered AI-generated React applications with a managed database, authentication primitives, a Deno-based backend function runtime, and basic deployment. Custom domains had launched two months earlier. The credit-based billing model was already in place. There was no Enterprise tier, no SSO, no dedicated support tier, and no formally published SLA — the standard "commercially reasonable efforts" language sat at the bottom of the Terms of Service.
The competitive landscape at that moment was crowded but unsettled. Lovable, Bolt.new, Replit Agent, and Cursor were all in active iteration. Bubble had been around for a decade and was incumbent in the no-code space but did not have an AI-first generation flow. Webflow had announced AI features but had not shipped a competing primary surface. Wix itself had launched its AI website builder (Wix Studio with AI) but had no equivalent to Base44's full-application generation capability.
The strategic reading at the time of the announcement was that Wix bought Base44 to plug a specific gap: full-application generation, not just websites. The acquisition press release used the phrase "vibe coding" — a term that became normalized in the AI development space over the following year. Wix did not have an in-house team that could ship to that surface on the timeline competition required.
Deal mechanics and contractual structure
The deal closed on July 2 2025. The structure of the consideration, per the merger filings and the Wix Q3 2025 earnings call, was approximately $80 million in cash at close, plus a multi-tranche earn-out tied to product and revenue milestones spanning two years post-close. The exact earn-out cap was not publicly disclosed but estimates from reporting on the deal placed it in the $20-50 million additional range.
Three contractual changes flow from the deal mechanics and are visible to Base44 customers.
Governing entity change. The Terms of Service were re-issued on August 12 2025. The governing entity moved from Base44 Ltd. (the original Israeli company) to Wix Ltd. as parent. Dispute resolution moved to Wix's arbitration framework — JAMS arbitration in California for U.S. customers, with mandatory pre-arbitration negotiation. The original Base44 Terms used Israeli civil court venue. For enterprise customers with vendor management processes that flagged the change, this triggered a contract re-review.
Data Processing Agreement rewrite. The DPA was rewritten on November 4 2025 to reflect Wix's sub-processor list. Eleven sub-processors were added that Base44 customers had not previously contracted with — including Wix's own CDN, Wix's analytics provider, and several Wix-internal services. For GDPR Article 28 compliance, this added 11 sub-processor disclosures to any chain-of-custody audit. We saw three audit engagements in Q4 2025 where this triggered a delay in vendor approval at the customer side.
SLA framework change. The paid-tier SLA language shifted in March 2026 from the original commercially reasonable efforts standard to Wix's tiered SLA model — 99.5 percent uptime for Starter, 99.9 percent for Pro, 99.95 percent for Enterprise. The credits for breach remain capped at the monthly subscription fee, which means a multi-day outage is effectively uncompensated unless a customer is on a separately negotiated Enterprise contract. The change is stricter on paper but the recourse is unchanged in practice. We cover the operational reality in no SLA outage risk.
Product roadmap shifts since the acquisition
The roadmap signal since the deal closed has been two-tracked. New growth-aligned features ship at a faster cadence than they did pre-acquisition. Platform-stability fixes for non-critical bugs ship at a slower cadence. Both are consistent with the post-acquisition resource re-allocation that earn-out structures incentivize.
On the growth-feature side, the visible shipments include native support for embedding Base44 apps into Wix sites (October 2025), an updated visual editor with closer alignment to Wix's design system (December 2025), AI-assisted content generation for marketing copy inside apps (February 2026), and the Enterprise tier with SSO and audit logging (March 2026). All of these have direct upsell motions attached.
On the platform-stability side, the timeline for non-critical bug fixes has lengthened. Pre-acquisition, our audit notes from January through May 2025 showed that platform-reported bugs in the feedback board with under 50 upvotes typically shipped fixes in 2 to 3 weeks. Post-acquisition, the same class of bug — same upvote threshold, same severity — averaged 6 to 9 weeks to a shipped fix across the 12 we tracked from August 2025 through April 2026. Critical issues (security, payments, auth) still ship in days, but the long tail has lengthened.
A specific roadmap item that has been notably deferred is server-side rendering. The feedback board post titled "Essential SEO Improvements" had 199 upvotes at the time of the acquisition and crossed 340 upvotes by May 2026 without a shipped SSR solution. The product comments from the Base44 team have moved from "in active investigation" to "on the longer-term roadmap" — a categorical shift in language. We cover the SEO-specific implications in Base44 app not showing in Google.
The Wix product-line integration items that did ship are interesting in what they reveal about the parent's intent. The Wix-site embedding feature suggests Base44 is being positioned as a backend application layer that Wix sites can incorporate. The design system alignment suggests visual convergence is the medium-term direction. Neither is a hostile signal — both are consistent with Base44 staying a distinct product — but both suggest the long-term arc points toward tighter coupling with Wix's broader stack.
Pricing changes: the most-felt impact
Pricing is where customers have felt the acquisition most directly. There have been three distinct pricing changes since the deal closed.
October 2025 — credit allowance reorganization. Base44 reorganized the credit allowances on the Starter and Pro tiers. Tier prices stayed the same, but the credits-per-dollar ratio dropped. For typical workflows — feature generation, schema edits, function deployment — the effective cost per generation rose between 18 and 25 percent. Customers who had budgeted on the pre-October ratios saw their monthly Base44 line item drift upward without a corresponding usage increase.
March 2026 — Enterprise tier introduction and grandfather expiration. The Enterprise tier launched with SSO, audit logging, custom DPA negotiation, dedicated support, and an SLA that allows for individually negotiated service credits. The minimum commitment is a $50,000 annual contract value. Several features that had been included in the Pro tier moved to Enterprise-only — most notably SSO, role-based access control beyond the basic admin/user split, and audit logging. Existing Pro customers were grandfathered onto their existing feature set for an additional six months.
May 2026 — contract-only price for high-volume credits. The volume credit pricing for accounts above approximately 50,000 generations per month moved to a contract-only model, removing the previously published per-credit price point. The practical effect is that the largest customers now have no published reference price for marginal credit consumption, and pricing is negotiated quote-by-quote.
Across our last 30 audit engagements, the like-for-like spend change for customers who started before October 2025 and continued past March 2026 averaged between 22 and 41 percent. The wide range reflects the mix of grandfathered customers (closer to 22 percent) and customers who had to re-tier into Enterprise to retain SSO (closer to 41 percent). For the 4 customers in that 30 who were specifically using SSO on the Pro tier and had to move to Enterprise, the spend change was between 65 and 180 percent depending on negotiated discounts.
We cover the operational implications of the credit model — independently of the acquisition — in Base44 credit system explained and the pricing reality in Base44 pricing real costs analysis.
Team retention and roadmap velocity
Founder Maor Shlomo and the original engineering leadership stayed at Wix through the publicly visible release cadence of the year following the deal. This is consistent with the earn-out structure. The visible engineering output — released features, GitHub-equivalent issue closures on the feedback board, conference presence — has been from the original Base44 team operating under Wix governance, not from Wix engineers absorbing the product.
What is harder to track from outside is attrition at the IC engineering layer. Public LinkedIn moves over the year following the deal showed roughly 8 engineers departing Base44 — a normal-to-slightly-elevated turnover rate for a 35-person team going through an acquisition. New hiring is happening, but the listings have been routed through Wix's careers page since November 2025, which obscures the headcount picture.
The roadmap velocity signal has two patterns we noted in the previous section. Growth features ship faster; platform stability fixes ship slower. A third pattern is worth calling out: documentation and developer-experience improvements have effectively paused. The docs site received its last substantive content addition in September 2025 — minor copy updates have continued, but no new section, no new SDK reference page, no new tutorial content. Customers who have built on the platform since late 2025 have been working off increasingly stale docs.
Customer impact: three anonymized scenarios
We have run audit engagements with roughly 60 Base44 customers in the year since the deal closed. The following three are anonymized composites that map cleanly onto recurring patterns we have seen.
Scenario one: the marketplace startup. A two-founder marketplace startup signed up in March 2025, built their MVP on Base44 over six weeks, and launched in May 2025. They were on the Pro tier at the original credit allowance. Their post-acquisition impact: monthly spend rose 28 percent through the October 2025 pricing change without any usage increase. They added one developer in January 2026 and the seat cost rose. They needed SSO in March 2026 for a Series A enterprise pilot and discovered that SSO had moved to Enterprise tier — a $50,000 ACV minimum. They migrated the SSO surface to a separate Next.js authentication layer running on their existing domain and routed the rest of the app to Base44. The migration took two weeks and cost roughly $18,000 in our engagement time. Net effect: they stayed on Base44 for the application layer, paid Pro tier pricing, and got the enterprise auth requirements satisfied off-platform.
Scenario two: the agency builder. An agency building client apps on Base44 had 14 client apps in production at the time of the acquisition. Their post-acquisition impact: client billing got more complicated as the credit reorganizations rippled through their per-client pricing. Two client apps required SSO after the March 2026 Enterprise gating, and the agency was forced to either re-tier those clients onto Enterprise — passing through a 4x cost increase the clients refused — or migrate them to an alternative. They migrated both clients to a Next.js + Supabase stack over the following four months. The remaining 12 clients stayed on Base44 because the cost increase was absorbable. This is the pattern we see most often: partial migration of the most enterprise-adjacent apps, retention of the rest. We cover the agency-specific dynamics in Base44 for agencies.
Scenario three: the regulated industry pilot. A health-tech company that had been piloting Base44 for an internal tool encountered the DPA rewrite in November 2025. Their HIPAA review process required documentation of every sub-processor handling PHI. The new 11 sub-processors triggered a full vendor re-review, which delayed the internal tool launch by six weeks while their compliance team worked through the new chain. The tool eventually launched, but the team's compliance lead flagged Base44 as "high friction for regulated use cases" in the next vendor review cycle. Net effect: Base44 retained the customer but lost the next two app deployments to a Next.js stack on their existing cloud provider where the sub-processor surface was already approved.
The pattern across all three scenarios is that the acquisition did not cause an immediate customer-facing crisis. The friction accumulated quietly through pricing, contracts, and feature gating. Customers who noticed and modeled the second-order effects early adjusted their architecture before the friction became expensive. Customers who did not notice continued to pay the higher cost without an explicit decision to do so.
Is Wix ownership a positive or negative for Base44 users?
The honest answer is that it depends on the customer's threat model.
For customers whose primary vendor risk was Base44-as-a-startup going under, Wix ownership is a clear net positive. The legal entity behind the platform is now Nasdaq-listed (WIX), with $1.6 billion in annual revenue, a 25-year operating history, and a cash position that does not depend on the next venture round. The probability that the platform simply disappears in a 24-month window dropped substantially after the deal.
For customers whose primary vendor risk was integration risk — a forced migration, a forced pricing model change, a forced product direction that did not match their use case — Wix ownership is a clear net negative. The probability of those events is higher under Wix than under an independent Base44, because acquiring companies do eventually rationalize overlapping products. The five-year horizon for this risk is real, even if the 24-month horizon is calm.
For customers in the middle — modest scale, no exotic compliance requirements, no extreme price sensitivity — the acquisition is closer to neutral with a mild positive bias. Pricing went up, but service-level stability also went up. Roadmap shifted, but the core product surface is still functional. The friction is real but absorbable.
The structural recommendation we make in audit engagements has not changed because of the acquisition. Decouple from the SDK so that migration remains an option. Maintain an export path so that data ownership is portable. Track the credit model so that pricing changes do not surprise the finance team. Watch the roadmap signal so that strategic platform shifts do not catch the engineering team flat-footed. The acquisition raised the stakes on all four of these disciplines but did not change the disciplines themselves.
How to track the acquisition impact going forward
The signals worth tracking quarterly are public, lightweight, and cumulatively informative.
// A minimal monitoring sketch for tracking acquisition signals
const signals = {
pricingChanges: "https://base44.com/pricing", // diff monthly
termsOfService: "https://base44.com/terms", // diff quarterly
dpa: "https://base44.com/dpa", // diff quarterly
feedbackBoard: "https://feedback.base44.com", // monitor top 10 issues monthly
status: "https://status.base44.com", // monitor incident frequency
jobsListings: "https://www.wix.com/careers", // filter "base44" monthly
releaseNotes: "https://docs.base44.com/changelog", // monitor cadence
};
The diff of the pricing page month over month is the single highest-signal data point. The cadence of release notes and the depth of changelog entries is a close second. The feedback board's top issues — and how long they stay at the top — is the third. Together these three are enough to maintain a defensible view of platform direction without subscribing to expensive analyst services.
The contract-level signals — Terms of Service, Data Processing Agreement, sub-processor list — are worth diffing once per quarter and routing through whoever owns vendor management. Most enterprise customers we work with did not have a process for catching the August 2025 ToS change or the November 2025 DPA rewrite until the audit engagement surfaced both.
The strategic question for 2026 and beyond
The structural question that customers should be asking in 2026 is not whether the Wix acquisition was good or bad — that question is too coarse to be useful. The structural question is whether the customer's three-year roadmap is compatible with the most likely Wix-Base44 trajectory.
The most likely trajectory, based on the visible roadmap and pricing signals, is that Base44 stays a distinct product through the earn-out window (mid-2027), gradually converges on Wix's design and runtime stack through the following 12 to 18 months, and either becomes a sub-feature of Wix's broader platform or is wound down in favor of a Wix-native equivalent on a 4 to 5 year horizon. This is not certain — many acquisitions resolve differently — but it is the modal outcome for the structure Wix bought.
Customers whose three-year roadmap fits inside that trajectory — modest scale, no exotic requirements, comfortable with the convergence direction — should plan to stay. Customers whose three-year roadmap pushes against the trajectory — large scale, regulated industries, strong SEO requirements, deep platform customization needs — should be planning their migration path now, even if they do not execute on it for 12 to 18 months. See When to leave Base44 for the decision framework we use with audit clients, and Base44 vendor lock-in deep dive for the technical decoupling work that precedes any migration.
The acquisition is not a crisis. It is a re-pricing of the platform's risk profile that customers should be modeling explicitly. The customers who model it explicitly will be in better shape, regardless of which way the platform ultimately goes.
Frequently asked questions
The FAQ block above answers the six most common questions we get on the acquisition. If your specific question is not covered there, the audit engagement walks through the customer-specific implications in detail.
Related reading
- Base44 user sentiment and security disclosures after the Wix acquisition — companion piece on the user-visible side: G2/Trustpilot review drift, the Wiz SSO bypass and Imperva XSS disclosures, the Feb 3 2026 outage, and the November 2025 record-limit change.
- When to leave Base44 — the migration decision framework we use across audit engagements.
- Base44 vendor lock-in deep dive — the technical decoupling work that gives any customer optionality regardless of platform direction.
- Base44 pricing real costs analysis — current pricing structure, hidden cost drivers, and how the acquisition has reshaped the cost model.