Licensing Explainer — How Meergo's Hybrid Model Works
Meergo uses a hybrid licensing approach designed to balance openness, transparency, and protection of core intellectual property.
The Core — Elastic License v2 (ELv2)
What it covers:
Identity resolution engine, schema system, transformation engine, and data pipeline logic.
License: Elastic License v2 (ELv2)
What you can do:
- Use the source code freely for internal use, testing, or evaluation.
- Modify it for your internal business needs.
- Fork it, run it, and self-host it internally.
What’s restricted:
- You cannot provide it as a service (SaaS/CDP product) to third parties.
- You cannot redistribute it as part of a commercial offering.
Connectors & Drivers — MIT License
What it covers:
All data source/destination connectors, SDKs, and drivers (e.g., for Snowflake, PostgreSQL, etc.).
License: MIT
One of the most permissive open-source licenses.
What you can do:
- Use in commercial and non-commercial projects.
- Modify and redistribute freely.
- Extend with custom connectors and contribute back to the community.
Summary
| Component | License | Purpose | Restrictions |
|---|---|---|---|
| Core engine (identity, schema, pipeline) | Elastic License v2 | Power the CDP's foundational capabilities | No SaaS/CDP resale, no commercial redistribution |
| Connectors (sources & destinations) | MIT | Integrate external tools and platforms | None |
| SDKs & warehouse drivers | MIT | Embed data tracking & connect to DWH | None |
