Hi @saolof,
On the LXD licencing question - we did not select AGPL to create fear and drive people to commercial licensing, we selected it to avoid fragmentation of the network API and protocol. So dual-licensing isn’t our goal or something we do regularly. At the same time, for companies that are partners or customers, we often give people a royalty-free source license if that makes their internal conversations easier (we understand some orgs have a historical aversion to AGPL). So yes, if you were embedding all of this into a product and using Ubuntu Pro we would do the same for you. That’s not a traditional permissive open source license, just a non-AGPL source available license for you, it wouldn’t allow your customers to treat the code as if it were theirs, only you. And our goal, again, would be to make sure that your API was the same as the standard API for LXD even if you modified it. Does that help?
On the timescaledb question, I believe we do support that scenario, please do reach out to me if you want to discuss it and I can connect you with the right people working with Postgres on our side.