Why this matters
Acquisitions change platforms in predictable ways. Most users skip the post-acquisition due diligence, treat the platform as if nothing changed, and discover the changes one billing cycle or one outage at a time. This article is the diligence: what changed, what didn't, and what those changes imply for anyone running production apps on Base44 in 2026.
Sources are TechCrunch's original deal coverage, Product Hunt and G2 reviews from before and after the deal, the Base44 changelog, security researcher disclosures from Wiz and Imperva, the platform's status page, and our own client engagements during the transition.
Timeline
Pre-acquisition: late 2024 to June 2025
Base44 launched as a solo-developed AI app builder in late 2024. The product gained rapid traction in the vibe-coding space, competing with Lovable, Bolt.new, and Replit's AI features. The founder (single person) ran product, engineering, and growth.
Sentiment in this period was overwhelmingly positive. Early reviews praised the speed, the AI agent's capability, and the founder's responsiveness. Pricing was simple, support was direct (the founder responded personally), and the platform's quirks were tolerated as the cost of an early-stage product.
June 18, 2025: acquisition announced
Wix announced the acquisition for $80 million cash. TechCrunch's headline framed it as "6-month-old solo-owned vibe-coder Base44 sells to Wix for $80M cash." The deal closed in July 2025.
The narrative around the deal was strategic: Wix wanted exposure to AI-driven app construction to compete with Squarespace's AI features and the broader vibe-coding category. Base44's traction and small team made it an attractive bolt-on rather than a competitor to be ignored.
July 2025: security disclosures
Within weeks of the acquisition closing, Wiz published a critical vulnerability disclosure about an SSO bypass affecting Base44. The vulnerability allowed any attacker to register a verified account on private SSO-only apps using only the app_id. Wiz wrote: "Attackers could create a verified account on private apps using only an app_id."
Imperva followed shortly with disclosures of stored XSS in the /apps-show/ endpoint and JWT leakage via URL fragments. Imperva's quote: "Injected code had access to authentication tokens stored in browser local storage." And: "An attacker wouldn't just control the single app: they could access the victim's full Base44 account."
The platform patched both disclosures within 24 hours of report. The underlying class of vulnerabilities — default-permissive trust between authenticated users — was not structurally addressed and remains a concern as of May 2026.
August–November 2025: pricing adjustments
User reports on Product Hunt and Trustpilot started citing price increases and reduced credit allowances. The platform did not issue a public price-change announcement; users discovered the changes at billing time. Quote from a Product Hunt review: "You can't buy more credits unless you upgrade to an expensive tier plan."
We saw this in client engagements as well. Apps that ran comfortably within their tier in mid-2025 were over-tier by year-end. Whether the changes were de jure (tier price increases) or de facto (reduced credit allowances per dollar), the effect was the same: the platform got more expensive.
Late 2025: support response degradation
G2 and Trustpilot reviews began citing multi-week response times for support tickets. One representative quote: "Support ticket opened March 29 never received a single reply." Another: "Spent 10+ hours with AI support; received 8-10 useless solutions per issue."
This is a common post-acquisition pattern. A small company's support function, where one person knew every customer's app, gets integrated into a larger company's ticketing pipeline. The institutional knowledge does not transfer cleanly. Customers who used to get same-day responses now wait weeks.
November 27, 2025: explicit limit changes
The platform shipped a documented 5,000-record-per-request limit, replacing whatever the previous (undocumented) limit was. This broke at least some apps that had been listing larger result sets without pagination. Adaptation was straightforward but unannounced before the change took effect.
February 3, 2026: platform-wide outage
A multi-hour platform-wide outage hit on February 3. Status.base44.com confirmed the outage; the post-mortem (if one was published internally) was not published externally. There is no SLA at any tier, so users with affected apps had no recourse beyond waiting.
This was the first widely-reported sustained outage post-acquisition. Earlier outages had been shorter or scoped. The February event made the absence-of-SLA a tangible problem for production apps.
March 2026: custom integrations deprecated
The platform signaled that adding new custom integrations after March 1, 2026 would no longer be supported. Existing custom integrations continue to work, but new integrations must go through backend functions. This affected enterprise customers who had relied on platform-managed integration wrappers for niche services.
May 2026: where we are now
The acquisition is eleven months old. The product surface has changed in measurable ways. The team identity has shrunk in user-facing visibility. Roadmap communications are sparse. Status quo as of writing:
- Pricing trends 15–30% higher per equivalent app footprint than mid-2025.
- Support response times measured in days to weeks rather than hours.
- AI agent behavior more aggressive on regeneration, more frequent on regressions.
- Security defaults still permissive, two major disclosures patched but not architecturally fixed.
- No SLA at any tier.
- No SOC 2 or HIPAA attestation published.
- Custom integrations deprecated.
What stayed the same
Not everything changed. To be balanced:
The AI agent still ships fast. The core value proposition — "describe an app, get a working app in minutes" — still works for prototypes. The speed-to-first-prototype is unchanged or better.
The IDE remained stable. The development environment, the agent UI, the entity editor, the deployment flow all look and work like they did in early 2025. No major UX overhauls.
The brand stayed visible. Despite Wix ownership, the Base44 name, domain, and product identity are intact. There has been no rebrand, no merge into a Wix subdomain.
The pricing structure (not the prices) stayed similar. Subscription tiers with credit allowances, code export gated behind Pro, same general shape. The changes are within the structure, not to it.
Custom domains still work. Pro tier still supports custom domains, SSL is still automatic, DNS instructions are unchanged.
What users complain about now vs. before
A loose comparison from public review trends:
| Complaint category | Pre-acquisition (2024–early 2025) | Post-acquisition (mid 2025–2026) |
|---|---|---|
| AI agent regressions | Common, but founder responsive | Common, no clear escalation path |
| Pricing | Considered fair | Considered expensive |
| Support response | Hours to days | Days to never |
| Stability | Bursty quality | Sustained outage Feb 2026 |
| Security | Limited disclosures pre-deal | Two major disclosures post-deal |
| Code export | Beta but improving | Still beta, no clear ETA |
| Roadmap clarity | Founder-driven, transparent | Corporate, opaque |
This pattern is consistent with what happens when a small founder-led company is acquired by a larger one. It is not a moral judgment of either party. It is the realistic operational shift.
Implications for current users
If you are running a production app on Base44 today, the acquisition shifts your risk profile in three ways.
Roadmap risk increased. Wix's strategic interests now drive Base44's roadmap. If Wix's primary customer (SMB website builders) doesn't share your needs (developer tooling, production apps, regulated workloads), your needs may be deprioritized. The custom-integrations deprecation is an early signal of this.
Pricing risk increased. Wix is a public company with quarterly earnings expectations. Pricing power on Base44 is now subject to Wix's quarterly pressures, not just the founder's intuition. Plan for further price increases of 10–25% annually.
Support risk increased. Larger company, less responsive support. Treat platform support as advisory, not load-bearing. Build your own runbooks for everything you might need to fix.
Implications for prospective users
If you are evaluating Base44 in 2026, the post-acquisition state is the relevant baseline. The romantic version of the platform — solo founder, tight feedback loop, clean security — is no longer current.
This does not mean don't use Base44. It means use Base44 with eyes open about the post-acquisition reality:
- Treat support as nonexistent for response time planning.
- Budget 25% headroom on subscription costs.
- Assume the SLA is "best effort" and plan for outages.
- Harden security manually because the platform's defaults are still permissive.
- Maintain a documented exit plan from day one.
If those compromises work for your app, the platform still ships value. If they don't, look at alternatives — we cover the migration paths in our migration playbooks.
What we don't know
To be honest about the gaps in this analysis:
- Wix has not published Base44-specific revenue or growth numbers, so we don't know the platform's commercial trajectory.
- The internal team size and composition under Wix is not publicly known.
- The roadmap beyond the next 90 days is not communicated publicly.
- Whether the founder is still actively involved (vs. transitioned out) is not publicly confirmed as of writing.
These unknowns are themselves a signal. A platform that doesn't communicate its plans is harder to plan against.
Common acquisition-era mistakes
Assuming the platform you signed up for in early 2025 is the platform you have today. It is not. Re-evaluate annually.
Treating support response times as recoverable. They have not recovered post-acquisition. Plan around the slow path.
Skipping the security re-audit after the disclosures. If you set up your app pre-July 2025, you may still be running on patched-but-not-architecturally-fixed defaults. Re-audit.
Assuming the founder's documented responsiveness applies today. It does not. The founder is not the platform's customer-facing layer anymore.
Discounting the SLA absence because "it's been fine so far." February 3, 2026 was the proof point. Plan for the next one.
Summary
The Wix acquisition was financially good for Base44's founder and operationally mixed for Base44's users. The platform still works for what it works for — fast prototyping, AI-driven app construction, indie builds — but production apps face a higher operational burden than they did pre-acquisition. Plan accordingly.
The decision framework for whether to stay, harden, or migrate is in our is base44 production ready article. The realistic cost of leaving is in our vendor lock-in deep dive.
Want us to assess your acquisition-era exposure?
Our $497 audit reviews your app's security posture, support runbook, exit plan, and cost model in light of the post-acquisition reality. We deliver a prioritized list of mitigations. Order an audit or book a free 15-minute call.
Related reading
- Base44 Pricing Real Costs Analysis — the detailed cost numbers behind the acquisition-era pricing.
- Base44 Limitations Explained — the structural limits that didn't get fixed post-acquisition.
- Is Base44 Production Ready? — the decision framework that incorporates post-acquisition risk.