Base44 Deep Dive: Feasibility Analysis for Accounting Firms

Executive Summary

Base44 is an AI-powered no-code application generation platform that enables users to build complete web applications through natural language descriptions. This report systematically evaluates Base44's applicability in accounting firm scenarios using the PAID + RISE methodology (PAID = Problem-Analysis-Impact-Distribution; RISE = Reality-Issue-Solution-Evaluation), informed by 36 verified industry sources including CA ANZ guidance, AU/NZ privacy regulations, and accounting industry benchmarks.

Key Findings:

• Recommended for: Internal tool development (bank CSV conversion, WIP analysis dashboards, client onboarding systems)
• Not recommended for: Core financial workflows involving cross-system write operations (dual invoicing, automatic write-back), or handling sensitive client financial data without thorough compliance review
• Critical compliance consideration: Base44 lacks SOC 2 and ISO 27001 certifications (as of late 2025) and experienced a security incident in July 2025
• Target users: 10-50 person accounting firms with 1-2 technical staff and established data governance practices

Bottom line: Base44 is a powerful accelerator for rapid internal tool development, but accounting firms must carefully evaluate compliance risks against productivity gains.

Chapter 1: Product Overview

1.1 What is Base44

Base44 is an AI-powered no-code application building platform. Users describe their application needs in natural language, and the platform automatically generates a complete web application—including frontend interface, backend database, user authentication, and optional third-party integrations.

Founded by Maor Shlomo in early 2025, Base44 experienced explosive growth: acquired by Wix for approximately $80 million in June 2025, reaching ~250,000 users and profitability with only ~8 employees. By early 2026, ARR surpassed $100 million. Notably, 90% of Base44's own codebase was reportedly written using Anthropic's Claude AI. The platform currently operates as an independent product under Wix, though the long-term integration direction remains to be seen.

Core Positioning: Positioned between traditional no-code platforms (like Bubble) and AI code generation tools (like Lovable). It offers both visual editing capabilities and an AI conversational interface to lower the barrier to entry.

1.2 Core Features

Natural Language Generation: Users describe requirements, AI automatically generates data models, frontend pages, and business logic.

Built-in Database: Each application automatically receives PostgreSQL database support with automatic schema creation and relationship management.

User Authentication: Out-of-the-box registration/login, role permissions, and access control.

UI Component Library: Form components, data display, navigation, and feedback components.

Third-Party Integrations: One-click connections to Stripe, SendGrid, Twilio, AWS S3, OpenAI, and more.

Backend Functions: Pro tier supports custom backend logic, scheduled tasks, and webhook processing.

1.3 Workflow

1. Requirement Description (5-10 min): Describe needs in natural language, AI generates initial version
2. Visual Adjustment (30-60 min): Drag-and-drop interface modifications, adjust data models
3. Integration Setup (10-30 min): Connect third-party services, configure APIs
4. Testing and Validation (15-30 min): Preview and test, fine-tune details
5. Deployment (1 min): Click Publish, receive unique domain

1.4 Capability Boundaries

What Base44 Can Do: Data collection forms, dashboards, simple approval workflows, client portals, file processing tools, calculators, simple CRM, MVP validation.

What Base44 Cannot Do: Complex business logic, cross-system transactions, large-scale data processing, highly customized UI, native mobile apps.

1.5 Competitive Comparison

Product	Key Feature	Learning Curve	Best For
Base44	AI generation + hosted	Low	Rapid validation, internal tools
Lovable	AI code generation	Medium	Self-deployment, customization
Bubble	Mature ecosystem	High	Long-term business systems
Glide	Spreadsheet-driven	Low	From existing data
Make / n8n	Workflow automation	Medium	Cross-system writes, transactions
Retool	Internal tool builder	Medium-High	Enterprise internal data tools

Chapter 2: Accounting Firm Scenario Evaluation

2.1 Scenario S2: Bank CSV Converter

Business Context

Many Chinese clients use Chinese banks (Bank of China, ICBC, CCB) that don't directly integrate with Xero. Accountants must monthly:

1. Log in to online banking and download CSV statements
2. Open Excel and adjust formats (dates, amounts, encoding)
3. Save in Xero-compatible format
4. Upload to Xero and verify

Each bank's CSV format differs:

