Hi there just wondering if you can help regarding the password complexity
In my created app, users can enter any password they are not prompted to enter strong password. how to overcome this
Haitham AlShatta About 3 hours ago
Feature Request
Hi there just wondering if you can help regarding the password complexity
In my created app, users can enter any password they are not prompted to enter strong password. how to overcome this
Haitham AlShatta About 3 hours ago
Feature Request
.Hello, I would like to share some feedback regarding the Starter plan and monetization security. I recently discovered that important security features (like server-side logic and secure watermarking) are not included in the Starter plan. Unfortunately, this was not clearly highlighted when choosing the plan. For an app with monetization, this is a critical point. Without backend protection, it is possible to bypass limitations or access non-protected images, which directly impacts revenue. I have already paid for the Starter plan, and I only realized these limitations after testing with real users. Some of them were even able to bypass the system, which is obviously a concern. From a commercial point of view, I believe this kind of limitation should be clearly emphasized upfront. Transparency builds trust. That’s why I would like to ask if it would be possible to benefit from a temporary access (for example 1 month) to the Builder plan, in order to properly test my application with full security. This would allow me to validate my business model in real conditions, and I would very likely upgrade afterwards if everything works as expected. Thank you in advance for your understanding and support.
DOMINIQUE PENET About 3 hours ago
Feature Request
.Hello, I would like to share some feedback regarding the Starter plan and monetization security. I recently discovered that important security features (like server-side logic and secure watermarking) are not included in the Starter plan. Unfortunately, this was not clearly highlighted when choosing the plan. For an app with monetization, this is a critical point. Without backend protection, it is possible to bypass limitations or access non-protected images, which directly impacts revenue. I have already paid for the Starter plan, and I only realized these limitations after testing with real users. Some of them were even able to bypass the system, which is obviously a concern. From a commercial point of view, I believe this kind of limitation should be clearly emphasized upfront. Transparency builds trust. That’s why I would like to ask if it would be possible to benefit from a temporary access (for example 1 month) to the Builder plan, in order to properly test my application with full security. This would allow me to validate my business model in real conditions, and I would very likely upgrade afterwards if everything works as expected. Thank you in advance for your understanding and support.
DOMINIQUE PENET About 3 hours ago
Feature Request
Feature Request: Exportable Granular Usage Logs (CSV/JSON) for Credit Auditing
As a user building professional solutions on Base44, I need better visibility into how credits are being consumed. Currently, tracking usage message-by-message is time-consuming and doesn't allow for a high-level audit of automated tasks or API calls. I am requesting an "Export Logs" feature that provides: Timestamped activity: Exactly when credits were deducted. Context/Endpoint: Whether it was a Manual Chat, an AI Agent, or an Automation. Cost breakdown: The specific amount of credits used per event. Error Tracking: Identifying if credits were consumed by failed requests or retries. Why this is important: Without granular logs, it’s difficult to optimize workflows or justify scaling the platform for larger projects. Transparency in billing builds trust and helps us build more efficient apps.
adi mazzawi About 4 hours ago
Feature Request
Feature Request: Exportable Granular Usage Logs (CSV/JSON) for Credit Auditing
As a user building professional solutions on Base44, I need better visibility into how credits are being consumed. Currently, tracking usage message-by-message is time-consuming and doesn't allow for a high-level audit of automated tasks or API calls. I am requesting an "Export Logs" feature that provides: Timestamped activity: Exactly when credits were deducted. Context/Endpoint: Whether it was a Manual Chat, an AI Agent, or an Automation. Cost breakdown: The specific amount of credits used per event. Error Tracking: Identifying if credits were consumed by failed requests or retries. Why this is important: Without granular logs, it’s difficult to optimize workflows or justify scaling the platform for larger projects. Transparency in billing builds trust and helps us build more efficient apps.
adi mazzawi About 4 hours ago
Feature Request
iCloud
You should integrate iOS, iCloud in terms of files emails and shortcuts. This way we have so much more options
Rafi About 4 hours ago
🔌 Integrations
iCloud
You should integrate iOS, iCloud in terms of files emails and shortcuts. This way we have so much more options
Rafi About 4 hours ago
🔌 Integrations
SuperAgent accessibility limitation on Telegram
Hi team, I created a SuperAgent chat bot on Telegram for my client’s users to chat with his bot but the bot is only accessible to me. Can you give an ETA for this feature to be released?
sarah rolland About 4 hours ago
Feature Request
SuperAgent accessibility limitation on Telegram
Hi team, I created a SuperAgent chat bot on Telegram for my client’s users to chat with his bot but the bot is only accessible to me. Can you give an ETA for this feature to be released?
sarah rolland About 4 hours ago
Feature Request
Old, failed apps EVERYONE HAS IS
You should get 80% of credits back when you delete an app that disintegrates work cause I bet everyone had a failed app and waisted soooooo many credits on it
Rafi About 4 hours ago
Feature Request
Old, failed apps EVERYONE HAS IS
You should get 80% of credits back when you delete an app that disintegrates work cause I bet everyone had a failed app and waisted soooooo many credits on it
Rafi About 4 hours ago
Feature Request
Adsense permission
I am trying to incorporate AdSense into my ad to Make revenue to pay for the service of my app. I was able to add it in just fine to the code but once I tried putting it out on Google Play I need this “com.google.android.gms.permission.AD_ID” And I'm getting told that I can't put it in and now I'm told base 44 can't put it in and I have to go in here and put it out here. If I can add AdSense into the code there's no reason why this should not be an option to fix as well. If I can build an app through the service in the option to download the files for Google and iOS then we need to make sure that everything can work with the Play store and Apple store.
Jonathan Hurrell About 5 hours ago
Feature Request
Adsense permission
I am trying to incorporate AdSense into my ad to Make revenue to pay for the service of my app. I was able to add it in just fine to the code but once I tried putting it out on Google Play I need this “com.google.android.gms.permission.AD_ID” And I'm getting told that I can't put it in and now I'm told base 44 can't put it in and I have to go in here and put it out here. If I can add AdSense into the code there's no reason why this should not be an option to fix as well. If I can build an app through the service in the option to download the files for Google and iOS then we need to make sure that everything can work with the Play store and Apple store.
Jonathan Hurrell About 5 hours ago
Feature Request
Private App User Approval Confusion
Hi Base44. Would it be possible for private apps to not require admin user approval. Perhaps have a per app setting that enables/disables the need to approve user requests. Although a good idea it is confusing to new users. They signup, get told an email will come confirming, but most don’t read it and try to sign in straight away which then gives them an invalid user or password error (because they have not been approved yet). Alternatively, can a better message be sent on sign in screen that indicates they have not yet been approved to access app yet and try later, rather than the current confusing message. Your consideration would be appreciated.
KennyG About 7 hours ago
Feature Request
Private App User Approval Confusion
Hi Base44. Would it be possible for private apps to not require admin user approval. Perhaps have a per app setting that enables/disables the need to approve user requests. Although a good idea it is confusing to new users. They signup, get told an email will come confirming, but most don’t read it and try to sign in straight away which then gives them an invalid user or password error (because they have not been approved yet). Alternatively, can a better message be sent on sign in screen that indicates they have not yet been approved to access app yet and try later, rather than the current confusing message. Your consideration would be appreciated.
KennyG About 7 hours ago
Feature Request
Foolproof approvals
auto-bake default dark mode toggle + privacy policy template/link in every build—for foolproof approvals
Jason Bulsa About 9 hours ago
Feature Request
Foolproof approvals
auto-bake default dark mode toggle + privacy policy template/link in every build—for foolproof approvals
Jason Bulsa About 9 hours ago
Feature Request
llms.txt
This is what was suggested by base44 support to ask for regarding llms.txt . You're absolutely right that llms.txt is an important and growing standard, especially as AI crawlers become a bigger source of traffic and visibility. The Base44 AI gave you accurate advice — this genuinely does need a platform-level fix, not something that can be patched with code in your app. Here's what I'd suggest: Submit a feature request at feedback.base44.com — specifically request that Base44 map /llms.txt as a platform-served file, similar to how /robots.txt and /sitemap.xml are handled. This is the only path to getting it properly implemented. Can you make this happen so that llms.txt is handled similar to how /robots.txt is handled?
Dean Yaukey About 15 hours ago
Feature Request
llms.txt
This is what was suggested by base44 support to ask for regarding llms.txt . You're absolutely right that llms.txt is an important and growing standard, especially as AI crawlers become a bigger source of traffic and visibility. The Base44 AI gave you accurate advice — this genuinely does need a platform-level fix, not something that can be patched with code in your app. Here's what I'd suggest: Submit a feature request at feedback.base44.com — specifically request that Base44 map /llms.txt as a platform-served file, similar to how /robots.txt and /sitemap.xml are handled. This is the only path to getting it properly implemented. Can you make this happen so that llms.txt is handled similar to how /robots.txt is handled?
Dean Yaukey About 15 hours ago
Feature Request
Custom-branded OAuth callback/auth domain (no base44 shown)
We use Base44 Google auth with custom OAuth Client ID/Secret, but the callback still routes through https://app.base44.com/api/apps/auth/callback, so users see “continue to base44.com” in Google sign-in. Please add support for a custom-branded auth domain / callback URL (e.g., https://auth.objectionpilot.com/...) so consent and redirects show our domain instead of Base44.
Karam Homsi About 17 hours ago
Feature Request
Custom-branded OAuth callback/auth domain (no base44 shown)
We use Base44 Google auth with custom OAuth Client ID/Secret, but the callback still routes through https://app.base44.com/api/apps/auth/callback, so users see “continue to base44.com” in Google sign-in. Please add support for a custom-branded auth domain / callback URL (e.g., https://auth.objectionpilot.com/...) so consent and redirects show our domain instead of Base44.
Karam Homsi About 17 hours ago
Feature Request
Post-OAuth redirect failing on iOS.
Fix the deep link redirect for iOS apps being required for custom native app configuration (registering a URL scheme or using Universal Links), which isn't currently configurable in Base44's mobile app generation. This is a platform-level limitation of the current mobile wrapper.
Francisco Masjuan About 18 hours ago
Feature Request
Post-OAuth redirect failing on iOS.
Fix the deep link redirect for iOS apps being required for custom native app configuration (registering a URL scheme or using Universal Links), which isn't currently configurable in Base44's mobile app generation. This is a platform-level limitation of the current mobile wrapper.
Francisco Masjuan About 18 hours ago
Feature Request
Full White-Label Control for Transactional Emails (Remove All Base44 Template Elements & Links)
Currently, even after setting up a custom email domain, transactional emails (such as email verification and password resets) still include Base44-controlled template elements. Specifically: A header section (e.g., “Reset your password”) remains in the email That header is clickable and links to Base44 This creates unintended external navigation and breaks the white-label experience This means that while visible branding like logos and sender domains can be customized, the email is not fully white-labeled. This causes credibility risks within our apps. Requested functionality: Ability to fully remove or disable all Base44 template elements Option for plain-text email format Guarantee that no external Base44 links are included in transactional emails This is essential for teams building customer-facing applications that require a fully branded and trusted experience.
E-mo About 20 hours ago
Feature Request
Full White-Label Control for Transactional Emails (Remove All Base44 Template Elements & Links)
Currently, even after setting up a custom email domain, transactional emails (such as email verification and password resets) still include Base44-controlled template elements. Specifically: A header section (e.g., “Reset your password”) remains in the email That header is clickable and links to Base44 This creates unintended external navigation and breaks the white-label experience This means that while visible branding like logos and sender domains can be customized, the email is not fully white-labeled. This causes credibility risks within our apps. Requested functionality: Ability to fully remove or disable all Base44 template elements Option for plain-text email format Guarantee that no external Base44 links are included in transactional emails This is essential for teams building customer-facing applications that require a fully branded and trusted experience.
E-mo About 20 hours ago
Feature Request
Is Base44 down?
all of my apps stopped working. When I’m trying to fix it I see this is not a code problem but a connection issue. Nothing has changed on my end and it seems that all of my apps are currently not working
Nil Doron About 22 hours ago
Feature Request
Is Base44 down?
all of my apps stopped working. When I’m trying to fix it I see this is not a code problem but a connection issue. Nothing has changed on my end and it seems that all of my apps are currently not working
Nil Doron About 22 hours ago
Feature Request
Title: AI coding agent should warn that Core.SendEmail doesn't support external email addresses Message: The AI coding agent repeatedly guided me to implement Core.SendEmail to send emails to external recipients, without ever warning me that this function is restricted to users registered within the app. As a result, I wasted a significant number of credits trying to make something work that was simply impossible. Request: The AI agent should systematically inform users of this limitation as soon as it detects a use case involving external recipients, and immediately suggest the appropriate alternative (e.g. Resend). This would prevent unnecessary credit loss and frustration for users.
Title: AI coding agent should warn that Core.SendEmail doesn't support external email addresses Message: The AI coding agent repeatedly guided me to implement Core.SendEmail to send emails to external recipients, without ever warning me that this function is restricted to users registered within the app. As a result, I wasted a significant number of credits trying to make something work that was simply impossible. Request: The AI agent should systematically inform users of this limitation as soon as it detects a use case involving external recipients, and immediately suggest the appropriate alternative (e.g. Resend). This would prevent unnecessary credit loss and frustration for users.
david grout About 22 hours ago
Feature Request
Title: AI coding agent should warn that Core.SendEmail doesn't support external email addresses Message: The AI coding agent repeatedly guided me to implement Core.SendEmail to send emails to external recipients, without ever warning me that this function is restricted to users registered within the app. As a result, I wasted a significant number of credits trying to make something work that was simply impossible. Request: The AI agent should systematically inform users of this limitation as soon as it detects a use case involving external recipients, and immediately suggest the appropriate alternative (e.g. Resend). This would prevent unnecessary credit loss and frustration for users.
Title: AI coding agent should warn that Core.SendEmail doesn't support external email addresses Message: The AI coding agent repeatedly guided me to implement Core.SendEmail to send emails to external recipients, without ever warning me that this function is restricted to users registered within the app. As a result, I wasted a significant number of credits trying to make something work that was simply impossible. Request: The AI agent should systematically inform users of this limitation as soon as it detects a use case involving external recipients, and immediately suggest the appropriate alternative (e.g. Resend). This would prevent unnecessary credit loss and frustration for users.
david grout About 22 hours ago
Feature Request
EU Data Residency Option – Critical for GDPR Compliance and Scaling in Europe
Hi Base44 team, We’re a big fan of your platform and actively building a SaaS app on it (an AI-powered sales tool that generates ready-to-send offers from meeting transcripts; it’s called Nimblo), which we plan to sell primarily in Europe (Germany, France, Benelux, Czechia, etc.). The issue: All data is stored exclusively in the US, creating significant GDPR barriers (Schrems II, Art. 44 transfers, CLOUD Act risks). Many potential EU B2B clients (especially those handling personal data like names, emails, call transcripts) reject it due to data sovereignty and DPIA requirements. My request: Add an option to choose EU/EEA data residency (AWS Frankfurt, Azure West Europe, Hetzner Germany, or similar) – e.g., a toggle when creating a project or in account settings. Ensure all databases, storage, auth, and processing stay fully within the EU (not partially). Bonus: Auto-generated DPA/SCCs, a residency badge in the dashboard, or a clear compliance indicator. This would unlock the entire European market – right now we have to turn away clients. I see similar requests (EU Data Residency for GDPR, We need EU-Hosting, Server hosting from the EU, etc.) with dozens/hundreds of votes and marked "In Review" – please add my project to the priority list and let us know if there's a planned timeline (2026/Q3?). Thanks a lot for considering this – European market could be a huge opportunity for Base44!
Neowara Solutions 1 day ago
Feature Request
EU Data Residency Option – Critical for GDPR Compliance and Scaling in Europe
Hi Base44 team, We’re a big fan of your platform and actively building a SaaS app on it (an AI-powered sales tool that generates ready-to-send offers from meeting transcripts; it’s called Nimblo), which we plan to sell primarily in Europe (Germany, France, Benelux, Czechia, etc.). The issue: All data is stored exclusively in the US, creating significant GDPR barriers (Schrems II, Art. 44 transfers, CLOUD Act risks). Many potential EU B2B clients (especially those handling personal data like names, emails, call transcripts) reject it due to data sovereignty and DPIA requirements. My request: Add an option to choose EU/EEA data residency (AWS Frankfurt, Azure West Europe, Hetzner Germany, or similar) – e.g., a toggle when creating a project or in account settings. Ensure all databases, storage, auth, and processing stay fully within the EU (not partially). Bonus: Auto-generated DPA/SCCs, a residency badge in the dashboard, or a clear compliance indicator. This would unlock the entire European market – right now we have to turn away clients. I see similar requests (EU Data Residency for GDPR, We need EU-Hosting, Server hosting from the EU, etc.) with dozens/hundreds of votes and marked "In Review" – please add my project to the priority list and let us know if there's a planned timeline (2026/Q3?). Thanks a lot for considering this – European market could be a huge opportunity for Base44!
Neowara Solutions 1 day ago
Feature Request
Lowest Monthly Plan for hosting
Can you actually create a paid plan for just 4 or 5 bucks a month, keeping the 25 credits limit per month without a daily limit? People don't mind paying a recurring monthly fee to host their app, and doesn't limit their prompts in a day, also keeping the base44 banner away. Please also add a top-up option for the credits. With these, the platform will really be an attractive investment for small businesses (self-employed individuals)
Viel Evasco 1 day ago
Feature Request
Lowest Monthly Plan for hosting
Can you actually create a paid plan for just 4 or 5 bucks a month, keeping the 25 credits limit per month without a daily limit? People don't mind paying a recurring monthly fee to host their app, and doesn't limit their prompts in a day, also keeping the base44 banner away. Please also add a top-up option for the credits. With these, the platform will really be an attractive investment for small businesses (self-employed individuals)
Viel Evasco 1 day ago
Feature Request
Critical: Manifest Access & AD_ID Compliance for Android
I am a developer currently trying to publish my app, Z…., on Google Play. I have encountered two critical blockers that cannot be resolved through the React code editor: AD_ID Permission Requirement: Google Play now requires the com.google.android.gms.permission.AD_ID permission to be explicitly declared in the AndroidManifest.xml. Since my app is flagged for using advertising/analytics IDs, I am getting a compliance warning. I need a way to add this permission to the native manifest. Version Code Control: I need manual control over the versionCode in the build.gradle. Currently, I cannot sync my Play Console releases with the automated increments provided by Base44. Deobfuscation (Mapping) Files: Google Play is flagging missing mapping files for R8/Proguard. This makes crash analysis (like the White Screen issues I'm facing) impossible to debug. Request: Please provide a "Native Configuration" section in the Publish dashboard or allow manual edits to the AndroidManifest.xml. As an "indiedev" building on your platform, these are essential requirements for app store compliance in 2026. I have already discussed this with support, and they suggested I flag this as a compliance requirement here for the engineering team to prioritize.
Ipek AG 1 day ago
Feature Request
Critical: Manifest Access & AD_ID Compliance for Android
I am a developer currently trying to publish my app, Z…., on Google Play. I have encountered two critical blockers that cannot be resolved through the React code editor: AD_ID Permission Requirement: Google Play now requires the com.google.android.gms.permission.AD_ID permission to be explicitly declared in the AndroidManifest.xml. Since my app is flagged for using advertising/analytics IDs, I am getting a compliance warning. I need a way to add this permission to the native manifest. Version Code Control: I need manual control over the versionCode in the build.gradle. Currently, I cannot sync my Play Console releases with the automated increments provided by Base44. Deobfuscation (Mapping) Files: Google Play is flagging missing mapping files for R8/Proguard. This makes crash analysis (like the White Screen issues I'm facing) impossible to debug. Request: Please provide a "Native Configuration" section in the Publish dashboard or allow manual edits to the AndroidManifest.xml. As an "indiedev" building on your platform, these are essential requirements for app store compliance in 2026. I have already discussed this with support, and they suggested I flag this as a compliance requirement here for the engineering team to prioritize.
Ipek AG 1 day ago
Feature Request