Practical overview
When it fits
Use Trinity when agent work needs a self-hosted runtime, fleet-level coordination or operational visibility rather than a standalone agent session.
Who it is for
- Teams operating multiple AI agents on infrastructure they control.
- Developers building internal agent orchestration services.
- Organizations seeking scheduling, monitoring and audit capabilities around agent execution.
Documented uses
- Run supported AI agents in isolated Docker containers.
- Coordinate work between agents through delegation.
- Schedule recurring agent tasks across a fleet.
- Monitor agent activity and operational health.
- Maintain execution records through an audit trail.
Requirements & limits
The repository describes Trinity as open source under the Apache-2.0 license. Docker is required. SQLite is the default for local development and evaluation; PostgreSQL is recommended for production.
- Self-hosting keeps the runtime on infrastructure selected by the operator.
- Docker isolation is part of the described execution model.
- Claude Code, Codex and Gemini support is stated, but integration configuration is not included in the supplied material.
- Production deployments should use PostgreSQL according to the repository guidance, while SQLite is intended for local development and evaluation.
- The project identifies scheduling, delegation, observability, cost tracking and audit trails as platform capabilities.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Start Trinity on a Linux server with prebuilt images
Install and start Trinity on a Linux server using the hosted prebuilt-image stack.
Before you start
- A Linux server; Ubuntu 22.04 LTS or later is recommended, with 8 GB RAM minimum.
- Docker Engine 24+ and the Docker Compose plugin.
- A domain or subdomain pointing to the server IP, or a plan for private access.
- OpenSSL and outbound HTTPS access from the server.
- An
.envconfiguration withADMIN_PASSWORD,ANTHROPIC_API_KEY,FRONTEND_URL/PUBLIC_CHAT_URL, and an email provider.
Steps
Clone the Trinity repository and change into its directory.
Copy
.env.exampleto.envand configure the required values.Pin the desired release by adding a
TRINITY_IMAGE_TAGvalue to.env.Run
./scripts/deploy/start.sh --hosted --unattended.
Expected outcome
The hosted stack starts using prebuilt images; on a fresh install, the script configures the bundled PostgreSQL service and reports serving status and next steps.
Guide limitations
- Keep the repository checkout beside the compose file because the hosted stack mounts configuration and template files from it.
- The hosted stack does not build images; a failed image pull stops installation.
- Do not use a bare
docker compose up -don a production host; the guide specifies the hosted start script and hosted compose file for this setup.
Compare options for Agent orchestration
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.
| Project | Documented purpose | Platform | Access and requirements |
|---|---|---|---|
| Trinity | Run supported AI agents in isolated Docker containers. | Cloud, Self-hosted, Server, Web | The repository describes Trinity as open source under the Apache-2.0 license. Docker is required. SQLite is the default for local development and evaluation; PostgreSQL is recommended for production. |
| Agenite | Define typed tools with JSON Schema validation and error handling. | CLI | |
| Veldra | Create an agent with a policy, tools, skills, knowledge base and reasoning method. | Self-hosted | The documented deployment is self-hosted and uses a sign-in gate after a first-run administrator account is created. |
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 4 October 2026
- Original website title
- Abilityai/trinity · Official homepage title · retained in its source language

