Support & help
Base44 support — and what to do when it can't fix your app.
Base44's official support handles the platform: billing, accounts, connectors, and confirmed platform bugs. It explicitly does not debug your app's code. This page routes you the right way — check if Base44 is down, use official support for platform issues, or get an independent developer when your own app is broken.
Short answer
Base44 support runs through three official channels — a documentation AI, a Discord community, and support tickets — but it is scoped to the platform: billing, accounts, connectors, and confirmed platform bugs. Base44’s own docs state its support “does not provide hands-on debugging or fixes for your individual app code, prompts, or architecture.” So when your live app breaks, first check status.base44.com to rule out an outage. If Base44 is up, the fault is in your app — and that is what an independent Base44 developer fixes. Self-triage with the 60-minute guide, or get urgent help with a response inside two business hours on weekdays.
01 / First, split the problem
Is it Base44, or is it your app?
Almost every “base44 support” question is really one of three different problems with three different owners. Sort it before you spend an hour in the wrong queue.
Step 01 · 2 minutes
Is Base44 down?
Check status.base44.com. A platform-wide outage affects everyone — if there’s an active incident, the only fix is to wait.
Step 02 · platform issue
Billing / account / connector?
These are Base44’s job. Open an official support ticket — that is the fastest path for anything about the platform rather than your code.
Step 03 · your app
Errors, white screen, data loss?
If Base44 is up and it’s not billing, the fault is in your app’s own code or architecture — outside official support’s scope, and where an independent developer comes in.
02 / Official Base44 support
What Base44’s own support covers — and what it doesn’t.
Base44 offers real, responsive support — for the platform. Here are the official channels and what each is for, straight from Base44’s support docs.
| Channel | Best for | Where |
|---|---|---|
| Documentation AI | Instant how-to answers on building, integrations, setup, and troubleshooting. | “Ask a question” on any page of docs.base44.com |
| Discord community | Real-time help from the community and the Base44 team — and where Base44 sends app-building questions. | Base44 Discord (linked from their docs) |
| Support ticket | Billing, account, connectors, GitHub sync, and confirmed platform bugs. Include expected vs. actual behaviour, repro steps, links, and logs. | app.base44.com/support → New Ticket |
| abuse@base44.com | Appealing support access you believe was restricted by the spam policy in error. |
The limit that surprises people
Base44’s documentation is explicit that its support “does not provide hands-on debugging or fixes for your individual app code, prompts, or architecture.” It covers platform features, billing, connectors, and confirmed platform bugs — and points app-building questions to the Discord community or Base44 partners. That gap — a broken app that isn’t Base44’s fault to fix — is exactly the problem an independent developer solves.
03 / The support map
Every situation, and the one place to take it.
Match your situation to its real owner. Two of these belong to Base44; the rest are what we do.
| Situation | Who fixes it | Go to |
|---|---|---|
| Base44 itself is down / a platform-wide outage | Base44 — wait it out | status.base44.com → |
| Billing, account, connector, or GitHub-sync issue | Base44 official support | Open a support ticket → |
| Your app throws errors, white-screens, loses data, or login breaks | An independent Base44 developer | 60-minute triage → |
| Not sure whether to fix it yourself or hire | You, with a decision rubric | DIY-vs-hire guide → |
| Production emergency — revenue, auth, or data at risk | Urgent Base44 developer | Get urgent help → |
Prefer to browse fixes directly? The /fix index has documented playbooks with fixed pricing, and /audit scopes a one-engineer, one-day production review.
04 / Independent Base44 support
When your app is the problem, here’s the help — and how fast.
Free self-triage
Start with the 60-minute triage. About one in three issues resolves on the universal checks alone — no engagement needed.
Fix sprint
A single high-impact bug, fixed by one engineer. Sprints typically begin inside 48 hours and carry a money-back guarantee. See /fix for pricing.
Urgent, production-down
Payments down, auth broken, app unreachable? The urgent path responds inside two business hours during weekday working hours.
05 /FAQ
Frequently asked questions
Q.01Does Base44 have a support team?
Yes. Base44 offers support through three official channels: a documentation AI assistant (the “Ask a question” box on docs.base44.com), a Discord community with the team and other builders, and support tickets opened from app.base44.com/support. There is also abuse@base44.com for appealing restricted support access.
Q.02Will Base44 support fix my broken app?
No — and this catches a lot of founders off guard. Base44's own documentation states its support “does not provide hands-on debugging or fixes for your individual app code, prompts, or architecture.” Official support covers the platform itself — billing, accounts, connectors, and confirmed platform bugs — and directs app-level help to the Discord community or to Base44 partners. If the fault is in your app's code, you need an independent developer, not a support ticket.
Q.03How do I open a Base44 support ticket?
Go to your Base44 dashboard's support area (app.base44.com/support) and start a new ticket. Base44 asks you to include expected vs. actual behaviour, the steps to reproduce, any relevant links, and screenshots or logs. That detail speeds up triage on platform-side issues — but if the root cause is your own app code, the ticket will be categorised as out of scope.
Q.04How do I know if Base44 is down right now?
Check the official status page at status.base44.com first — it reports the builder, applications data, hosting, and login components. Independent monitors like IsDown and StatusGator track Base44 too. If there's an active incident, the fix is to wait; if the status page is clean, the problem is in your app, not the platform.
Q.05Base44 support won't help with my code — what are my options?
That's expected: app-level debugging is outside Base44's support scope by design. Three routes, cheapest first: run the free 60-minute triage at /base44-app-not-working, score whether the fix is DIY-able at /base44-debugging-help, or hand it to an independent Base44 developer — a fix sprint for a single high-impact bug, or the urgent path for a production emergency.
Q.06How fast can base44devs help in an emergency?
For genuine production emergencies — payments down, auth broken, app unreachable — the urgent path responds inside two business hours during weekday working hours. Diagnostic audits begin within one business day; bug-fix sprints typically begin inside 48 hours of payment. Fix sprints carry a money-back guarantee if the issue can't be resolved.
NEXT STEP
Base44 support can't touch your code. We can.
Official support is for the platform. When the fault is in your own app, get an independent Base44 developer on it — urgent response inside two business hours on weekdays, money-back on fix sprints.