Every Odoo deployment ships with the same generic /web/login screen: a centered card, the stock database picker, and Odoo branding baked into the template. For an internal tool that might be acceptable, but the login page is the first thing employees, franchise partners, and portal customers see every day — and out of the box you cannot change the background, restructure the layout, tune the copy, hide the database selector, or reflect your own brand without editing core templates. Odoo core exposes no settings screen for any of this; the moment you want it, you are into overriding the web.login QWeb template and the auth controllers, which is precisely the kind of change that silently breaks on the next -u base or version upgrade if it is not packaged as a proper module.

This is a made-to-order module that ECOSIRE designs, builds, and installs specifically for your instance. We deliver it as a clean, self-contained addon with its own __manifest__.py that inherits (never patches) the relevant web templates via XML <template> inheritance, so your look survives upgrades and can be uninstalled cleanly. Technically, we override the web.login and web.login_layout QWeb templates to inject your background image or gradient, restructured card, logo, custom heading/subheading, footer links, and language/theme controls; assets (CSS/SCSS, optional OWL widgets, images) are registered through the web.assets_frontend bundle in the manifest so they are bundled and cached the Odoo way. Configurable options — background source, show/hide the database selector, custom links, per-company branding — are stored as res.config.settings fields backed by ir.config_parameter, so administrators change them from Settings without a redeploy. Where you need behavioral control (for example suppressing the DB selector, adding a "reset password" nudge, or a compliance/consent notice), we extend the web.Home / Session auth controllers with a thin Python override rather than replacing them.

Security and correctness are treated as first-class, because the login page sits on an unauthenticated route. Any new fields carry proper ir.model.access.csv entries and, where multi-company or restricted visibility matters, record rules; user-supplied HTML in custom notices is escaped/sanitized so the branding surface can never become an injection vector; and we keep the change compatible with your CSP and reverse-proxy headers. The module is built and tested against Odoo 17.0, 18.0, and 19.0, and works on both Community and Enterprise (Enterprise's own web assets are respected, not overwritten). If you drive provisioning through the XML-RPC/JSON-RPC API or automated actions, the configuration parameters remain scriptable so branding can be applied consistently across staging and production databases.

Because this is build-to-order, nothing is pre-listed for instant download — we build your version after we understand your scope. The flow is a short scoping call to confirm the exact look, the options you need, and your target Odoo version and edition; a fixed written quote; development on a staging copy of your database; UAT sign-off with a documented rollback; then installation on production and a handover of the git repository and docs. Typical delivery is 2–4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); multi-company branding, pixel-exact design replication, extra languages, or bundling with a broader portal/theme project increases the quoted scope.