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 has four ways in: a ticket at app.base44.com/support, the email address support@base44.com, the Base44 Discord, and the “Ask a question” AI on docs.base44.com. None of them is a phone line, and none carries a published response time (checked 13 September 2026). All four are scoped to the platform — 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, check status.base44.com first 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, see the decision rule for when your ticket goes unanswered, or get urgent help with a response inside two business hours on weekdays.
01 / Contact
How to contact Base44 support.
Base44 spreads its contact details across three subdomains: the channel list and the scope statement live on docs.base44.com, the email address on feedback.base44.com/contact, and the ticket portal on app.base44.com. Here they are in one table, checked 13 September 2026.
| Channel | Best for | Where |
|---|---|---|
| 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 |
| Support email | The address Base44 publishes as its contact point on the feedback hub. A ticket is still the better route for anything account-specific — it threads to your account and stays trackable under “My Support Tickets”. | support@base44.com |
| 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) |
| Status page | Checking before you write anything. Reports the builder, application preview, applications data, hosting, login, file uploads, file and image serving, and billing. | status.base44.com |
| abuse@base44.com | Appealing support access you believe was restricted by the spam policy in error. |
One habit to form before you use any of them: Base44’s docs ask you not to open a second ticket for an issue you have already reported, and to reply on the existing thread instead. Duplicated submissions are listed in its support Terms of Use among the behaviours that can get support access restricted — so the move that feels fastest is also the one that can cost you the channel.
02 / Phone, chat & hours
Is there a phone number, 24/7 line, or live chat?
No phone number appears on either of Base44’s documented contact surfaces — the support page in its documentation, or the contact page on its feedback hub (both checked 13 September 2026). Neither publishes a telephone line, a 24/7 desk, or stated support hours.
The closest things to live chat are the “Ask a question” AI at the bottom of every docs page — which answers from the documentation, not from your account — and the Discord server, where the team and other builders reply when they are around. Useful, both of them. Neither is a queue with a named person at the end of it.
One constraint worth knowing before you write: Base44’s docs state that while the platform and its AI chat run in several languages, its human support team operates in English only, and a ticket filed in another language may come back with a request to rewrite it.
If you came looking for a number because something is down right now, the honest substitute is an urgent Base44 developer with a two-business-hour response — a person, on your app, inside the working day. That is a different product from vendor support, and it is priced like one.
03 / Support scope
What Base44’s own support covers — and what it won’t touch.
Base44 offers real, responsive support — for the platform. Its docs draw the boundary themselves, in a “Support scope” section most people never read until a ticket comes back closed.
Base44’s job
- General guidance on how to use Base44 features
- Billing questions and account management
- Base44-offered connectors and GitHub sync — explicitly not third-party or open-source integrations
- Platform bugs and errors
- Workarounds or solutions to known issues
- Clarifying which part of an issue belongs to Base44 and which part belongs to an external system or your own implementation
Yours
- Debugging your app’s own code, whoever or whatever wrote it
- Fixing a prompt that keeps regenerating the wrong build
- Anything architectural — data model, auth flow, integration design
- Third-party and open-source integrations you wired up yourself
- Building the feature for you — the docs route that to Discord or a Base44 partner
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.
What happens when your ticket is categorised out of scope
Look again at the last line of Base44’s own in-scope list: it commits to clarifying which part of an issue belongs to Base44 and which part belongs to your implementation. That sentence decides most tickets. Support will tell you whose problem it is; it will not make yours go away. So a ticket that closes out of scope isn’t a queue problem — it is the wrong queue. One reproducible bug in your own code is a fixed-price fix sprint from $1500, scoped and quoted before any work starts, money-back if it can’t be resolved. If you can’t yet say what is broken — only that something is — a $497 production audit buys one engineer for one business day and returns a written list of what is actually wrong, refundable against fix work.
04 / Filing it well
Write a ticket Base44 can actually action.
Base44’s docs name the fields its team wants — the link to your app, what you expected, what actually happens, what you did immediately before it happened, steps to reproduce, and a screenshot or logs — and then describe them in prose. Here they are as something you can paste.
App URL: What I expected to happen: What actually happens instead: Steps to reproduce: 1. 2. 3. Last thing I changed before it broke: When it started (date + time, with timezone): How often (every time / intermittently / once): Browser + device: Attached: screenshot, console log, network log
Before you send it, Base44 asks you to try the cheap things first: search the docs for your exact error string, log out and back in or retry in an incognito window, check the changelog for a platform change dated near the day it broke, confirm your own network is stable, clear your browser cache and Base44 cookies, and — the one that saves the most time on both sides — reproduce the issue in a minimal test app. That last step is also a diagnosis. If the bug will not reproduce in a clean app, it is specific to yours, which is the same as saying it is outside what a ticket can fix.
Two rules from Base44’s own support terms are easy to trip over. First: one issue, one ticket. Add new information by replying on the existing thread — duplicated submissions are listed among the behaviours that can get support access restricted, and there is an appeal address (abuse@base44.com) precisely because it happens. Second: write it in English. The platform speaks several languages; the human support team, per the docs, does not. Everything you file stays trackable afterwards under “My Support Tickets” at app.base44.com/support/conversations.
And if the ticket comes back out of scope, the 47 documented fix playbooks with fixed pricing set out what each class of Base44 bug costs to resolve on our side of the line.
05 / When it goes quiet
If the ticket goes quiet: the escalation ladder.
Base44 publishes no response-time commitment. Its own support FAQ answers “Why has support not responded to my ticket yet?” with “Response times vary based on ticket volume and issue urgency” (checked 13 September 2026). That is an honest answer, and a useless one when your app is down. The long version of what to do next is the playbook on what to do when a Base44 support ticket goes unanswered. The short version is the ladder below — climb it in order, because each rung costs less than the one after it.
Rung 01
Reply on the ticket you already have
Add the thing you did not have when you filed it: a reproduction in a clean test app, a console error, a timestamp. Do not open a second ticket — Base44 asks you not to, and duplicate submissions sit in the Terms of Use list that can cost you support access entirely.
Rung 02
Rule the platform in or out
Check status.base44.com for an open incident on the component you are actually using — builder, hosting, login, data, file uploads and billing are reported separately — then the Base44 changelog for a platform change dated near the day it broke. If either lines up, say so on the ticket. A reproducible platform bug moves differently from an unexplained one.
Rung 03
Ask in Discord
Base44’s docs name Discord as the place for real-time help from the community and the team, and as where app-building questions get pointed. Someone has usually hit your error before. Fastest rung, least guaranteed.
Rung 04
Put it on the feedback board
feedback.base44.com is where Base44 collects bug reports and feature requests, with a public roadmap and changelog attached. A board post is visible and votable in a way a private ticket is not — which is the entire reason to use it.
Rung 05
If the channel itself is gone, appeal it
If tickets stop going through at all, Base44 documents abuse@base44.com for appealing support access you believe was restricted in error under its anti-spam policy. That is a different problem from a slow queue, and it has a different address.
The 72-hour stop rule
This one is ours, not Base44’s, and it is a rule of thumb rather than a measurement: once a ticket is 72 hours old and the issue is still blocking revenue, signups, or logins, treat the channel as failed and stop waiting on it. Waiting is only free when the app isn’t earning. At that point the cheapest next move is a $497 Base44 production audit — one engineer, one business day, a written report with reproduction steps you can act on or hand to anyone, and the fee comes off the fix if you go ahead with one. Another day of refreshing the ticket buys nothing you can act on.
06 / 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.
07 / 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 47 documented fix playbooks with fixed pricing cover the named failures, and a one-engineer, one-day production audit for $497 covers the ones you can’t name yet.
08 / 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. It runs the universal checks first — the ones that resolve a live app with no engagement and no invoice.
Fix sprint
A single high-impact bug, fixed by one engineer. Sprints typically begin inside 48 hours and carry a money-back guarantee — see a fix sprint from $1500. If the same class of thing keeps breaking, a reactive sprint is the wrong shape and an ongoing support retainer is the comparison to run.
Urgent, production-down
Payments down, auth broken, app unreachable? The urgent path responds inside two business hours during weekday working hours.
09 /FAQ
Base44 support FAQ
Q.01Does Base44 have a support team?
Yes. Base44 offers support through a ticket opened from app.base44.com/support, the email address support@base44.com that it lists on its feedback hub, a documentation AI assistant (the “Ask a question” box on docs.base44.com), and a Discord community with the team and other builders. There is also abuse@base44.com for appealing restricted support access.
Q.02What is Base44's support email address?
support@base44.com. Base44 publishes it as its contact address on feedback.base44.com/contact, alongside the help centre at app.base44.com/support/conversations and its Discord. For anything account-specific, the ticket portal is the route Base44's own documentation points you to, because the conversation threads to your account and stays trackable under “My Support Tickets”.
Q.03Does Base44 have a support phone number?
No phone number appears on either of Base44's documented contact surfaces — its support docs page or the contact page on its feedback hub (both checked 13 September 2026). The published routes are the ticket portal, support@base44.com, Discord, the Ask AI assistant in the docs, and abuse@base44.com for appealing restricted access. There is no published 24/7 line and no stated support hours, and Base44's docs note that its human support team operates in English only.
Q.04How long does Base44 support take to reply?
Base44 publishes no response-time commitment. Its own support FAQ answers “Why has support not responded to my ticket yet?” with “Response times vary based on ticket volume and issue urgency,” and asks you to reply on your existing ticket with new details rather than open a second one (checked 13 September 2026). That second part matters: duplicated support submissions are listed in Base44's support Terms of Use among the behaviours that can get support access restricted.
Q.05Will 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.06Base44 support said my issue is out of scope — what now?
That is the documented outcome, not a brush-off: hands-on debugging of your app's code, prompts, and architecture sits outside Base44's support scope by design. Two routes from there. If you can name the bug and reproduce it, it is a fixed-price fix sprint on your own code — from $1,500, money-back if it can't be resolved. If you can only say the app is wrong and not what is wrong, start with the $497 production audit: one engineer, one business day, a written list of what is actually broken, refundable against fix work.
Q.07How 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.08How 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.09Base44 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, and that policy is also why app-code tickets go quiet — the decision rule for when your ticket goes unanswered is at /fix/support-nonexistent-tickets-ignored. 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.10How 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 — fixed-price sprints with money-back if the bug can't be resolved, and a written audit first if you can't name it yet.