FAQ

Yes - Zep offers a free tier. See Pricing for more information.

Yes - Zep offers a LangChain ZepChatMessageHistory and ZepVectorStore class that you may use in your LangChain Expression Language (LCEL) project.

Please use the classes available in the Cloud SDKs and not in the LangChain SDKs.

Not yet - we are working on adding support for LlamaIndex.

Yes, you can use Zep Memory - Cloud and Zep Collection - Cloud nodes in the latest Flowise release.

You can learn more in our Flowise Ecosystem section.

Yes - we’ve deprecated Intent Analysis and replaced it with a Session Classifier.

We’ve also removed the Named Entity Recognition (NER) feature. We are in the process of replacing NER with a more powerful and flexible Structured Data Extractor.

The API URL for Zep Cloud is https://api.getzep.com. Note that you do not need to specify the API URL when using the Cloud SDKs. If a service requests the Zep URL it is possible it’s only compatible with the Zep Open Source service.

We have official multilingual support on our roadmap, enabling the creation of graphs in a user’s own language. Currently, graphs are not explicitly created in the user’s language. However, Zep should work well today with any language, provided you’re using a multilingual LLM and your own prompts explicitly state that responses to the user should be in their language.

Zep Cloud is currently a major update to the Zep Open Source product. Going forward, Zep Open Source will offer a subset of Zep Cloud’s functionality, primarily as proprietary language models are used exclusively in Zep Cloud.

Yes - we will be releasing a new version of Zep Open Source based on Zep Cloud functionality. See above for more.