If you're looking for an open-source consent solution there's Klaro, which is used by thousands of websites already and is completely free (BSD-licensed):
You can easily adapt it to various legislations (GDPR & ePrivacy, CCPA, ...) and customize styling and code. It's fully self-hostable and does not require any external resources, it also doesn't send any information to third parties. Interactive consent as a feature (what they call contextual consent) is coming soon as well.
I like Metomic but I wouldn't say it's "privacy-first" as they log consent in their backend. This unnecessarily sends user data to a third party. Neither the ePrivacy directive nor the GDPR requires such a thing. I can understand why they want this data as they need to monetize their service, but I think it's really pointless as you store a cookie that then allows you to retrieve consent data, which you could just as easily store directly in the cookie as well (which Klaro does). Storing consent directly in a cookie allows the website owner to check it on the server side if required, and to prove that the user was asked for his/her consent.
Otherwise it seems like a great tool with a good UI!
https://klaro.kiprotect.com/
You can easily adapt it to various legislations (GDPR & ePrivacy, CCPA, ...) and customize styling and code. It's fully self-hostable and does not require any external resources, it also doesn't send any information to third parties. Interactive consent as a feature (what they call contextual consent) is coming soon as well.
I like Metomic but I wouldn't say it's "privacy-first" as they log consent in their backend. This unnecessarily sends user data to a third party. Neither the ePrivacy directive nor the GDPR requires such a thing. I can understand why they want this data as they need to monetize their service, but I think it's really pointless as you store a cookie that then allows you to retrieve consent data, which you could just as easily store directly in the cookie as well (which Klaro does). Storing consent directly in a cookie allows the website owner to check it on the server side if required, and to prove that the user was asked for his/her consent.
Otherwise it seems like a great tool with a good UI!