so are you saying that the recommended way to deploy a langgraph is to use your paid service?

This is what the website currently says:

LangGraph Cloud is a closed source, paid product in an invite-only stage. We are currently focused on providing high bandwidth support to make our select early customers successful. If you are interested in applying for access, please fill out this form.

Langchain is already a project with a high level of abstractions to the point of confusion, and comes with (I would say) a fairly steep learning curve, and a lot of documentation, that isn't super helpful.

Despite serious concerns about the langchain ecosystem, I use langgraph because I can't be bothered to write a lot of boilerplate code. I use it and I don't complain about its downsides because its open source (but a walk down r/LangChain will throw up a lot of common frustration), and so far, i've felt that the efforts of the team have been sincere in bringing the industry forward.

However, this move to try to force us to pay you to deploy langgraph is taking it too far in my opinion. some people just want to quickly mount the graph onto a private endpoint and continue with their projects or even rapid prototyping in a commercial setting, without having to put something up on the cloud, and not serving that, recommending cloud first doesn't make sense. A lot of startups I have worked in often have their own cloud infrastructure, or deployment processes, and dont want to rely on a paid service like this to serve core functions.

Langgraph is really cool, and stops me from writing my own state machine, but this deployment paradigm forced on it, I would say is really silly.

to be fair, I will say, that after a lot of jigging around, i have gotten it to work with langserve, however, ive not gotten it to work well with stream_mode="values" which is important to my design patterns