Practical overview
When it fits
Use Voapi when you need to operate a self-hosted gateway that centralizes AI model API forwarding and channel configuration.
Who it is for
- Operators who need to route AI model API requests across configurable provider channels.
- Teams that want a shared gateway with user-issued API tokens and multi-user management.
Documented uses
- Forward model API requests through configured channels.
- Organize channels into groups and associate them with routing rules.
- Synchronize remote model and provider catalog data.
- Manage API tokens and request limits for users and channels.
Requirements & limits
The repository documents Docker Compose and single-container deployment. The first registered user becomes the administrator. The README distinguishes community and Pro editions.
- The README documents Linux amd64 and arm64 Docker images.
- The single-container instructions require MySQL and Redis to be prepared and config.yml to be configured.
- Database configuration lists MySQL or PostgreSQL for application data and MySQL, PostgreSQL or ClickHouse for separated logs; Redis is also configured.
- The README lists forwarding, tokens, channel controls, retries and synchronization in both community and Pro editions, while online payments and advanced dynamic routing are Pro-only.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Deploy Voapi with Docker Compose
Start the Voapi service using the repository's documented Docker Compose steps.
Before you start
- A Linux host; the README lists Linux amd64 and arm64 images.
- Docker Compose.
- For Linux arm64, use the documented arm64 image in docker-compose.yml.
Steps
Clone https://github.com/VoAPI/VoAPI.git.
Change into the VoAPI directory.
Run docker-compose up -d.
Open http://localhost:6800, adjusting the domain or port as needed.
Expected outcome
The documented deployment path starts the service and opens its interface; registering the first user creates the administrator account.
Guide limitations
- These are README setup instructions, not independently verified execution results.
- The supplied README does not detail further host-specific networking or deployment configuration.
Configure a first provider channel
Follow Voapi's documented administration sequence to create a channel after deployment.
Before you start
- A deployed Voapi instance.
- The first registered account, which the README identifies as the administrator.
Steps
Sign in and open the administration area using the gear icon.
In the model and provider sections, synchronize the remote model list and provider list.
Create a blank rules engine; the README says leaving optional fields empty makes it pass requests through.
Create a channel group, then create a channel and select that rules engine and group.
Expected outcome
A channel is configured with a selected rules engine and channel group.
Guide limitations
- The README describes configuration steps but does not verify a successful request through the channel.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 16 October 2026
- Original website title
- VoAPI/VoAPI · Official homepage title · retained in its source language