Built with Reflex badge remains visible on Reflex Cloud despite show_built_with_reflex=False

[he953]

Subject: Built with Reflex badge remains visible on Reflex Cloud despite being disabled

Hello Reflex Support Team,

I'm using Reflex 0.9.8.post1 for a Python e-commerce demonstration application hosted on Reflex Cloud.

Application URL:
https://mi-tienda-demo-internet-red-apple.reflex.run/

I configured the following option in rxconfig.py:

show_built_with_reflex=False

The badge disappears completely when running the application locally.

However, after successfully deploying the same configuration to Reflex Cloud, the "Built with Reflex" badge remains visible.

I have verified that:

• The production build and deployment both complete successfully.
• The configuration is recognized by Reflex.
• No direct reflex_enterprise imports or installed distribution were found.
• No REFLEX_SHOW_BUILT_WITH_REFLEX override is configured among the application's Cloud secrets.

Could you please clarify:

1. Is the badge mandatory for applications hosted on the Reflex Cloud Free plan?
2. Can it be removed without upgrading to Enterprise?
3. Is there an additional Cloud-specific configuration required?
4. If a paid plan is required, which plan specifically allows its removal?

Thank you for your assistance.

[junkerderprovinz]

On the free plan the deploy itself turns the badge back on, so there is no Cloud setting that will hide it. reflex deploy (reflex-hosting-cli 0.2.0) looks up the tier of the org you deploy with and, unless it is pro, team or enterprise, overrides your config with show_built_with_reflex=True. That's why your rxconfig.py value only works locally. On any of those three paid plans your False is kept, and an unset value defaults to hidden; the check is _resolve_badge_from_token_tier.

[saivamshidanthoju]

The explanation points to the deployment CLI overriding the application configuration based on the organization’s plan tier.

One useful way to make this behavior clearer would be to log a warning when _resolve_badge_from_token_tier overrides show_built_with_reflex=False on the Free plan. That would help developers distinguish a configuration issue from a hosting-plan restriction.

It would also be helpful to document this behavior in the deployment configuration reference, including which tiers preserve the setting and whether the override is applied during deployment or at runtime.

A small regression test could verify that show_built_with_reflex=False is preserved for Pro, Team, and Enterprise tiers, while the Free tier follows the intended restriction.

This would make the behavior easier to diagnose and prevent developers from spending time troubleshooting a setting that the deployment process intentionally overrides.