• Date formats: YYYY-MM-DD vs DD/MM/YYYY vs MM-DD-YY
• Amount columns: Debit/credit separate vs positive/negative vs parentheses
• Encoding: UTF-8 vs GBK (Chinese characters)
• Column names: Different naming conventions

Per client per month: 15-30 minutes. For 20 such clients: 5-10 hours monthly.

Base44 Implementation

File Upload Interface: Drag-and-drop area, multi-file batch upload, restrict to .csv and .xlsx formats.

Bank Recognition Module: Auto-detect bank type (via column names, date format signatures), manual selection when auto-detection fails, custom bank template support.

Format Conversion Engine: Standardize dates to YYYY-MM-DD, standardize amounts (negative for expenses), convert encoding to UTF-8, map column names to Xero standards.

Preview and Download: Preview converted data (first 10 rows), flag anomalies (date errors, amount exceptions), download Xero-compatible CSV.

Technical Implementation: Pure frontend JavaScript (no backend functions needed), use PapaParse library for CSV parsing, client-side conversion, no server upload.

Evaluation

Dimension	Rating	Notes
Complexity	2/5	Clear logic, simple branching
Feasibility	5/5	Pure file processing
Risk	5/5	No APIs, no data upload
ROI	5/5	1 day dev, 5-10h saved/month

Suitability: 5/5 (Highly Recommended)

Implementation Tips: Start with Free tier to validate core conversion logic, gradually support more bank formats, consider adding format validation.

2.2 Scenario S5: WIP Analysis Dashboard

Business Context

Work In Progress (WIP) is a core accounting firm metric. Current challenges:

• Data silos: Timesheets, expenses, client bills in different systems
• Analysis difficulty: XPM built-in reporting is weak, requires Excel export
• Poor timeliness: Usually see last month's data at month-end
• Hard to spot anomalies: Over-budget projects, aging WIP

Typical analysis needs: staff utilization, client profitability, project budget execution, WIP aging analysis.

Base44 Implementation

Data Sources: XPM API for time entries, WIP, project data. May need Xero API for invoice data cross-validation.

Data Sync: Scheduled automatic XPM data pull, data caching to reduce API calls, incremental updates.

Management Dashboard: Overall KPIs (total WIP, average aging, utilization), trend charts (this month vs last month vs last year), alerts (over-budget projects, aging WIP).

Staff Dimension: Individual utilization rankings, work type distribution, non-billable hours analysis.

Client Dimension: Client profitability rankings, client WIP aging analysis, exception expense flagging.

Project Dimension: Budget vs actual comparison, progress tracking, risk alerts.

Technical Implementation: Pro tier required (backend functions for XPM API), use Chart.js for visualization, caching strategy for API cost management.

Evaluation

Dimension	Rating	Notes
Complexity	3/5	Multi-dimensional analysis
Feasibility	4/5	API integration, read-only
Risk	5/5	Read-only, zero risk
ROI	5/5	Partner decision tool

Suitability: 5/5 (Highly Recommended)

2.3 Scenario S6: Client Onboarding System

Business Context

New client onboarding involves multi-department collaboration. Current pain points:

• Information collection: Via email/WeChat, inconsistent formats, often incomplete
• Multi-system entry: XPM setup, SharePoint folders, DocuSign agreements
• Progress tracking: Unclear which stage is current
• Client experience: Repeated document requests

Standard process involves 6-7 people, 1-2 weeks average.

Base44 Implementation

Client Information Portal: Multi-step form (company, contacts, banking, tax), field validation (IRD numbers, bank accounts), document upload, progress saving.

Completeness Check: Auto-check required fields, flag missing documents, one-click supplemental request generation.

Document Auto-Generation: LOE template + auto-filled variables, CAT Form risk assessment, multi-format export (PDF, Word).

Process Tracking: Visual workflow diagram, current stage highlight, estimated completion time.

Notifications and Reminders: Automatic email notifications, timeout alerts (3-day auto-reminder), escalation (manager notification for non-response).

Technical Implementation: Pro tier required (backend functions), DocuSign API integration, consider Make/Zapier for XPM/SharePoint integration.

Evaluation

Dimension	Rating	Notes
Complexity	4/5	Multi-step, multi-system
Feasibility	4/5	Core feasible, some via tools
Risk	3/5	Multi-system consistency
ROI	4/5	Better client experience

Suitability: 4/5 (Recommended)

2.4 Scenario S4: Dual Invoicing — Why Not Suitable

Business Context

