Rebrand to mem0 unclear to consumers

[catmeme]

🐛 Describe the bug

Embedchain became a rebranded product with no outward messaging to users?

Today when I visit https://github.com/embedchain/embedchain I am redirected to https://github.com/mem0ai/mem0

• The website for Embedchain, https://embedchain.ai is still up, I don't see any messaging about an upcoming rebrand.
• There is no mention of this change in the blog: https://embedchain.ai/blog
• The README.md at https://github.com/mem0ai/mem0 contains no mention of Embedchain or the lineage.
• The website https://docs.mem0.ai/getting-started/quickstart mentions nothing about embedchain, furthermore, the package to install in the quickstart is a different name.

Can the maintainers please clarify what's going on with this transition?

[taranjeet]

Hey @catmeme , thanks for sharing your views. Please find our rationale for changing the name here: https://x.com/taranjeetio/status/1811789999257587785

We are working on other pointers, will keep you posted on this thread.

[Panczo]

TBH it gives me some vibes that you just want to make some money. Why I think like this? Just keep reading. First, there is no easy way to implement custom memory to embedchain, so far you just support your memory solution or some very limited information about session memory. Second, for god's sake, looking at the github readme your library solves completely different problem. Why not to just create a different repo? Third, changing project name to mem0 without any announcements keep users unsure what's the project goal. So far, I was thinking that your main goal is to gives users FAST and EASY way to implement rag applications. With this unclear change it looks like you change your directions to 'how to make some money'. What's more I believe your strategy now is to gives user ability to create RAG application but then only with your memory solution. So you just found your niche which is a memory for LLM apps. TBH it's not bad, but that big change is quite suspicious. And all of that is on the verge when I wanted to use your library in my project.

[catmeme]

This response is disappointing. There are licensing and security implications to this change, and that erodes trust with your existing user base.

1. My concerns haven't been addressed
2. There is no license defined for this new project
3. More dependencies are being added, possibly out of scope for what users originally thought they were installing
4. This is an unprofessional way to transition a project

[haroon0x]

@parshvadaftari we can close this issue