Congrats on the launch! I'm one of the cofounders of Prequel (I saw our name in the feature grid - small nit: we do support self-hosting). This is definitely a problem worth solving - the market is still early and I'd bet the rising tide will help all of us convince more teams to support this capability. I'm not a lawyer, but the latest EU Data Act might even make it an obligation for some software vendors?
Maybe I can save you a headache: Snowflake is actively deprecating single-factor username/password auth in favor of key pair auth, so the faster you support that, the fewer mandatory migrations you'll be emailing users about.
Thanks! Kalan here, I appreciate the nit! PR is already merged. Definitely agreed on the market, it seems like there's a ton of opportunity. And thanks for the heads up re Snowflake auth! we're actively working that one, and a few other auth modes for Redshift and BQ as well.
Great question. We think of data products as multi-tenant tables that are created with the intention of sending that data to a customer.
To compare with an ETL tool like Airbyte, it's really easy to sync a full table somewhere with Airbyte, but it get's more complicated if you have a multi-tenant table, where you want to sync only a subset of data to a customer.
When you're setting up a data model with Pontoon, you just define which column has the customer id (we call it a tenant id) and it handles sending the right data to the right customer.
And yet, the top level license file contains two licenses, a goddamn if statement, and finally a default to Elastic License which is not open source
Then, because if this trickery, lawyers get to make good money because does "2. LICENSE file in the same directory as the work" combined with "4. Defaults to Elastic License 2.0 (ELv2)" mean that this zero byte file NAMED LICENSE but devoid of any content match clause 2 or 4?
I hate cutesy licenses with all my heart. Just say you want to use Elastic, drop the Open Source pretense, and go back to selling software instead of trying to position yourself as "open"
No educated person is going to give you free commits in the current state so no need to be opaque in hopes of tricking them
To clarify the dual license, our connectors are under MIT and the core of Pontoon is under ELv2. We should have an FAQ to clarify that, since, as you mention, the license file isn't the most user friendly to read.
Pontoon is free to use and anyone can deploy it, we just want to have the protection in place in case we want to offer a managed version of Pontoon in the future for those who don't want the hassle of self-hosting.
We chose to go with ELv2 to be upfront from the start with what the license is, rather than the common trend we've seen with open source projects of starting with MIT/Apache 2.0 and then changing their license afterwards. We're really not trying to trick anyone here, we have both licenses listed right at the top of the readme.
Another great self-hostable platform. I'm not sure where they got their name from though, translations don't have a connection to lakes like data does...
Congrats on the launch! I'm one of the cofounders of Prequel (I saw our name in the feature grid - small nit: we do support self-hosting). This is definitely a problem worth solving - the market is still early and I'd bet the rising tide will help all of us convince more teams to support this capability. I'm not a lawyer, but the latest EU Data Act might even make it an obligation for some software vendors?
Maybe I can save you a headache: Snowflake is actively deprecating single-factor username/password auth in favor of key pair auth, so the faster you support that, the fewer mandatory migrations you'll be emailing users about.
Thanks! Kalan here, I appreciate the nit! PR is already merged. Definitely agreed on the market, it seems like there's a ton of opportunity. And thanks for the heads up re Snowflake auth! we're actively working that one, and a few other auth modes for Redshift and BQ as well.
What does the row "First-class Data Products" in the comparison table entail?
Great question. We think of data products as multi-tenant tables that are created with the intention of sending that data to a customer.
To compare with an ETL tool like Airbyte, it's really easy to sync a full table somewhere with Airbyte, but it get's more complicated if you have a multi-tenant table, where you want to sync only a subset of data to a customer.
When you're setting up a data model with Pontoon, you just define which column has the customer id (we call it a tenant id) and it handles sending the right data to the right customer.
> Open source: Pontoon is free to use by anyone
And yet, the top level license file contains two licenses, a goddamn if statement, and finally a default to Elastic License which is not open source
Then, because if this trickery, lawyers get to make good money because does "2. LICENSE file in the same directory as the work" combined with "4. Defaults to Elastic License 2.0 (ELv2)" mean that this zero byte file NAMED LICENSE but devoid of any content match clause 2 or 4?
https://github.com/pontoon-data/Pontoon/blob/v0.2.0/data-tra...
I hate cutesy licenses with all my heart. Just say you want to use Elastic, drop the Open Source pretense, and go back to selling software instead of trying to position yourself as "open"
No educated person is going to give you free commits in the current state so no need to be opaque in hopes of tricking them
To clarify the dual license, our connectors are under MIT and the core of Pontoon is under ELv2. We should have an FAQ to clarify that, since, as you mention, the license file isn't the most user friendly to read.
Pontoon is free to use and anyone can deploy it, we just want to have the protection in place in case we want to offer a managed version of Pontoon in the future for those who don't want the hassle of self-hosting.
We chose to go with ELv2 to be upfront from the start with what the license is, rather than the common trend we've seen with open source projects of starting with MIT/Apache 2.0 and then changing their license afterwards. We're really not trying to trick anyone here, we have both licenses listed right at the top of the readme.
Not to be confused with Pontoon, a self-hostable translation platform made by Mozilla: https://github.com/mozilla/pontoon
Another great self-hostable platform. I'm not sure where they got their name from though, translations don't have a connection to lakes like data does...
Is it like an offline sync?
Kalan here, syncs are batch based and scheduled, similar to conventional ETL / data pipelines