Hacker News new | past | comments | ask | show | jobs | submit login

Hi @malisper, we totally appreciate concerns around potential uncertainty what a "Value Added Service" means.

In fact, when we were looking at Timescale licensing, we took careful look at what a lot of other like company licenses did here (Confluent, Redis, etc), and what later became the Polyform License. Most of them left this definition pretty vague -- because frankly, legal language is never as precise (and perhaps shouldn't be) as what an engineer may like.

We went a step further, and tried to define this more precisely about what it means to "offer" TimescaleDB:

      (iii) users of such Value Added Products or Services are prohibited,
      either contractually or technically, from defining, redefining, or
      modifying the database schema or other structural aspects of database
      objects, such as through use of the Timescale Data Definition Interfaces,
      in a Timescale Database utilized by such Value Added Products or
      Services.
[def] https://github.com/timescale/timescaledb/blob/master/tsl/LIC...

What that means is that if you've defined the Heap schema, you have built the indexes and tables, and then are offering a SaaS product on this, you're fine:

- You are offering a product/marketing SaaS service around usage/product analytics, not a time-series-database-as-a-service

- You are not approaching the market and saying, "Here's how to get TimescaleDB-as-a-service" (unlike, say, Managed TimescaleDB running on Rackspace or Digital Ocean), you are saying "Here's a full Product/Marketing Analytics Solution".

- You are not giving your users direct/psql access to the raw database to define their tables/schemas/indexes and otherwise just treat that service as a hosted TimescaleDB instance.

I hope that helps!






> We went a step further, and tried to define this more precisely about what it means to "offer" TimescaleDB

I don't understand how the bit you posted helped make things more concrete? Section 3.21, the section you referenced lists three conditions, all of which have to be true for your product to be considered "Value Added". I agree the third condition, the one you quoted, is pretty clear. But the second condition, the one I quoted seems really vague so the definition of "Value Added" as a whole becomes really vague.

> What that means is that if you've defined the Heap schema, you have built the indexes and tables, and then are offering a SaaS product on this, you're fine.

FWIW, Heap would automatically create new tables for customers as they sign up and would also automatically create new indexes for customers as needed. For that reason alone, I'm pretty sure Heap would violate the Timescale license.

I agree that it's pretty difficult to be specific about what "value added" means. I'm not sure what the right solution is. I would still want to go over with the Timescale License with an IP lawyer pretty thoroughly before I were to use TimescaleDB.


> FWIW, Heap would automatically create new tables for customers as they sign up and would also automatically create new indexes for customers as needed. For that reason alone, I'm pretty sure Heap would violate the Timescale license.

Nope! The user doesn't define or control that those tables and indexes are created. I.e., the user, through the Heap UI, doesn't say: I want a table with this schema and I want to create an index on (event_id, timestamp).




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: