> The self hosted license seems fairly permissive (Don't cluster, don't let your users manage the database views/queries [IANAL, read the license yourself])
The self-hosted version is being discontinued after the current version. The only offering will be the purely commercial cloud offering.
> Honeypot ships with both Go binaries and a Docker image. This results in minimal artifacts to deploy, maintain, and monitor, and an entirely cloud-agnostic deployment model.
I'm not quite clear what the single container/package is. Is Honeypot the event collection and validation component with transport/routing being separate installations of Redpanda, and observability being a separate installation of Kowl. Likewise for the data persistence.
This sounds pretty awesome! Is Honeypot's intention to combine the tools to make for a single installation to quickly get up and running with event tracking, collection, and monitoring?
The quickstart looks to provide a good working example but with it being a docker-compose setup, how is it intended to deploy the setup into production and what are the requirements?
When it comes to event tracking are you free to use Snowplow tracker or any other tracking implementation and then just follow their setup instructions for defining tracking-events? How does Honeypot work in combining these multiple protocols to be queried in a database such as Materialize? Is serparate transformation in the database then required to be able to merge data from multiple sources and event protocols?