> You may already be asking: “why not just power the stack using TimescaleDB?” The Timescale License would restrict our use of features such as compression, incremental materialized views, and bottomless storage. With these missing, we felt that what remained would not provide an adequate basis for our customers’ time-series needs. Therefore, we decided to build our own PostgreSQL-licensed extension.
It's much newer for one, so it's behind on features. But, we're working on adding new ones based on customer demand.
We want to build it with a PostgreSQL license using existing community extensions as much as possible and build custom stuff (still permissively licensed) only when necessary.
The use of postgresql licensing might mean we can see this available for AWS RDS and other managed PostgreSQL providers.
Timescaledb's license is more like Redis' new license?