Deploy DocsGPT

Chat with your documents and build AI agents; pgvector, no API key needed

Deploy DocsGPT

Just deployed

/data

/data

/var/lib/postgresql/data

Deploy and Host DocsGPT on Railway

DocsGPT is an open-source AI assistant that answers from your own documents. You upload files or add websites, then chat with answers that cite their sources. It also builds agents with tools and schedules, and serves them through a chat widget, a REST API and an OpenAI-compatible endpoint.

About Hosting DocsGPT

DocsGPT needs its API (which also serves the web UI), a Celery worker for ingestion and scheduled jobs, PostgreSQL with pgvector, and Redis. This template runs the official arc53/docsgpt:1.1.0 image, pinned by digest and built from a public GitHub repo, with the API and the worker in one service that shares a volume for uploaded files. Railway's Postgres holds users, chats, agents and vectors; Railway's Redis holds the task queue. All secrets are generated, sign-in is on, and the hosted DocsGPT model works without an API key. Nothing to fill in at deploy.

Common Use Cases

  • A documentation assistant that answers from product docs, wikis and PDFs, with citations
  • Private search over a team's internal documents
  • A support chat widget or an OpenAI-compatible endpoint backed by your own sources

Dependencies for DocsGPT Hosting

  • PostgreSQL with pgvector (Railway's Postgres, included)
  • Redis (Railway's Redis, included)
  • An LLM: the hosted DocsGPT model by default, or your own OpenAI, Anthropic, Google, Groq or OpenRouter key

Deployment Dependencies

Implementation Details

After deploy: wait until DocsGPT, Postgres and Redis are green. Open the DocsGPT service's deploy logs, find Generated Simple JWT Token: and copy the token after it. Open the public domain and paste the token when asked. Then add a source (upload a file or add a website) and ask a question.

Sign-in: upstream ships with no sign-in. This template sets AUTH_TYPE=simple_jwt, one shared access token. Keep it private; set a new JWT_SECRET_KEY to revoke it. For one account per person, set AUTH_TYPE=oidc with OIDC_ISSUER, OIDC_CLIENT_ID and OIDC_FRONTEND_URL.

Your own model: add LLM_PROVIDER (for example openai) and API_KEY to the DocsGPT service, optionally LLM_NAME, and redeploy.

Data: uploaded files on the DocsGPT volume (/data), everything else in Postgres. Don't change ENCRYPTION_SECRET_KEY after you connect tools or services, or their stored credentials become unreadable. Update API_URL when you add a custom domain.

Memory: ingestion runs the embedding model on the CPU and needs about 1.5 GB of RAM, so use the Hobby plan or higher.

Updates: the DocsGPT service builds from aalfath/docsgpt-railway-template. When we bump the pinned version, Railway shows you an update notice and you choose when to apply it. Read the repo's CHANGELOG first and back up Postgres before a major upgrade; migrations run on start.

Why Deploy DocsGPT on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying DocsGPT on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.


Template Content

More templates in this category

View Template
Chat Chat
Chat Chat, your own unified chat and search to AI platform.

okisdev
117
View Template
Weaviate
Vector database with hybrid search and an API key-protected API

GitHub Locker
1
View Template
Möbius Personal AI OS
Self-hosted AI agent that builds and runs apps for you, with memory.

bento
1