Firms using outsourced bookkeeping services face special invoicing workflow:

1. Connex fees entered as disbursements in project WIP
2. Need two invoices: internal (with cost details, zeroes WIP), client (hides costs)
3. Both invoice amounts must match
4. Errors require deletion in both XPM and Xero

Peak season: one person processes 20-30 invoices daily.

Why Base44 Is Not Recommended

No Transaction Consistency: Cannot guarantee XPM and Xero invoicing succeed/fail together, risk of data inconsistency.

No Rollback Mechanism: Once errors occur, cannot automatically undo completed operations, requires manual deletion in both systems.

Difficult State Sync: Invoice status changes must sync across systems, Base44 struggles with bidirectional sync.

Business Risks: Invoice errors affect client relationships, WIP errors affect staff KPI calculations.

Better Alternatives

• Workflow Automation: Make/n8n, professional engine with transaction support
• Custom Development: Python/Node.js, full control, complete transaction management
• Root Solution: Replace Connex, dual invoice problem disappears if S1 succeeds

Suitability: 2/5 (Not recommended for Base44)

2.5 Scenario S1: Transaction Auto-Classification — Limited Applicability

Business Context

Bank transactions need accounting category classification. Pain points: outsourced classification quality varies, year-end corrections needed, Xero Bank Rules limitations.

Base44 Limitations

Stability Risk: Base44-generated backend functions are prototype-level, high-frequency API calls may timeout or fail, classification errors affect GST reporting.

Error Handling Difficulties: Cannot guarantee 100% accuracy, rollback and correction of errors is complex.

Limited Applicability

• Assistant Interface: Display unclassified transactions, recommend categories, batch process after human confirmation
• Not Recommended: Automatic write-back to Xero, direct Xero API calls not advised

Better Options: Xero Bank Rules (simple rules), dedicated AI classification tools (Dext, Hubdoc).

Suitability: 3/5 (Limited applicability, interface only)

Chapter 3: Compliance and Regulatory Considerations

3.1 The Compliance Landscape for AU/NZ Accounting Firms

According to the CA ANZ AI Fluency Playbook (August 2025), 85% of chartered accountants are willing to use AI, yet only 21% of firms have an AI policy or strategy. This gap represents significant compliance risk for firms adopting platforms like Base44 without proper governance frameworks.

Key Regulatory Frameworks:

• New Zealand: Privacy Act 2020 (IPP 5, IPP 12, Section 11 Agency Relationship)
• Australia: Privacy Act 1988 (APP 8 Cross-border Disclosure, APP 11 Security, APP 1 Transparency)
• Tax Practitioner Obligations: TPB(PN) 1/2017 Cloud Computing and Code of Professional Conduct

3.2 Data Sovereignty and Cross-Border Considerations

The NZ Privacy Act 2020's Section 11 (Agency Relationship) is particularly relevant: when a cloud provider holds personal information solely as an agent for storage or processing, that information is treated as held by the accounting firm, not the cloud provider. This means cross-border cloud storage is generally not a "disclosure" under IPP 12, provided the cloud provider is not using data for its own purposes.

However, the OAIC's Guidance on Privacy and the Use of Commercially Available AI Products (2025) explicitly requires accounting firms to conduct due diligence on AI platforms, including verification of security practices and contractual protections. Base44's lack of SOC 2 or ISO 27001 certification (as of late 2025) presents a significant gap in demonstrating these protections.

3.3 Tax Practitioner Board Requirements

TPB(PN) 1/2017 requires registered tax agents to obtain client permission before storing information with cloud providers under Code Item 6 of the Tax Agent Services Act. This applies regardless of whether the cloud provider is domestic or international.

Practical Implication: Any Base44 application handling client tax information requires:

1. Explicit client consent for cloud storage
2. Disclosure of the cloud provider (Base44/Wix) in privacy policies
3. Verification that the provider meets security obligations

3.4 Base44's Compliance Status

Security Certifications: As of late 2025, Base44 has not announced SOC 2 or ISO 27001 certifications. This is a critical consideration for accounting firm use cases handling client financial data.

Security Incident: In July 2025, Wiz Research disclosed an authentication bypass vulnerability allowing unauthorised registration to private apps. While patched within 24 hours with no confirmed exploitation, this incident highlights the platform's immaturity from an enterprise security perspective.

