Test the apps you build with Base44 before you publish
Base44 prompts a full-stack app to life, but generated code can hide records that never save and permissions that leak data. Run Kane CLI to verify your published Base44 app in a real browser, in plain English. Free to install.
or read the documentation
Why test apps built with Base44
Base44, now part of Wix, turns a prompt into a deployed full-stack app in minutes, with entities, auth, role-based access, and integrations like Invoke LLM, SendEmail, and Stripe. That speed is why generated code needs verifying.
The failures hide in data flows and permissions: a required field fails silently on save, Row Level Security leaks records across users, a workflow fires step one but not the follow-up, and the next prompt revives a fixed bug.
Kane CLI is that second pair of eyes. Describe the journey in plain English and it drives your live Base44 app in a real Chrome browser, clicks through, confirms data persists, and tells you where it breaks. Build, verify, ship.
What Kane CLI tests in your Base44 app
From a single entity save to a full role-gated, integration-driven journey, verified in a real browser.
Entities, CRUD, and persistence
Create, read, update, and delete records, then confirm they save to your Base44 entities and reappear on reload. Catch the silent save failures from a required field that never made it into the form.
Auth, roles, and permissions
Sign up and log in with OAuth, magic links, or passwords, then verify Admin, Staff, and Viewer see exactly what they should. Confirm Row Level Security scopes data per owner instead of leaking it or returning empty lists.
Built-in integrations
Walk the flows that lean on Base44 integrations: Invoke LLM responses, SendEmail confirmations, Stripe checkout and subscriptions, and connectors like Slack or Google Sheets. Verify each one fires, not just that the button exists.
Multi-step workflows
Base44 struggles most when one action has to trigger the next. Kane CLI walks the whole chain, so a workflow that works in isolation but never fires its follow-up steps gets caught before a user hits the dead end.
Published app, not the preview
Test the live published URL, not the builder preview. Surface the gap when the deployed app behaves differently, the backend is stuck in debug mode, or empty and error states render broken in a real browser.
Regression on the next edit
Base44's agent has a habit of breaking flows it already fixed. Lock in your known-good journeys and re-run them on every publish, so reintroduced bugs surface instantly instead of in production.
Build up confidence before you publish
Start in your terminal
Validate on the cloud
Release with confidence
Built for the prompt-to-published-app loop
Kane CLI and KaneAI share the same automation engine and dashboard.
From a generated app to a verified app
Base44 prompts the full-stack app into existence and publishes it. Kane CLI proves it works, closing the gap between a generated UI and a verified user journey before you press share.
Verify the live app, not the builder preview
Run Kane CLI against your published Base44 URL in a real Chrome browser to catch what the in-builder preview hides: a backend stuck in debug mode, an integration that never fires, permissions that leak data.
Evidence you can share
Every run produces a persistent video, a step trace, and a replay link you can drop into a bug report, a Base44 feedback ticket, or a team message to show exactly where the app broke.
Test your Base44 app in three steps
Install Kane CLI
Run npm install -g @testmuai/kane-cli and sign in with your TestMu AI account. Nothing to wire into your Base44 app, you just need its published URL.
Point your agent, or run it yourself
Run flows straight from your terminal against your live Base44 URL, or tell a coding agent like Cursor, Claude Code, Codex, or Gemini to drive Kane CLI as it iterates.
Describe the flow and verify
Write the journey in plain English, naming the entity that should update or the role that should be blocked. Kane CLI drives a real browser, verifies each step, and returns a pass or fail with evidence.
Get Started With Kane CLI
🎉 Launch offer: Bonus credits for the first 3 months on paid plans
Choose the right plan for you
Local test authoring via CLI
Auto-heal & vision
View test cases on UI
Test Manager
Free
$0
/month
200 Credits
Resets in every
30 days
Starter
$19
/month
2000 Credits
Launch: 4,000 Credits (+100%)
Bonus for first 3 months
Pro
$99
/month
10,000 Credits
Launch: 15,000 Credits (+50%)
Bonus for first 3 months
Enterprise
Get access to solutions built on Enterprise-Grade Security, Privacy, and Compliances.
Need more credits?
Got a bigger use case in mind?
Let’s talk
Choose the right plan for you
Free
$0
/month
200 Credits
Resets in every
30 days
Starter
$19
/month
2000 Credits
Launch: 4,000 Credits (+100%)
Bonus for first 3 months
Pro
$99
/month
10,000 Credits
Launch: 15,000 Credits (+50%)
Bonus for first 3 months
Enterprise
Get access to solutions built on Enterprise-Grade Security, Privacy, and Compliances.
Need more credits?
Got a bigger use case in mind?
Let’s talk
Get the technical rundown
Documentation
Everything you need to install, configure, and run Kane CLI in under 2 minutes.
Frequently asked questions
Install Kane CLI, then describe the journey in plain English, for example "open the published app, sign up, create a record, and confirm it shows on the dashboard and saves to the entity." Kane CLI drives your live Base44 app in a real Chrome browser, checks each step, and returns a pass or fail with video evidence. Run it yourself from the terminal, or point a coding agent like Cursor or Claude Code at it to verify alongside your build.
Base44 turns a prompt into a full-stack app with built-in entities, auth, and integrations, published to a live URL in minutes. That speed is exactly why testing matters. A required field missing from the form fails silently on save, entity permissions and Row Level Security can leak data or return empty lists, a Stripe or SendEmail integration can fail quietly, and the published app does not always match the builder preview. The next prompt often reintroduces bugs into flows that worked a minute ago. Kane CLI verifies the real published app in a browser so you ship what works.
End-to-end journeys against your published URL: sign-up and login with OAuth, magic links, or passwords, role-based access for Admin, Staff, and Viewer, CRUD on your entities, whether records persist and reappear, multi-step workflows that chain one action into the next, built-in integrations like Invoke LLM, SendEmail, and Stripe, empty and error states, broken links, and console errors. It checks each step, not just the final screen, and flags the exact point where the app breaks.
Yes. If you iterate on your Base44 app with a coding agent like Cursor, Claude Code, Codex, or Gemini, point it at the guide at testmuai.com/kane-cli/agents.md. It installs Kane CLI, runs flows against your live app with the --agent flag, reads the structured results, and fixes what failed before you see it. Base44 builds and publishes the app, Kane CLI verifies the running app in a real browser.
Yes. Authenticate with your TestMu AI credentials, pass --headless and --timeout, and gate your pipeline on the exit code: 0 on pass, 1 on fail, 2 on setup or auth errors, and 3 on timeout. Re-run your key flows every time you publish a new version, so a regression on the AI's next edit gets caught before users hit it.
The CLI is free to install and use. Local runs are free; cloud runs on the TestMu AI grid are billed against your TestMu AI plan. Start on the free tier and verify your published Base44 app end to end without a credit card.
Teach your agent to test what it builds
Point your AI coding agent at the Kane CLI guide and it installs, authenticates, and verifies your published Base44 app in a real browser on its own.
Point your agent to: testmuai.com/kane-cli/agents.md