Model or dataset
vintasoftware/django-ai-assistant avatar
vintasoftware/django-ai-assistant

django-ai-assistant: one env template, three provider extras, two Discord links

Integrate AI Assistants with Django to build intelligent applications

430 stars40 forksPythonMIT

At a glance

What is it?
A pre-1.0 Django package from Vinta Software that puts LangChain and LangGraph inside Django apps for tool calling and RAG. The dependency choices are legible and the front page is not, and setup lives entirely on an external site.
Who is it for?
Treat vintasoftware/django-ai-assistant as a library paired with an external documentation site rather than a self-contained project, because that is what the repository holds: a poetry manifest, a one-line environment template, seven sample Django apps and a hosted guide.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Activity is slowing. The repository last received commits 7 months ago.
What is it written in?
Mainly Python, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • vintasoftware/django-ai-assistant430 ★ · -2
Star history
Repository2026-09-152026-11-15
vintasoftware/django-ai-assistant432430

-2 Stars in the last 61 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Two Discord invite codes carry the same label

The front page carries two different Discord invite links and no note about the difference. The badge row at the top of the file points at discord.gg/mqdubnPb, while the Community section lower down points at discord.gg/fQfH9PkJM6. Both are bare invite codes, and both are labelled a Discord Server.

For a project whose main channel for questions is chat, that is the first link a new reader clicks, and the page gives no way to tell which invite is current or whether one belongs to a server that has moved on. Anyone landing on the wrong one gets an expired-code screen instead of a channel, and nothing in the repository separates the two. A Discord invite appears twice on the page, the documentation address once, and the commercial contact address once.

Onboarding is a video, and the front page carries no install command

The whole setup path is a recording. The section headed 5 minute demo holds a single GitHub asset URL and no text at all, so the first thing a new user is shown is a video rather than a sequence of steps. After it the page moves to Community, then Contributing, then Commercial Support. The only pointer to actual setup is Please check the documentation, aimed at vintasoftware.github.io/django-ai-assistant.

The 156-word front page therefore contains no install command, no configuration snippet and no minimal example. Everything a user needs to run the app sits behind a hosted site the repository does not contain. The three badges at the top also carry no link text, being bare anchors wrapped around images, which makes the first accessibility question on the front page of an accessibility-adjacent Django package one its own scanners would raise.

The one-line description names OpenAI, the extras table offers three vendors

The metadata and the dependency table disagree about which provider this package is for. The description field in pyproject.toml reads Django app to integrate with OpenAI Assistants API. The repository summary reads Integrate AI Assistants with Django to build intelligent applications, with no vendor named. The front page says AI Tool Calling and RAG, again with no vendor.

The dependencies name three. langchain-openai, langchain-anthropic and langchain-google-genai are all declared optional, and the extras table maps openai to langchain-openai with further provider entries following. So the field that package indexes and search results read first names one vendor while the install surface offers three. langchain ^1.2.6 and langgraph ^1.0.6 are required, while no provider client is, and langgraph in particular has no mention anywhere in the front page.

The committed env template names one key and the extras offer three providers

The environment template at the repository root is one line: OPENAI_API_KEY=your-key-here. There is no Anthropic key and no Google key in it, and no model endpoint or database variable, even though django_ai_assistant is a Django app whose runtime configuration has to arrive from somewhere for a chosen provider.

That leaves the template and the extras table describing different projects. The default path, which installs no extra at all, matches the single line that exists. Every path that pulls in langchain-anthropic or langchain-google-genai leaves the reader to work out the variable name alone, and the placeholder your-key-here documents nothing about scope or format. example/ ships its own .env.example as well, so a fresh clone has two templates to reconcile and nothing saying which one to copy.

Django is unbounded and the classifier matrix stops at 5.1

The Python floor is narrow and the Django floor is not. The dependency block asks for python = ^3.10 and Django >=4.2. The classifiers declare Python 3.10, 3.11, 3.12 and 3.13, and Django 4.2, 5.0 and 5.1, with Development Status :: 3 - Alpha attached to the same list.

The Django constraint carries no upper bound, so it admits every future release of the framework while the declared matrix stops at 5.1. Django is where breaking changes tend to land in a web framework, and an open-ended lower bound lets a resolver pair this package with a Django version nobody has run against it. The Python range does the opposite and stops cleanly below 4.0. Nothing in the front page states a supported-version matrix, so those two declarations in pyproject.toml are the only place to look.

Three releases in seven weeks, and the last commit is the newest tag