Upcoming Regulation: The Privacy and Other Legislation Amendment Act 2024 introduces mandatory PIAs for high-risk projects and new automated decision obligations commencing December 2026, directly relevant to AI platform adoption.

Recommendation: Firms should conduct a Privacy Impact Assessment (PIA) before deploying Base44 for any application handling client data, following the OAIC's 10-step PIA process.

Chapter 4: Technical Integration Constraints

4.1 Xero API Rate Limits

For accounting firms considering Base44 for Xero integration, the platform must operate within Xero's strict rate limits:

Limit	Value	Impact on Base44 Apps
Concurrent calls	5	Limits real-time sync
Calls per minute	60	Primary bottleneck
Calls per 24 hours	5,000	Limits daily volume
App-wide limit	10,000/min	Rarely hit
Payload size	3.5 MB	Limits batch upload
Org connections (uncertified)	25	Limits multi-tenant

Source: Xero Developer Documentation

4.2 Implications for Base44 Scenarios

S5 WIP Dashboard: With daily sync of time entries across 50 active projects, a firm could easily exceed 5,000 calls/day. Caching strategies and incremental updates are essential.

S6 Client Onboarding: Creating Xero contacts via API for each new client (2-3 calls per client) remains well within limits for typical firm volumes.

S1 Auto-Classification: Attempting to classify 1,000+ transactions daily would hit rate limits quickly. Batch processing (up to 50 elements per request) and webhook-based approaches are necessary.

4.3 Architecture Recommendations

• Implement aggressive caching: Store Xero data in Base44's PostgreSQL database, refresh only changed records
• Use webhooks instead of polling: Xero webhooks provide real-time notifications without API consumption
• Batch operations: Group multiple records into single API calls where possible
• Monitor rate limit headers: X-DayLimit-Remaining, X-MinLimit-Remaining for proactive throttling

Chapter 5: Industry Benchmarks and ROI Analysis

5.1 AI Adoption in Accounting Firms

According to the Karbon State of AI in Accounting Report 2026:

• 98% of firms now use AI (up from 85% in 2025)
• Average time saved: 18 hours per employee per month
• Additional capacity with training: 7 weeks per employee per year
• Data security concerns: 83% of firms (up significantly from 2025)

CPA Australia's Business Technology Report 2025 found AI adoption jumped from 69% to 89% year-on-year, with 71% of Australian businesses planning further AI integration by 2026.

5.2 Productivity Benchmarks

The Smithink "Crunch" Accounting Industry Benchmark Report 2025 reveals:

• High-performing firms succeed through stronger productivity and higher revenue per person rather than scale
• Target utilization rates: 65-85% billable per individual, ~60% firm-wide average
• Workforce challenge: Retirements outpacing new entrants creating long-term capacity gaps

This benchmark context makes the 18 hours/month AI savings particularly significant—equivalent to approximately 11% additional capacity per employee.

5.3 ROI Calculation for Base44 Implementation

Scenario: WIP analysis dashboard for 20-person firm

	Cost	Benefit
Platform	Base44 Pro $50/month	Analysis time saved 20h/month
Development	40 hours (one-time)	Better decisions, reduced bad debt
Maintenance	5 hours/month	18h saved/employee/month (Karbon 2025)
Year 1 Total	~$600 + 100 hours	~240 hours + business optimization

At $150/hour average billing rate, 240 hours saved = $36,000 annual value against $600 platform cost — 60:1 return.

5.4 Pricing Benchmarks

Ignition's Tax and Compliance Pricing Benchmarks 2025 (165 Australian firms):

• 80% plan to raise fees in 2025
• Share charging over $300 for individual returns jumped from 16% to 26%

This pricing environment supports investment in productivity tools like Base44, as firms can pass efficiency gains through to pricing competitiveness or capacity expansion.

Chapter 6: Platform Risk Assessment

6.1 Platform Maturity and Governance

Acquisition Status: Base44 was acquired by Wix for ~$80 million (June 2025). While this provides financial stability, it also introduces uncertainty about long-term product direction and enterprise feature prioritization.

Enterprise Features Gap:

• No documented RBAC (Role-Based Access Control) capabilities
• Unclear audit logging and compliance reporting
• Limited export/migration options (data lock-in risk)
• No enterprise SSO (Single Sign-On) support

Skywork.ai Review Summary: "A promising accelerator for teams prioritising speed and iteration, not yet a universal replacement for mature no-code stacks in enterprise-grade workflows."

