We want to become the self-hosted data integration and transformation engine that most companies use in the future. This implies that our open-source technology will support both ingestion to warehouses from any tool, database or SaaS, and distribution of data to any SaaS tools.
On top of that, we will build data quality monitoring, privacy compliance (GDPR, CCPA, HIPAA, etc), and enterprise features (role access / management, SSO, etc.).
Eventually, you should be able to build your own Fivetran platform internally, while having complete control over your data and costs (not indexed on MTUs). If any integration that you need is missing, we will make it super easy for you to build it and to use our orchestration and scheduling features for it.
We will stay at parity with the incumbent’s features (Fivetran, StitchData) at first - see our high-level roadmap -, as our differentiation is on:
open source, enabling you to add your own integration very easily
data privacy and control
fixed pricing (not indexed on data volume or monthly active users).
There are a few key differentiating aspects to our strategy:
Our core product is free to use, open source, and extensible by anybody who can code.
We will be able to offer a wider array of data integration connectors. If an integration is missing, it is simpler to add it for an engineer, in comparison to building it on the side. Plus, you don’t need to wait for someone else's engineering team to prioritize it.
Your data stays in your cloud, which means it is more secure, and you have full control over your data transfer costs.
We have a zero-friction adoption in small, midsize and big companies, as you don’t need to go through security compliance to start implementing our solution.
Our pricing will not be indexed on data volume and can better fit with enterprises’ context. And our open-source codebase will never contain arbitrary limits (e.g., event volumes, user numbers).
We raised $1.8M in a seed round that gives us a runway until mid 2022. We will focus on the community edition until the Series-A. The metrics we will display to investors will be on adoption, deployments, and external contributions.
It is completely fine for us not to present any revenues before the Series-A.
We will build out and release the enterprise edition only after the Series-A. It is paramount that we continue to support the community edition so it:
remains the most reliable option with an active community
offers the highest number of integrations, sources and destinations.
Our team is composed of 5 engineering leaders, all from one of the highest-growing data companies in the world. We have already built 1,000+ integrations in the past on high-scale volume projects. This is why we can afford our ambitious technological goals.
We are working closely with contractors on the frontend side and to help us ramp up the number of connectors. We are doing all the UI design specs in-house for the moment though.