OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
RAG & Knowledge Systems

Azure Tenant AI Chat

Azure Tenant AI Chat is a TypeScript-based, multi-user RAG application that organizations can deploy in an Azure subscription. It uses Neon Serverless Postgres for chat storage and search, creating a separate database for each user.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Azure Tenant AI Chat — OpenViST project profile in RAG & Knowledge Systems.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use it when you need a deployable Azure RAG chat application with per-user database separation, or want to adapt the Azure Chat Solution Accelerator to use Neon for chat storage and search.

Who it is for

  • Organizations building a private, multi-user document-chat application in Azure.
  • Developers adapting the Azure Chat Solution Accelerator to use Neon Serverless Postgres.

Documented uses

  • Deploy a private chat tenant in an Azure subscription.
  • Let users ask questions about documents such as PDFs.
  • Keep chat data separated by user with dedicated Neon databases.
  • Store chat threads, messages, and metadata and support search.
Before you choose

Requirements & limits

  • The project is a deployable application, so Azure and Neon services must be configured for the intended deployment.
  • The documented local-development prerequisites include a Neon account, a Neon API key, and Azure OpenAI configuration for AI chat.
  • The README says deployment costs depend on region and usage.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Prepare a local development setup

Configure and start the application locally for development.

Before you start

  • A Neon account
  • Azure OpenAI service configuration for the AI chat feature
  • A Neon API key

Steps

  1. Clone or fork the repository and change into its src directory.

  2. Rename .env.example to .env.local and populate the environment variables.

  3. Create a Neon API key and set it as NEON_API_KEY in .env.local.

  4. Install packages with npm install, then start the app with npm run dev.

Expected outcome

The development server starts; the README says a new Neon database is created for each new user.

Guide limitations

  • An identity provider is not required for local development; configuring one is optional.
  • The README identifies Azure OpenAI configuration as necessary to test the AI chat feature.
Documentation 1 ↗
COMPARE OPTIONS

Compare options for Retrieval-augmented applications

These projects document a common task and share a project role. This is a source-based comparison, not an execution benchmark or a guarantee of interchangeability.

ProjectDocumented purposePlatformAccess and requirements
Azure Tenant AI ChatDeploy a private chat tenant in an Azure subscription.Cloud, Web
Rag Powered AI Assistant Transforming Data Retrieval And Analysis Across The Web And PdfsRetrieve relevant passages from web and PDF content to answer a question.Web
LangChain in Supabase Edge FunctionsInitialize and start a Supabase project locally.Cloud, Server
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
16 October 2026
Original website title
neondatabase/azure-tenant-ai-chat · Official homepage title · retained in its source language
How we review sourcesSuggest a correction