It is &quot;free&quot; if you squint, but they kind of screw with you when you don&#x27;t pay them, to the point where I ditched jOOQ entirely because I didn&#x27;t feel like I could trust them to deal straight with me. They spam your application output like nagware unless you dig into the code for an undocumented flag (which has a really godawful guilt-trip comment next to it begging you to allow them to continue littering your logs with unparseable garbage that can&#x27;t even be bothered to go through logback to be piped correctly) and they hide their unit tests (and are real jerks about them, calling them &quot;an enterprise feature&quot;, when <i>in reality</i> they&#x27;re both documentation and verification that the stuff they say works actually <i>does</i> work). It&#x27;s their prerogative to do that, of course, but it&#x27;s not behavior I&#x27;d support. Team&#x27;s kind of shitty on Twitter, too, trolling around keyword searches and looking for a fight.<p>I don&#x27;t recommend its use, both from a &quot;can I trust this&quot; perspective as well as a &quot;do I want to support these guys&quot; one. If you can use Slick, I recommend it, as its developers have in my experience been uniformly solid people; I haven&#x27;t needed either recently, as I&#x27;ve switched stacks for the project I was going to use one or the other for, but Slick&#x27;s developers don&#x27;t make me feel <i>icky</i> to support.