✅ Quick Summary
Push44 provides a 100% free, production-grade fix operating at the Vite build pipeline level. Instead of hacking the DOM at runtime, Push44 connects directly to your Base44 project sandbox, injects atomic CSS specificity suppression rules (#base44-edit-badge, #base44-badge, div[id*='base44'] { display: none !important; opacity: 0 !important; pointer-events: none !important; }) into src/index.css, and dispatches a deployment trigger to POST /api/apps/:appId/deploy. When Vite compiles the production assets, the suppression rules are bundled synchronously into the primary stylesheet, ensuring the badge is suppressed before the browser engine paints a single pixel.
The Problem
Base44 injects an external script (/static/js/badge.js) inside the HTML <head> of every published site. On DOMContentLoaded, this script instantiates a high-priority container with id='base44-edit-badge' styled with position: fixed, bottom: 20px, right: 20px, and zIndex: 999999. In Base44's dashboard settings, toggling off this badge requires an expensive monthly tier subscription. Furthermore, attempting to delete the DOM element with browser JavaScript post-render often triggers layout shifts, console warnings, or fails when the badge script executes asynchronously.
How Push44 Solves It
Push44 provides a 100% free, production-grade fix operating at the Vite build pipeline level. Instead of hacking the DOM at runtime, Push44 connects directly to your Base44 project sandbox, injects atomic CSS specificity suppression rules (#base44-edit-badge, #base44-badge, div[id*='base44'] { display: none !important; opacity: 0 !important; pointer-events: none !important; }) into src/index.css, and dispatches a deployment trigger to POST /api/apps/:appId/deploy. When Vite compiles the production assets, the suppression rules are bundled synchronously into the primary stylesheet, ensuring the badge is suppressed before the browser engine paints a single pixel.
Step-by-Step Guide
Locate and copy your Base44 Personal API Token
Log in to your Base44 dashboard. Click your user avatar in the bottom-left corner and navigate to Account Settings > API Keys. Generate or copy your active API Key (e.g., b44_live_...). This token grants programmatic access to your sandboxed project source files and build deployment triggers.
Connect Push44 to your Base44 developer workspace
Navigate to Push44 (push44.vercel.app) or launch the terminal CLI (p44). Open Settings, select Base44, and paste your API key. Push44 instantly queries GET /api/auth/me to verify authorization and discovers all active projects in your workspace.
Inspect sandbox structure and live deployment metadata
Go to the Push dashboard and select your target application. Push44 inspects your live published domain (https://<slug>.base44.app), active Git checkpoint, and sandbox file tree (src/index.css, package.json, and components).
Execute automated CSS injection and edge production rebuild
Click the '🛡️ Remove Badge from Live Base44 Site' button on the project dashboard. Push44 automates three distinct operations: it verifies your current stylesheet, prompts the Base44 AI engine to append atomic suppression rules to src/index.css, and triggers POST /api/apps/:appId/deploy to rebuild the production Vite bundle.
Verify white-label suppression on desktop and mobile
Click 'View live site' to open your published *.base44.app URL. Perform a hard browser cache refresh (Ctrl+Shift+R or Cmd+Shift+R). Inspect the bottom-right corner — the 'Edit with Base44' button is completely gone for all visitors worldwide.
Pro Tips
- The CSS specificity approach guarantees zero Cumulative Layout Shift (CLS), ensuring perfect Google Lighthouse performance scores.
- The injected CSS rules persist across all visitor sessions, incognito tabs, and embedded iframes.
- Combine live badge removal with Push44's GitHub export feature to maintain a clean, independent source code backup.
Common Mistakes to Avoid
- Attempting to hide the badge using client-side tampermonkey or ad-blocker scripts, which only hides it on your personal machine.
- Manually modifying minified .js bundles in DevTools, which gets overwritten on subsequent page reloads.
- Paying $50+/month for enterprise builder tiers when client-side API injection delivers identical 100% white-label results for free.
Ready to Export?
Push44 is free, open source, and takes under 2 minutes to set up.