Yeah, the code is in a docker image, published on docker hub. It's prepackaged so it's easy to set up with docker-compose. The repo mostly has the docker files needed to self-host the dropbase worker and client. As you said, it's a bizarre, but not uncommon way to distribute. We're not technically open source at the moment, but considering evolving into source-available, and maybe eventually move up to an open source model. But we still have plenty to figure out. It's a bummer we can't get your feedback though, that's definitely a nice thing about open.

So does the docker file have something like python bytecode files in it or actual source? If it has source aren't you worried about people leaking it?

It has actual source for the worker. We aren't worried about it being leaked because we are not particularly trying to hide it in the first place. We will probably make source available to paying customers on request if they want to verify that their sensitive data only moves between self-hosted worker and self-hosted client.

The other reason is that internally we've always thought that we'd eventually gravitate to an open model when the time is right i.e. at least until after we've figured out the product.