# Potential Enhancement: Django-Managed PostgresSaver

**URL:** <https://forum.langchain.com/t/potential-enhancement-django-managed-postgressaver/3810>\
**Category:** LangGraph\
**Tags:** python-help\
**Created:** [May 28, 2026, 2:10am UTC](https://forum.langchain.com/t/potential-enhancement-django-managed-postgressaver/3810 "2026-05-28T02:10:44Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jcayers20](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.langchain.com/jcayers20/32/3063_2.png) [@jcayers20](https://forum.langchain.com/u/jcayers20)\
**Post date:** [May 28, 2026, 2:10am UTC](https://forum.langchain.com/t/potential-enhancement-django-managed-postgressaver/3810/1 "2026-05-28T02:10:44Z")

</div>

I have been experimenting with the `langgraph-checkpoint-postgres` library; I’m pretty new to agent development so I haven’t tried anything too exciting yet but so far it works great! My only gripe as a Django developer is that it adds tables to the database that aren’t managed by Django.

I can (and will, for now) work around this by creating a migration that performs a `RunPython` operation instantiating a `PostgresSaver`and running the `.setup()` method on it, but I’m considering writing a library similar to `langgraph-checkpoint-postgres` that relies on Django and provides models, uses ORM for working with the database, etc. The concept I have in mind is to package the checkpointer as a Django app with models, migrations, and versions of `PostgresSaver`, `AsyncPostgresSaver`, etc. that use those models. Could probably do something for other databases too.

I’m putting this message out to see if there’s anyone else out there who’d be interested in something like this. If I’m alone I’ll probably just go with the workaround above but if others would find it useful, I’d love to contribute to LangGraph.