Persistent Branding Support for Web Console (e.g., Favicon & Logo)

Is your feature request related to a problem?

🧩 Is your feature request related to a problem?

Yes. Currently, replacing favicon.ico or favicon.svg in public/assets lets you customize the web console’s icon—but these changes are overwritten every time QuestDB is upgraded. This makes it difficult to maintain consistent branding across upgrades, especially for enterprise and internal deployments.

---

🌟 Describe the solution you'd like

I’d love to see persistent, upgrade-safe branding support added to the QuestDB web console. Possible enhancements:

• Support a config option or environment variable to specify a custom logo folder or asset path.
• Provide a dedicated “custom branding” folder that is preserved during upgrades.
• (Optional) Introduce UI theming capabilities—like custom colors, fonts, or logo placement—to better match user/enterprise branding.

---

🔁 Describe alternatives you’ve considered

• Manually replacing favicon files after each upgrade—this is time-consuming and error-prone.
• Using a proxy or middleware to intercept and inject custom assets—an overly complex workaround.

---

🙋 Full Name

Suryansh Jain

---

🎓 Affiliation

Student

---

🗒 Additional Context

This feature is especially valuable for developers embedding QuestDB into internal dashboards or tools where consistent UI/UX and branding standards are required.

Describe the solution you'd like.

No response

Describe alternatives you've considered.

No response

Full Name:

Tousif khan

Affiliation:

QuestDB

Additional context

No response

Start by reviewing how assets in public/assets, including favicon.ico and favicon.svg, are served and replaced during upgrades. Define a concrete upgrade-safe branding mechanism from the listed options, then verify that custom assets remain available after an upgrade without requiring manual replacement.