Urgent: Critical Limitations in Auth and Domain Scalability – Pro User Feedback

Dear Base44 Team,

As a developer currently managing 17 projects on your platform, I am writing to share critical feedback regarding limitations that are directly impacting my launch and scalability capabilities in the Latin American market.

Despite having submitted feedback previously, I have not seen any progress on points I consider vital for any modern SaaS solution:

1. Auth Localization and Customization The current authentication system is too rigid. For the LATAM market, having a login flow exclusively in English is an unacceptable barrier to entry for end users.

Need: The ability to fully translate and customize the login interface.

Impact: The login page is the first point of contact with our brand; if we cannot control the language and flow, we lose brand identity and user trust.

2. Multidomain and Subdomain Structure (Scalability) Currently, the platform limits the ability to organize a "Mother Project" with independent technical branches.

Need: To be able to connect multiple subdomains to specific folders within the same project (e.g., docs.mydomain.com, admin.mydomain.com, app.mydomain.com).

Impact: Forcing connections to external platforms to resolve this only generates unnecessary costs and a fragmented architecture. We need file and path management that allows an ecosystem to scale under a single technical roof.

Honestly, I'm constantly creating systems with Base44 authentication, and I'm losing interest. I'm about to transfer all my projects elsewhere and am already looking for a solution. The authentication is very limited; there's only one Base44 authentication, and the worst part is that it's in English, and not all clients speak English. I'm creating a solution for Latin America.

A login page is where I enter to sell my brand and create the entire flow of my system.

Even though I've been sending feedback to Base44 for months, they don't listen. If you create the platform, you pay to use it; it's not free, so why limit it?

And they're sending me to connect to another platform, which is another expense, not to mention using the platform itself.

Base44 is creating things they won't use without focusing on the platform's actual solution.

The platform is missing many things, and all of them are very limiting.

1- Base44 authentication: which all Base44 clients are using, and the problem is that it's in English.

2- The possibility of [something] in a single project Scaling, creating, and connecting multiple domains and subdomains

In other words:

I can create folders within folders where I can place files.

I can create subdomains and connect them to a folder I opened on a website. Let's take the same example: I'm creating a parent project called postblin.com.

Within this project, I can have several folders that connect to various subdomains:

docs.postblin.com

help.postblin.com

admin.postblin.com

etc... Scaling all of this means the subdomain opens on a page, not on the main domain.

To understand what we need, I'm missing these two points in base44 encoding.

Conclusion: I have evaluated other alternatives on the market (such as Kilocode) that offer greater flexibility and more competitive cost structures for full-stack developers. My intention is to keep my 17 projects in Base44, but without a solution to these points of friction, I will be forced to begin a complete migration of my infrastructure to avoid further delays to my releases.

I hope you can prioritize these features, which are fundamental for those of us who build real and scalable solutions.