I was thinking about writing an article with some similar insights: it's hard to build a company out of an OSS product where you're competing with your self hosting version. A good exit is better than shutting down. Fivetran looks like a solid company so it's still great news for the team! It also mean there will be a great support for the customers that already went for commercial offer from SQLMesh. For OSS users/contributors, it's not clear yet where it's heading. As you mentioned for dbt, dbt Fusion makes it awkward for OSS contributors should they stick to dbt Core? Move to dbt Fusion and risk being blocked by the Elastic license?
What's sure is that dbt project format is becoming the standard for SQL transformations with the intent of a full dbt project compatibility of SQLMesh.
This is the tough reality for data tooling companies. I wish Tobiko stayed independent, or I should say I thought they'd stay that way. But it wasn't the case and now I just hope fivetran will keep tobiko OSS products as OSS for as long as they can. I might set up an automation to fork SQLMesh OSS code periodically to prepare the day when fivetran locks it in 😂
I was thinking about writing an article with some similar insights: it's hard to build a company out of an OSS product where you're competing with your self hosting version. A good exit is better than shutting down. Fivetran looks like a solid company so it's still great news for the team! It also mean there will be a great support for the customers that already went for commercial offer from SQLMesh. For OSS users/contributors, it's not clear yet where it's heading. As you mentioned for dbt, dbt Fusion makes it awkward for OSS contributors should they stick to dbt Core? Move to dbt Fusion and risk being blocked by the Elastic license?
What's sure is that dbt project format is becoming the standard for SQL transformations with the intent of a full dbt project compatibility of SQLMesh.
This is the tough reality for data tooling companies. I wish Tobiko stayed independent, or I should say I thought they'd stay that way. But it wasn't the case and now I just hope fivetran will keep tobiko OSS products as OSS for as long as they can. I might set up an automation to fork SQLMesh OSS code periodically to prepare the day when fivetran locks it in 😂