The release history is quick and the status label stays cautious. Releases went 0.2.1 on 2026-01-26, 0.3.0 on 2026-03-13 and 0.4.0 on 2026-03-23, while the classifiers still read Development Status :: 3 - Alpha. Three releases inside seven weeks under a pre-1.0 label is a normal shape for a young package, and the third release is also the last commit: the push to the default branch landed 2026-03-23, so nothing has moved on the default line since.

The version in pyproject.toml matches the newest tag exactly, which is the detail many repositories get wrong. The root does hold a CHANGELOG.md, but the manifest points Changelog at vintasoftware.github.io/django-ai-assistant/latest/changelog, a generated documentation page. The file in the tree and the address the manifest advertises are two different surfaces, and the three releases themselves carry no notes beyond the bare version numbers.

Seven sample Django apps and a second JavaScript toolchain

The example directory is larger than the package it demonstrates. example/ holds seven Django projects: demo, example, issue_tracker, movies, rag, tour_guide and weather. Five of the seven name one use case each, and only rag/ lines up with a claim made in the front page, which is RAG. The other four and issue_tracker appear nowhere in the 156 words above them.

Beside those servers sits a JavaScript toolchain the package metadata never mentions: package.json, pnpm-lock.yaml, tsconfig.json, webpack.config.js, babel.config.js, postcss.config.cjs and prettier.config.mjs, plus assets/ and a second manage.py. The repository root carries its own frontend/ directory as well. So a Python package described as a Django app ships a root frontend, an example frontend and seven sample servers, and the front page shows none of it, offering one video in place of the whole map.

Two addresses are called the homepage and neither is in the repository

Two different places are called the homepage. The project metadata records https://django-ai.com, and that string appears in none of the repository files. The manifest's own Homepage entry is https://github.com/vintasoftware/django-ai-assistant, which is the repository rather than a site.

That is the small version of a pattern running through the whole front page. The badge row points at a CI workflow, a coverage service and a Discord invite. The Community section points at a second Discord invite. The documentation address appears in the opening line and again in the manifest. The commercial support block names two domains for the same maintainer, vintasoftware.com and vinta.com.br, and one mailbox, [email protected]. None of it is wrong, and together it means a reader verifying the project has to decide which surface is authoritative.

Editorial conclusion

Treat vintasoftware/django-ai-assistant as a library paired with an external documentation site rather than a self-contained project, because that is what the repository holds: a poetry manifest, a one-line environment template, seven sample Django apps and a hosted guide. Before adopting it, confirm that the provider extra you need has an environment variable the template actually names, and pin Django to a version inside the declared classifier range instead of relying on an open-ended bound. Read the release notes first, since the package still declares alpha status and its last commit landed 2026-03-23.

Frequently asked questions

Which model providers does django-ai-assistant support?

Three, each as an optional extra: langchain-openai, langchain-anthropic and langchain-google-genai. The extras table maps openai to langchain-openai and lists further provider entries, while the one-line description in pyproject.toml names only the OpenAI Assistants API.

How do you install django-ai-assistant?

The 156-word front page gives no install command and sends you to the hosted documentation at vintasoftware.github.io/django-ai-assistant. The repository declares poetry in pyproject.toml, ships poetry.lock, and requires python ^3.10 with Django >=4.2.

What environment variables does django-ai-assistant need?

The root .env.example contains a single line, OPENAI_API_KEY=your-key-here. No Anthropic or Google key appears in it even though both clients are available as extras, and example/ carries a second .env.example of its own.

Is django-ai-assistant stable enough to depend on?

The classifiers read Development Status :: 3 - Alpha while pyproject.toml declares version 0.4.0. Releases 0.2.1, 0.3.0 and 0.4.0 shipped between 2026-01-26 and 2026-03-23, and the last push to the default branch landed 2026-03-23.

What example projects does django-ai-assistant include?

Seven Django projects under example/: demo, example, issue_tracker, movies, rag, tour_guide and weather, alongside package.json, webpack.config.js and a second manage.py. The repository root carries its own frontend/ directory as well.

Official sources

  1. License: MIT
  2. Project website
  3. README
  4. Releases
  5. vintasoftware/django-ai-assistant on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/vintasoftware-django-ai-assistant.svg)](https://hysenlabs.com/projects/vintasoftware-django-ai-assistant)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/vintasoftware-django-ai-assistant.svg)](https://hysenlabs.com/projects/vintasoftware-django-ai-assistant)

Was this useful?