Make Public Apps Usable Without Allowing “Edit with Base44” Cloning (Protect Builders’ Original Work)

I’m requesting a change to how Public apps work in Base44, specifically the “Edit with Base44” button.

Right now, if an app is set to Public, any logged-in Base44 user can click “Edit with Base44” and Base44 will automatically create a full structural copy of that app in their own account (often labeled as a copy). I understand this may be intended for learning, onboarding, and helping the platform grow. But for builders who create real systems for real organizations, this creates a major risk.

Why this is a problem

Many of us build apps that must be public for community access (registration, requests, services, public-facing forms). But public visibility should not automatically mean the app is “remixable.”

Even if no private data is copied, cloning can still copy:

• The full database structure / entity design

• Workflows (approval flows, status systems, exports, validations)

• UI layout and page logic

• The overall system design (which is the actual “product” we built)

For serious builders, the idea + structure + workflow design is the value. When cloning is one click, it becomes easy for someone to take the entire system blueprint and reuse it without doing the work.

Real-world impact

I built a full community registry system with custom workflows and structure. It needs to be public so community members can use it. But because “Edit with Base44” can clone it instantly, it makes it hard to:

• Protect original app designs and logic

• Invest time building complex systems on Base44 confidently

• Share public tools for communities without giving away the full blueprint

This is not about hiding data—it’s about protecting intellectual effort (the workflow engineering, layout, and system architecture).

Feature requests (solutions)

I think Base44 can keep Public apps accessible while giving builders control. Any of these would help:

1. Add a toggle: “Allow cloning/remixing” (default ON for demos, OFF for serious builders)

2. Change button behavior: Make “Edit with Base44” open Base44’s new app creation flow, not clone the current app

3. Limit cloning to explicit templates: Only allow cloning if the creator marks the app as a Template/Remix Allowed

4. allow users with free version to hide the badge (or at lest set limit that they can only hide it from one app)

Why this matters for Base44

Allowing builders to publish public-facing apps without giving away the full blueprint will:

• Increase trust for organizations using Base44

• Encourage more serious “production” apps on the platform

• Reduce fear of sharing public tools

• Improve adoption among builders who are creating real systems, not just prototypes

I think this would be a strong improvement for creator protection while still supporting Base44’s growth.

Thank You Very Much!