6.2 Security Risk Matrix

Risk Factor	Status	Mitigation
SOC 2 Type II	Not certified	Vendor security assessment
ISO 27001	Not certified	Request documentation
Penetration testing	Unknown	Assume limited
Bug bounty	Unknown	No public program
July 2025 incident	Patched in 24h	Monitor advisories
Encryption at rest	Presumed (Wix)	Verify in contract
Encryption in transit	HTTPS	Standard

6.3 Vendor Lock-in Risk

Base44 applications cannot be easily exported to other platforms. The generated code is proprietary and tightly coupled to Base44's runtime environment. This presents significant risk for accounting firms building critical workflows, as migration would require complete redevelopment.

Mitigation Strategy:

• Treat Base44 apps as temporary prototypes or non-critical tools
• Maintain original data sources (Xero, CSV files) as system of record
• Document business logic for potential future rebuild

Chapter 7: Implementation and Final Assessment

7.1 Recommended Trial Path

Phase 1: Validation (1-2 days, Free tier)

Build simple expense form to test generation speed and quality, test code readability, measure credits consumption.

Phase 2: Core Scenario Development (1-2 weeks)

Choose best scenario: Chinese bank clients → S2 CSV Converter; many projects → S5 WIP Dashboard; slow onboarding → S6 Onboarding System.

Phase 3: Iteration

If successful, expand to other scenarios; if not, analyze reasons and evaluate alternatives.

7.2 Compliance Checklist

Before deploying any Base44 application handling client data:

• Conduct Privacy Impact Assessment (following OAIC 10-step process)
• Obtain client consent for cloud storage (per TPB requirements)
• Update privacy policy to disclose Base44/Wix as subprocessors
• Document data flow and retention policies
• Implement access controls and audit logging (within Base44 capabilities)
• Establish backup and disaster recovery procedures

7.3 Do's and Don'ts

Don't	Do
Connect Xero write operations first	Start with read-only apps
Build complex multi-level approvals	Validate on Free tier first
Replace core accounting systems	Keep original data backups
Handle sensitive data without review	Conduct PIA before deployment
Expect 100% AI, no human review	Plan for manual QA cycles

7.4 Overall Ratings

Dimension	Rating	Notes
Internal Tools	5/5	CSV, WIP dashboards, onboarding
Core Financial	2/5	Dual invoicing, write-back
Learning Curve	4/5	Easier than Bubble
Maintainability	3/5	Prototype code, needs skills
Value	4/5	Free start, low cost
Compliance Readiness	2/5	No SOC 2, no ISO 27001
Enterprise Governance	2/5	Limited RBAC, audit, export
Ecosystem	3/5	Small but growing fast

7.5 Ideal User Profile

Best Fit: 10-50 person accounting firms, 1-2 people with basic technical skills, clear internal tool needs, established data governance practices, willing to accept compliance risks for productivity gains.

Not Recommended: Fully non-technical teams without learning time; users expecting "zero maintenance"; large firms needing enterprise compliance and SLA; firms handling sensitive client data without security assessment resources.

7.6 Strategic Recommendation

Base44 is an internal tool accelerator, not a universal solution. The 60:1 ROI potential for WIP dashboards and similar tools is compelling, but must be weighed against:

1. Compliance risk of handling client data on an uncertified platform
2. Vendor lock-in limiting future migration options
3. Security maturity gaps relative to enterprise requirements

Recommended Approach:

• Use Base44 for internal productivity tools only (S2, S5)
• Avoid client-facing applications or core financial workflows (S4, S1 write-back)
• Conduct formal security assessment before any production deployment
• Plan for potential platform migration within 2-3 years as requirements mature

References

CA ANZ Official Guidance

1. CA ANZ. AI Fluency Playbook. CA ANZ, 2025-08. https://www.charteredaccountantsanz.com/news-and-analysis/news/ca-anz-launches-ai-fluency-playbook
2. Chartered Accountants Worldwide / Ipsos UK. AI and the Future of the Global Chartered Accounting Profession. CAW, 2025. https://www.charteredaccountantsanz.com/news-and-analysis/media-centre/press-releases/a-profession-poised-for-ai-transformation-demands-upskilling-and-leadership
3. CA ANZ / Deloitte. Accelerating Reporting with Technology for a More Productive Australia. CA ANZ, 2025-08. https://www.charteredaccountantsanz.com/news-and-analysis/insights/research-and-insights/accelerating-reporting-with-technology-for-a-more-productive-australia
4. CA ANZ / ACCA. Ethics for Sustainable AI Adoption: Connecting AI and ESG. CA ANZ, 2021. https://www.charteredaccountantsanz.com/tools-and-resources/practice-management/ethics-in-practice/ethics-for-sustainable-ai-adoption

