Your Odoo login screen is the first thing employees, clients, and portal users see every day — and out of the box it carries a framework branding credit beneath the authentication card. For a company presenting Odoo as its own internal platform or a white-labelled client portal, that leftover credit undercuts the brand you have spent money building everywhere else. Odoo core lets you swap the header logo and set a company favicon, but the web-login QWeb template (web.login, web.login_layout, and the signup/reset variants) still renders the branding block server-side, and there is no Settings toggle to remove it. You are left either editing core templates in place — which every upgrade silently overwrites — or leaving the credit where it sits.

Hide Powered By is a purpose-built module that cleanly suppresses that branding on every authentication surface without touching Odoo core. Technically, we ship a small addon whose __manifest__.py depends on web (and on auth_signup when your database exposes public signup), and we override the relevant QWeb templates with an inheriting view — an xpath targeting the branding node with position="replace", or a guarded t-if — so the credit no longer renders in the served HTML rather than being merely hidden by CSS that a user can defeat through the browser inspector. We wire the behaviour to a flag stored in ir.config_parameter so the change is explicit and auditable, and we include a defensive stylesheet asset as a second layer. Because the override lives in its own addon, it survives module and minor-version upgrades and can be toggled or removed cleanly.

The build covers every place the branding appears in your flows: the standard /web/login, the /web/signup and /web/reset_password screens, the portal (portal) footer branding for external users, and the backend "about" surface where relevant to your scope. We keep it framework-clean — no monkey-patching of core Python, no edits to web source — so security stays intact: no new ir.model.access.csv rows or record rules are required beyond what a configuration-only feature needs, and nothing widens data access. We validate the result against your actual login theme, custom logo, and any reverse-proxy or web.base.url setup so the served page is genuinely clean for both authenticated staff and public portal visitors, and we confirm parity across Community and Enterprise since the login layout differs subtly between the two.

Delivery is build-to-order: after a short scoping call we confirm exactly which authentication and portal surfaces are in scope and your target Odoo series, then build against a copy of your theme, test on a staging database, and hand over installable source plus a rollback plan. Typical delivery is 2–4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); additional surfaces, multi-company or multi-website branding rules, deep custom-theme integration, and localization depth increase the quoted scope. You receive a fixed quote after the scoping call — never a surprise on the invoice.