AI News

Base44 review: pricing, security, ownership, and production limits

Verdict: Base44 can turn a prompt into an interactive app quickly, but the recorded Kingy walkthrough does not establish security, scale, portability, reliability, or maintainability.

Disclosure: Kingy’s Base44 video hpFQlvRDcNA, published as client-video post 915351, is sponsored and disclosure-resolved through delivery 923813.

Evidence checked July 31, 2026; pricing and billing rechecked September 5, 2026. “Kingy-observed” below refers only to interactions visible in the existing Kingy recording. “Vendor-reported” means Base44 states the capability in its own documentation. Kingy did not run a new build, inspect generated code, load-test the service or audit its permissions during this update.

What Kingy observed

The recorded walkthrough shows Base44 turning prompts into interactive app screens and flows during one session. That supports a narrow claim: the service can help a user reach a working prototype quickly.

The recording does not test schema quality, authorization boundaries, concurrency, backup recovery, failure handling, accessibility, long-term maintenance or real production traffic.

Pricing snapshot

Base44’s annual-billing page listed Free at $0, Starter at $16 per month, Builder at $40, Pro at $80 and Elite at $160 at the September 5, 2026 check. These are vendor-reported annual-billing equivalents. Confirm tax, region, checkout, promotion, message credits and integration credits before choosing a plan.

Message credits and integration credits are separate monthly allowances. Exact usage varies by action and selected model; confirm the current checkout and allowance for the intended workload.

A managed backend, according to Base44

Base44 documents a managed database, file storage, authentication, backend functions, integrations, APIs and hosting. Its current backend documentation describes a MongoDB-compatible NoSQL data layer, row- and field-level authorization rules, Deno-based serverless functions and automatic HTTPS for hosted single-page applications.

Those are platform capabilities, not proof that every generated app configures them correctly. Base44’s own security guidance says builders are responsible for app security settings and should review permissions and run a security scan before publishing.

Security, data and ownership

Base44 says its platform supports encryption at rest and in transit, app-level permissions, row-level security, credential scanning, code and package checks, and enterprise controls. It also says it holds SOC 2 Type II and ISO 27001 certifications. Kingy has not reviewed the SOC 2 report or tested these controls.

Base44’s documentation makes the builder responsible for each app’s visibility, data-access rules and pre-publication security review. Platform controls do not guarantee that a generated app has the right permissions for its users or data.

Base44 says workspaces use US storage by default. Its documentation describes optional EU or UK data residency for some Elite and Enterprise workspaces, with rollout and processing-location caveats. Confirm the current region, subprocessors, retention, incident terms and data-processing agreement for the exact workload.

Base44 says the creator retains ownership of an app. Before treating that as portability, separately test code export, data export, user migration, external dependencies and the behavior of paid-only features after cancellation.

Tested and not tested

Area Evidence Classification What remains untested
Prompt-to-app workflow Existing Kingy recording Kingy-observed Fresh replay, reproducibility and generated-code review
Interactive UI and navigation Visible in the recording Kingy-observed Accessibility, device/browser coverage and error states
Database, auth, APIs, storage and functions Base44 documentation Vendor-reported Permission correctness, isolation, backup/restore and failures
Encryption and certifications Base44 security pages and trust center Vendor-reported; independent audits claimed Audit-report review, certificate scope and control effectiveness for the app
Production readiness No adequate evidence Not tested Load, uptime, observability, recovery, security and data governance
Portability GitHub and export capabilities are documented Vendor-reported Full code, data and user export outside Base44
Pricing and credits Public pricing and billing documentation Vendor-reported Credit burn for a defined workload, taxes and regional checkout

Production-readiness checklist

  • Permissions: verify app visibility, roles, row-level rules, and least-privilege access with test accounts.
  • Backup: document what is backed up, retention, restore scope, and who can initiate recovery.
  • Export: export code, data, users, and external dependencies, then test the artifacts outside Base44.
  • Observability: confirm logs, alerts, error reporting, usage visibility, and an incident owner.
  • Recovery: rehearse a failed deployment, credential rotation, data restore, and service handoff before critical use.

Who should consider it?

Base44 belongs on the shortlist for prototypes, internal workflows and early customer apps when a managed stack and fast iteration matter more than infrastructure control.

Before using it for sensitive data or a revenue-critical service, test permissions, failure paths, credit consumption, backups, data export, code export, monitoring and recovery. Review the generated app and its dependencies with someone qualified to own the production risk.

Related Kingy guides

Primary sources