Credits being deleted at the end of month is a terrible business strategy. It devalues your product. It makes your company seem slimy.
markmcg 39 minutes ago
Feature Request
Credits being deleted at the end of month is a terrible business strategy. It devalues your product. It makes your company seem slimy.
markmcg 39 minutes ago
Feature Request
how many credits were earned in Superagent
I suggest adding transparency to how many credits were earned in Superagent for each action. Like there are 3 dots next to each of my prompts in the chat system where you can see how many credits were used.
עידו רושינק Ido Rosink About 3 hours ago
Feature Request
how many credits were earned in Superagent
I suggest adding transparency to how many credits were earned in Superagent for each action. Like there are 3 dots next to each of my prompts in the chat system where you can see how many credits were used.
עידו רושינק Ido Rosink About 3 hours ago
Feature Request
Push notifications
When will base44 support IOS and Android native push notifications? It is pointless to publish an app without it.
Adi Kraus About 3 hours ago
🔌 Integrations
Push notifications
When will base44 support IOS and Android native push notifications? It is pointless to publish an app without it.
Adi Kraus About 3 hours ago
🔌 Integrations
Greater Backend Control + Native Supabase Support for Production SaaS
We’ve been building a production SaaS platform on Base44 and overall the speed of development has been excellent. However, as we move closer to real-world deployment with multiple companies using the system, we’re encountering a few structural limitations that would benefit from deeper backend control. Key areas where additional functionality would significantly improve the platform: 1. Native Supabase Integration (Highly Needed for SaaS) For multi-tenant SaaS applications, Supabase provides mature features such as: Row Level Security (RLS) Auth management Database control Edge functions Direct support would allow developers to manage multi-company environments more reliably and securely. 2. Greater Backend Logic Control Currently many workflows rely on frontend-driven logic. In production SaaS systems we often need: Server-side functions Custom backend workflows Event-based triggers Validation that runs independently from the UI This helps ensure the system behaves correctly regardless of how the frontend is used. 3. Stronger Multi-Tenant Architecture Tools For SaaS platforms where multiple companies use the same application, developers need clearer control for: Company-level data isolation Authentication flows for new company owners vs invited team members RLS policies tied to company IDs Preventing cross-company data visibility 4. Auth Flow Flexibility Currently sign-up and access request flows are somewhat restrictive. It would help to allow: Custom onboarding flows Company creation during signup Admin approval logic customization Better handling of owner vs invited users Why this matters Base44 is extremely powerful for rapidly building SaaS products. With stronger backend and database control, it could also support more production-grade, enterprise SaaS systems, especially those using multi-tenant architectures. Would love to hear how others building SaaS on Base44 are handling these challenges as well. Thanks to the Base44 team for continuing to improve the platform.
aquo sync About 9 hours ago
🔌 Integrations
Greater Backend Control + Native Supabase Support for Production SaaS
We’ve been building a production SaaS platform on Base44 and overall the speed of development has been excellent. However, as we move closer to real-world deployment with multiple companies using the system, we’re encountering a few structural limitations that would benefit from deeper backend control. Key areas where additional functionality would significantly improve the platform: 1. Native Supabase Integration (Highly Needed for SaaS) For multi-tenant SaaS applications, Supabase provides mature features such as: Row Level Security (RLS) Auth management Database control Edge functions Direct support would allow developers to manage multi-company environments more reliably and securely. 2. Greater Backend Logic Control Currently many workflows rely on frontend-driven logic. In production SaaS systems we often need: Server-side functions Custom backend workflows Event-based triggers Validation that runs independently from the UI This helps ensure the system behaves correctly regardless of how the frontend is used. 3. Stronger Multi-Tenant Architecture Tools For SaaS platforms where multiple companies use the same application, developers need clearer control for: Company-level data isolation Authentication flows for new company owners vs invited team members RLS policies tied to company IDs Preventing cross-company data visibility 4. Auth Flow Flexibility Currently sign-up and access request flows are somewhat restrictive. It would help to allow: Custom onboarding flows Company creation during signup Admin approval logic customization Better handling of owner vs invited users Why this matters Base44 is extremely powerful for rapidly building SaaS products. With stronger backend and database control, it could also support more production-grade, enterprise SaaS systems, especially those using multi-tenant architectures. Would love to hear how others building SaaS on Base44 are handling these challenges as well. Thanks to the Base44 team for continuing to improve the platform.
aquo sync About 9 hours ago
🔌 Integrations
Please simplify the backend or add SUPABASE.
Hi team, please create data table like supabase with function to add foreign key to table and ensure the tables are categories as: auth, app entities, functions, security, logic. We as user need simple and more resilient backend here to edit, and update our backend so our app can work as we intend to, not as how AI models intends them to.
aquo sync About 9 hours ago
🔌 Integrations
Please simplify the backend or add SUPABASE.
Hi team, please create data table like supabase with function to add foreign key to table and ensure the tables are categories as: auth, app entities, functions, security, logic. We as user need simple and more resilient backend here to edit, and update our backend so our app can work as we intend to, not as how AI models intends them to.
aquo sync About 9 hours ago
🔌 Integrations
The Plan Price Page
Hi, I'm looking to purchase a plan and the plan options are highly deceiving. On the list of plans, it says $16/month, which is false advertising. The real price is $20/month, It's only $16 if I commit to one full year. I believe you should honor the price that you have on the plan page or put the real price and offer a discount, not the other way around. This certainly makes people second guess as the whether or not we should make a purchase. Would I be deceived when I need something else? App: PricePick (ID: 69a9fec54388a713fdf5aea4) App Link: https://app.base44.com/apps/69a9fec54388a713fdf5aea4/editor/preview 20:46 Hi Allyaz, Thanks for sharing this feedback — I completely understand where you're coming from, and it's a fair point to raise. To clarify what you're seeing: the $16/month price reflects the effective monthly cost when billed annually (yearly plan), while $20/month is the month-to-month price. This is a common pricing display practice — showing the lower per-month equivalent of an annual commitment — but you're right that it can feel misleading if it's not made crystal clear upfront. This is essentially the ~20% discount Base44 offers for committing to a yearly plan. So both prices are real — they just apply to different billing cycles: $20/month → billed monthly, cancel anytime $16/month → billed as ~$192 upfront for the full year Your feedback about making this distinction more obvious on the pricing page is genuinely valuable, and I'd encourage you to share it on the feedback board so the team sees it. That said, to directly answer your concern: you won't be deceived. The monthly plan at $20/month is straightforward with no hidden commitments, and the yearly plan saves you money if you're planning to stick around. Is there anything else I can help clarify about the plans before you decide? Happy to walk you through what's included in each tier! 20:46 That's not what's said on the plan page, only after I decide to purchase a plan. So, that's not straightforward. 20:47 You're absolutely right, and I appreciate you pushing back on that — if the pricing page shows $16/month without clearly indicating upfront that it's an annual commitment, that's a legitimate UX issue and your frustration is completely valid. I'd strongly encourage you to submit this as feedback directly so the product team can address how pricing is displayed: 👉 feedback.base44.com That said, to be transparent about how it works: $20/month = monthly billing, full flexibility $16/month = annual billing, paid upfront for the year Neither price is false — but the context should absolutely be visible before you click to purchase, not after. That's a fair expectation. Is there anything else I can help you with — whether it's choosing the right plan for your needs or anything else about PricePick? I'm happy to help!
Allyaz Stoned About 12 hours ago
Feature Request
The Plan Price Page
Hi, I'm looking to purchase a plan and the plan options are highly deceiving. On the list of plans, it says $16/month, which is false advertising. The real price is $20/month, It's only $16 if I commit to one full year. I believe you should honor the price that you have on the plan page or put the real price and offer a discount, not the other way around. This certainly makes people second guess as the whether or not we should make a purchase. Would I be deceived when I need something else? App: PricePick (ID: 69a9fec54388a713fdf5aea4) App Link: https://app.base44.com/apps/69a9fec54388a713fdf5aea4/editor/preview 20:46 Hi Allyaz, Thanks for sharing this feedback — I completely understand where you're coming from, and it's a fair point to raise. To clarify what you're seeing: the $16/month price reflects the effective monthly cost when billed annually (yearly plan), while $20/month is the month-to-month price. This is a common pricing display practice — showing the lower per-month equivalent of an annual commitment — but you're right that it can feel misleading if it's not made crystal clear upfront. This is essentially the ~20% discount Base44 offers for committing to a yearly plan. So both prices are real — they just apply to different billing cycles: $20/month → billed monthly, cancel anytime $16/month → billed as ~$192 upfront for the full year Your feedback about making this distinction more obvious on the pricing page is genuinely valuable, and I'd encourage you to share it on the feedback board so the team sees it. That said, to directly answer your concern: you won't be deceived. The monthly plan at $20/month is straightforward with no hidden commitments, and the yearly plan saves you money if you're planning to stick around. Is there anything else I can help clarify about the plans before you decide? Happy to walk you through what's included in each tier! 20:46 That's not what's said on the plan page, only after I decide to purchase a plan. So, that's not straightforward. 20:47 You're absolutely right, and I appreciate you pushing back on that — if the pricing page shows $16/month without clearly indicating upfront that it's an annual commitment, that's a legitimate UX issue and your frustration is completely valid. I'd strongly encourage you to submit this as feedback directly so the product team can address how pricing is displayed: 👉 feedback.base44.com That said, to be transparent about how it works: $20/month = monthly billing, full flexibility $16/month = annual billing, paid upfront for the year Neither price is false — but the context should absolutely be visible before you click to purchase, not after. That's a fair expectation. Is there anything else I can help you with — whether it's choosing the right plan for your needs or anything else about PricePick? I'm happy to help!
Allyaz Stoned About 12 hours ago
Feature Request
Razorpay Integration
Hello, I would like to share my experience while using Base44. The platform is very good and helpful, but I noticed one issue. Currently, Razorpay payment integration is not available. Since many users in India rely on Razorpay for online payments, it would be very useful if you could add Razorpay as a payment option. Many developers in India, including my friends, are using Base44, so this feature would make the platform even better for Indian users. Please consider adding Razorpay integration in a future update. I will be waiting for this feature. Thank you.
Suhail Suhail About 14 hours ago
Feature Request
Razorpay Integration
Hello, I would like to share my experience while using Base44. The platform is very good and helpful, but I noticed one issue. Currently, Razorpay payment integration is not available. Since many users in India rely on Razorpay for online payments, it would be very useful if you could add Razorpay as a payment option. Many developers in India, including my friends, are using Base44, so this feature would make the platform even better for Indian users. Please consider adding Razorpay integration in a future update. I will be waiting for this feature. Thank you.
Suhail Suhail About 14 hours ago
Feature Request
Android Capacitor: Native FCM push notifications support for closed/background app
Currently, FCM push notifications do not work when the app is closed or in background on Android, because the Capacitor wrapper does not include native FCM integration. The android/ folder is not exposed in the GitHub repo, so developers cannot add the required Firebase Messaging Service themselves. Please add native FCM support (background + closed app) to the Base44 Capacitor build pipeline for Play Store apps.
Antoine Leroux About 18 hours ago
Feature Request
Android Capacitor: Native FCM push notifications support for closed/background app
Currently, FCM push notifications do not work when the app is closed or in background on Android, because the Capacitor wrapper does not include native FCM integration. The android/ folder is not exposed in the GitHub repo, so developers cannot add the required Firebase Messaging Service themselves. Please add native FCM support (background + closed app) to the Base44 Capacitor build pipeline for Play Store apps.
Antoine Leroux About 18 hours ago
Feature Request
Android Capacitor: Add IMMERSIVE_STICKY fullscreen mode to Play Store build pipeline
When scrolling UP in a Capacitor-wrapped app installed from the Play Store, the Android WebView reveals a bottom Chrome bar showing the app's base44 URL. Scrolling DOWN works correctly fullscreen. This is the classic symptom of missing SYSTEM_UI_FLAG_IMMERSIVE_STICKY in MainActivity.java onResume(). Since android/ is not exposed in the GitHub repo, developers cannot fix this themselves. Please add immersive sticky mode natively to the Capacitor build pipeline for all Play Store apps.
Antoine Leroux About 18 hours ago
Feature Request
Android Capacitor: Add IMMERSIVE_STICKY fullscreen mode to Play Store build pipeline
When scrolling UP in a Capacitor-wrapped app installed from the Play Store, the Android WebView reveals a bottom Chrome bar showing the app's base44 URL. Scrolling DOWN works correctly fullscreen. This is the classic symptom of missing SYSTEM_UI_FLAG_IMMERSIVE_STICKY in MainActivity.java onResume(). Since android/ is not exposed in the GitHub repo, developers cannot fix this themselves. Please add immersive sticky mode natively to the Capacitor build pipeline for all Play Store apps.
Antoine Leroux About 18 hours ago
Feature Request
extended credit at base44
you must start giving extend credits like 25, 50 credits if we need at a cost till expiry. this will create additional revenue for base44 and ease our problem too
fmwgroupapp-byte About 18 hours ago
Feature Request
extended credit at base44
you must start giving extend credits like 25, 50 credits if we need at a cost till expiry. this will create additional revenue for base44 and ease our problem too
fmwgroupapp-byte About 18 hours ago
Feature Request
Its the Third time that Google Ads stop my advertizing telling me that the website is infected.
Hello everyone please let me know if there is a solution to it???
Kakoon About 18 hours ago
Feature Request
Its the Third time that Google Ads stop my advertizing telling me that the website is infected.
Hello everyone please let me know if there is a solution to it???
Kakoon About 18 hours ago
Feature Request
EMAIL BRANDING
Hello, branding, such as updating the sender name, email domain, and button text (for example changing “Access app” to “Enter My Company Name”). Everything else in the on boarding flow is working well, so I would prefer not to change
Samuel Strong About 20 hours ago
Feature Request
EMAIL BRANDING
Hello, branding, such as updating the sender name, email domain, and button text (for example changing “Access app” to “Enter My Company Name”). Everything else in the on boarding flow is working well, so I would prefer not to change
Samuel Strong About 20 hours ago
Feature Request
il faut pouvoir traduire l'interface d'autheentification de bas44 par mail et mot de passe, car on est beaucoup de francais a utiliser bas44 et c'est une limitation importante merci de travailler sur cette possibilité ou de fournir une API qui nous permettrai de personnaliser la page d'authentification tout en utilisant le serveur base44 cordialemnt
Morgan Pate pires About 20 hours ago
Feature Request
il faut pouvoir traduire l'interface d'autheentification de bas44 par mail et mot de passe, car on est beaucoup de francais a utiliser bas44 et c'est une limitation importante merci de travailler sur cette possibilité ou de fournir une API qui nous permettrai de personnaliser la page d'authentification tout en utilisant le serveur base44 cordialemnt
Morgan Pate pires About 20 hours ago
Feature Request
Feature Request: Project Organization / Status Management
As a user managing multiple applications in Base44, the current Apps dashboard becomes difficult to manage once the number of projects grows. At the moment, all projects appear in a single flat list. This makes it harder to quickly understand the status of each project or to keep development work organized. It would be extremely helpful if Base44 introduced a way to organize projects, for example: 1. Project Status Allow assigning a status to each project, such as: Draft / In Development Testing Production / Live Archived This would make it much easier to track which apps are still under development and which are already deployed. 2. Project Categories or Folders Allow grouping projects into categories or folders, for example: Client Projects Internal Tools Templates / Demos Archived Projects This would significantly improve usability for users managing many apps. 3. Optional Filters It would also be useful to filter the Apps dashboard by: Status Category Owner / Workspace This feature would make the Base44 dashboard much more scalable for developers and agencies working with many projects.
M. D. Akk About 21 hours ago
Feature Request
Feature Request: Project Organization / Status Management
As a user managing multiple applications in Base44, the current Apps dashboard becomes difficult to manage once the number of projects grows. At the moment, all projects appear in a single flat list. This makes it harder to quickly understand the status of each project or to keep development work organized. It would be extremely helpful if Base44 introduced a way to organize projects, for example: 1. Project Status Allow assigning a status to each project, such as: Draft / In Development Testing Production / Live Archived This would make it much easier to track which apps are still under development and which are already deployed. 2. Project Categories or Folders Allow grouping projects into categories or folders, for example: Client Projects Internal Tools Templates / Demos Archived Projects This would significantly improve usability for users managing many apps. 3. Optional Filters It would also be useful to filter the Apps dashboard by: Status Category Owner / Workspace This feature would make the Base44 dashboard much more scalable for developers and agencies working with many projects.
M. D. Akk About 21 hours ago
Feature Request
Wildcard domain - Dominio curinga
A key function would be base44, which supports wildcard domains, and is especially useful in SaaS systems, catalogs, and multi-tenant environments. Uma função primordial seria o base44, suporta domínio curinga, principalmente sistemas saas, catálogos, multi tenent, usam muito a função.
Festeiros Brasil About 21 hours ago
Feature Request
Wildcard domain - Dominio curinga
A key function would be base44, which supports wildcard domains, and is especially useful in SaaS systems, catalogs, and multi-tenant environments. Uma função primordial seria o base44, suporta domínio curinga, principalmente sistemas saas, catálogos, multi tenent, usam muito a função.
Festeiros Brasil About 21 hours ago
Feature Request
Even when I upload an image and specify the same eyes or art style, the result turns out completely different. Even when I generate characters based on the image style, they end up with a different aesthetic and a different art style. The image analysis is weak. The art styles are all stiff. It tends to reuse the same backgrounds. I’d like to see improvements in image generation.
兵頭美希 1 day ago
Feature Request
Even when I upload an image and specify the same eyes or art style, the result turns out completely different. Even when I generate characters based on the image style, they end up with a different aesthetic and a different art style. The image analysis is weak. The art styles are all stiff. It tends to reuse the same backgrounds. I’d like to see improvements in image generation.
兵頭美希 1 day ago
Feature Request
Feature Request: Google Contacts Connector
It would be great to have a dedicated Google Contacts connector in Base44 that supports the contacts.readonly scope from the Google People API. Use case: Being able to search and retrieve contact information (e.g., names, emails, last contacted date) directly within Base44 apps — particularly useful for CRM-style applications. Why it's needed: The existing Gmail connector only covers email operations and doesn't support Google Contacts, which is a separate API ( people.googleapis.com ). There's currently no native way to connect to Google Contacts without building a custom backend function with your own OAuth credentials. Requested scope: contacts.readonly (read-only access to Google Contacts)
Eyal Rabinovich 1 day ago
Feature Request
Feature Request: Google Contacts Connector
It would be great to have a dedicated Google Contacts connector in Base44 that supports the contacts.readonly scope from the Google People API. Use case: Being able to search and retrieve contact information (e.g., names, emails, last contacted date) directly within Base44 apps — particularly useful for CRM-style applications. Why it's needed: The existing Gmail connector only covers email operations and doesn't support Google Contacts, which is a separate API ( people.googleapis.com ). There's currently no native way to connect to Google Contacts without building a custom backend function with your own OAuth credentials. Requested scope: contacts.readonly (read-only access to Google Contacts)
Eyal Rabinovich 1 day ago
Feature Request
Connect superagents to base44 platform
Hello, I’ve been using the new superagent and found out he can’t actually use the base44 platform... Hello, I’ve been using the new superagent and found out he can’t actually use the base44 platform, he can’t edit the apps and do QA, open new apps etc Those are very strong and important stuff that your platform agent should do… that way it can automate a lot of the tasks and make base44 a much better platform for app building, both power users and beginners. Maybe an api to share with the superagent I really hope you’d add this feature. I think it’s a must In the support words “Allow API key auth for the MCP server so Superagents and automated workflows can connect without an interactive OAuth flow “ Thanks in advance!
Shaked Hetzroni 1 day ago
Feature Request
Connect superagents to base44 platform
Hello, I’ve been using the new superagent and found out he can’t actually use the base44 platform... Hello, I’ve been using the new superagent and found out he can’t actually use the base44 platform, he can’t edit the apps and do QA, open new apps etc Those are very strong and important stuff that your platform agent should do… that way it can automate a lot of the tasks and make base44 a much better platform for app building, both power users and beginners. Maybe an api to share with the superagent I really hope you’d add this feature. I think it’s a must In the support words “Allow API key auth for the MCP server so Superagents and automated workflows can connect without an interactive OAuth flow “ Thanks in advance!
Shaked Hetzroni 1 day ago
Feature Request
RLS: {{user.tenant_id}} works but {{user.data.tenant_id}} does not - documentation clarification needed
We confirmed through live testing that {{user.tenant_id}} resolves correctly in RLS rules but {{user.data.tenant_id}} does not. Please clarify: is {{user.tenant_id}} officially supported? Can you add it to the documentation? Also, why does {{user.data.*}} not resolve for RLS despite being documented as supported?
mo himmy 1 day ago
Feature Request
RLS: {{user.tenant_id}} works but {{user.data.tenant_id}} does not - documentation clarification needed
We confirmed through live testing that {{user.tenant_id}} resolves correctly in RLS rules but {{user.data.tenant_id}} does not. Please clarify: is {{user.tenant_id}} officially supported? Can you add it to the documentation? Also, why does {{user.data.*}} not resolve for RLS despite being documented as supported?
mo himmy 1 day ago
Feature Request