Dify integration
The root Docker Compose file supports source deployment, while the deploy directory targets released images.
Open-source / Deployable
Zhixing Gateway
Zhixing Gateway is a Dify-based local knowledge-base Q&A gateway: Gateway APIs, Admin Web, and assistant management make private knowledge bases, model connections, and Q&A entry points deployable in your own environment.
What is Zhixing Gateway
Zhixing Gateway is a self-hosted knowledge Q&A gateway built on Dify, providing Gateway APIs, an admin console, and assistant management to expose private knowledge bases through a unified entry point in your own environment.
Who it is for
- Developers and teams already using Dify or private knowledge bases
- Users who want to self-host a Gateway API and admin console
What problem it solves
Teams may already have documents, Dify apps, or local knowledge bases, but still need a deployable gateway layer to manage assistants and expose Q&A access cleanly.
Core capabilities
Gateway API
The Gateway exposes API docs and runs migrations plus idempotent seed logic on startup.
Admin console
Admin Web is separated from the Gateway backend so administrators can manage gateway configuration in their own environment.
Assistant management
Assistant management organizes Dify knowledge Q&A entry points into configurable workflows.
Typical workflows
- Configure Dify and environment variables
- Start Gateway and Admin with Docker Compose
- Create and manage assistants
- Ask questions through a unified API or frontend
Use cases
- Dify knowledge Q&A
- Private model entry
- Enterprise knowledge gateway
Inputs
- Dify application or knowledge-base connection
- Assistant configuration
- User questions
Outputs
- Unified Gateway API
- Assistant configuration
- Knowledge-base answers
Deployment and data boundary
- Services run in the user's own Docker environment
- Knowledge and model connections remain in the user's Dify environment
- The public repository is maintained on main and has no separate semantic release
Clone repository
git clone https://github.com/Jaycelu/zhixing.git
cd zhixingRun from source
cp .env.example .env
docker compose up -d --buildOpen services
Gateway API: http://127.0.0.1:8000
Gateway Docs: http://127.0.0.1:8000/docs
Admin Web: http://127.0.0.1:8080Run delivery compose
cd deploy
cp .env.example .env
docker compose up -dSystem requirements
- Requires Docker and Docker Compose
- Dify connection and environment variables must be configured according to the repository
Current version and update
main
Published：2026-05-27
Content updated：2026-07-14
Known limitations
- There is currently no semantic GitHub Release
- Dify and the runtime environment must be prepared by the user
How it compares
Using Dify directly
Dify provides knowledge base management. Zhixing Gateway adds a unified Gateway API, multi-assistant management, and an Admin console on top.
Cloud-hosted knowledge services
Cloud services store data on the provider's platform. Zhixing Gateway runs in your own environment — knowledge content and model connections stay within your control.
Building a custom gateway
Building from scratch requires implementing API routing, assistant management, an admin UI, and Dify integration. Zhixing Gateway provides a deployable, out-of-the-box solution.
Frequently asked questions
Is Zhixing Gateway a new model platform?
No. It is a deployable gateway and management entry for existing Dify applications and knowledge bases.
How is it deployed?
The repository provides Docker Compose workflows for source and delivery deployments.
Where does the data run?
Gateway, Admin, and connection settings run in the user's own environment.
How is Zhixing Gateway different from using Dify directly?
Dify provides knowledge-base application management. Zhixing Gateway adds a unified Gateway API, multi-assistant management, and an Admin console for teams that need a gateway layer.
Does my knowledge data leave my environment?
Zhixing Gateway runs in your own Docker environment. Knowledge content and model connections remain managed by your Dify instance and are not automatically transferred externally.
Related technical guides
No complete English guide is published for this product yet.
Product access
Product screenshots