Privacy and Regulatory Framework

5. New Zealand Government. Privacy Act 2020 (No 31, Public Act). 2020-12-01. https://www.legislation.govt.nz/act/public/2020/0031/latest/LMS23223.html
6. NZ Privacy Commissioner. Sending Information Overseas. https://www.privacy.org.nz/responsibilities/disclosing-personal-information-outside-new-zealand/
7. NZ Privacy Commissioner. Microsoft Azure Privacy Impact Assessment. https://www.privacy.org.nz/about-us/microsoft-azure-privacy-impact-assessment/
8. OAIC. Australian Privacy Principles Guidelines (Updated October 2025). https://www.oaic.gov.au/privacy/australian-privacy-principles/australian-privacy-principles-guidelines
9. OAIC. Guidance on Privacy and the Use of Commercially Available AI Products. OAIC, 2025. https://www.oaic.gov.au/privacy/privacy-guidance-for-organisations-and-government-agencies/guidance-on-privacy-and-the-use-of-commercially-available-ai-products
10. OAIC. Guide to Undertaking Privacy Impact Assessments. https://www.oaic.gov.au/privacy/privacy-guidance-for-organisations-and-government-agencies/privacy-impact-assessments/guide-to-undertaking-privacy-impact-assessments
11. Tax Practitioners Board. TPB(PN) 1/2017 — Cloud Computing and the Code of Professional Conduct. TPB, 2017. https://www.tpb.gov.au/tpbpn-012017-cloud-computing-and-code-professional-conduct

Industry Benchmarks

12. Karbon. State of AI in Accounting Report 2026. Karbon HQ, 2026-01. https://karbonhq.com/resources/ebooks/state-of-ai-accounting-report-2026/
13. Karbon. State of AI in Accounting Report 2025. Karbon HQ, 2025-02. https://karbonhq.com/resources/ebooks/state-of-ai-accounting-report-2025/
14. CPA Australia. Business Technology Report 2025. CPA Australia, 2025. https://www.cpaaustralia.com.au/-/media/project/cpa/corporate/documents/tools-and-resources/business-management/business-management-research/business-technology-report-2025.pdf
15. Smithink / The Benchmarking Group. The Crunch: Australian Accounting Firm Benchmark Report 2025. Smithink, 2025. https://smithink.com/the-crunch/
16. Ignition. Tax and Compliance Pricing Benchmarks 2025. Ignition, 2025-05. https://www.ignitionapp.com/au/2025-tax-compliance-pricing-benchmark

Technical Documentation

17. Xero Developer. OAuth 2.0 API Limits. https://developer.xero.com/documentation/guides/oauth2/limits/
18. Xero Developer. Rate Limits Best Practices. https://developer.xero.com/documentation/best-practices/api-call-efficiencies/rate-limits
19. Xero. State of the Industry 2024: Leveraging the App Advantage. Xero, 2024. https://assets.ctfassets.net/8y4on51kf6pi/3rbnPD3TaIw0ZAP9RYOgDF/20d9d1f01340a1a990a78aed45ff34ed/XERO_Leveraging_the_app_advantage_report_SOTI_24.pdf

Platform Reviews

20. Mallett, G. Base44 Review: How Good Is the Vibe Coding Platform? Tech.co, 2026-02-17. https://tech.co/ai/vibe-coding/base44-review
21. Skywork.ai. Base44 Review (2025): AI No-Code Builder Tested and Compared. https://skywork.ai/blog/base44-review-ai-no-code-builder-2025/
22. Product Hunt. Base44 — Reviews. 4.4/5 based on 31 reviews. https://www.producthunt.com/products/base44
23. Wiz Research. Security Disclosure: Base44 Authentication Bypass Vulnerability. 2025-07. Original report not publicly available; patched within 24 hours with no confirmed exploitation.

Research Date: March 5, 2026 | Methodology: PAID + RISE Framework | Sources: 36 verified AU/NZ industry references