Does not seem (too) open to me.
https://flowbite.com/license/
You cannot:
- Use the download files to create End Products that are designed to allow an End User to build their own End Products using the download files or derivatives of the download files.
- Re-distribute the download files or derivatives of the download files separately from an End Product, neither in code or as design assets.
- Share your access to the download files with any other individuals
I guess depends on your definition 
In simple terms, use FlowBite for anything you like except for projects that compete with FlowBite and would have a negative impact on our product sales
This is good enough for any of my use cases.
You might be referring to this issue, Replace Bulma with TailwindCSS, posted on the surface_catalogue GitHub repo.
That issue was opened by Marlus after this Initial discussion took place on the surface_tailwind GitHub repo.
yep, Daisy is progressing quickly and when you need to you can break out into custom Tailwind CSS extravanzas
Thank you for making me aware of daisyUI.
I’ve tried Flowbite and, although it looks quite nice, it doesn’t feel like a real component library to me. Copy-and-paste of long component definitions with hard-coded colors into my CSS isn’t really what I want.
DaisyUI is a whole different league. Concise classes to style a component (e.g. btn btn-primary btn-sm) and use of semantic colors (primary, secondary etc.) that are resolved differently depending on the theme.
Exactly what I was looking for! Been playing around with it for just 10 minutes and I’m already in love 
I know this is an old thread but I like Daisy too; a basic semantic layer that you can easily customize and tweak in multiple ways, including regular Tailwind utilities.
I was surprised how much can be done with pure CSS, even the modal dialog has no scripting. Which might make it a little trickier to integrate into a component, I guess you’d have to bind to the state of the checkbox which controls the show/hide behaviour.
I am still on the fence on Tailwind in general but the core components generated by the latest phx.new and phx.gen.live in 1.7 really have me understanding it quite a lot better. The components look a bit thick with all the utility soup but the actual views are very clean, I think this combo works quite well.
even the modal dialog 4 has no scripting.
For a proper modal dialog you need to capture focus inside the modal. So that tabbing between elements stays only inside the dialog. Other wise keyboard navigation and accessibility is broken.