I’m planning to rebrand Fluent Bit (allowed under ...
# fluent-bit
d
I’m planning to rebrand Fluent Bit (allowed under Apache 2.0) to offer it as an authorised, secure, efficient and reliable log-forwarding agent for Windows and Linux endpoints. What’s the best approach for the rebrand? 1. Surface-level edits — icons, resources, names, default configs, etc. 2. Full code-level rebrand — compile from source and update branding directly inside the codebase for a clean release. Also — am I overlooking anything important (licensing, packaging, distribution, maintenance, security, etc.)? Any input or experiences from the community would be super helpful. 🙌
p
I mean we already do this: https://fluent.do See: https://github.com/FluentDo/agent Is there something specific you want that we don't provide as core maintainers?