For AI agents: The documentation index is at https://docs.digitalocean.com/llms.txt. Markdown versions of pages use the same URL with index.html.md in place of the HTML page (for example, append index.html.md to the directory path instead of opening the HTML document).

Trinity is sovereign infrastructure for autonomous AI agents: it deploys, orchestrates and governs fleets of them on hardware you own, with every agent isolated in its own Docker container and given a standardized interface for credentials, tools and MCP servers. Agents run on schedules, react to webhooks and pick up queued work unattended — failures retry and escalate rather than vanishing — while you watch executions live, chat with any agent, and share files through a workspace per agent. Slack, Telegram, WhatsApp and voice channels are built in, alongside an MCP server that exposes your fleet to Claude Code and other MCP clients, and credentials are injected at runtime, encrypted at rest and masked in every log.

This 1-Click brings up a complete instance with a real Let’s Encrypt certificate for the Droplet’s own IP address, so there is no browser warning and nothing to accept: open https://<your-droplet-ip>, create your admin account in the browser, add a model credential, and create your first agent from a template. Trinity ships no model credentials — you supply your own. Apache 2.0, self-hosted and inspectable; 8 GB RAM and 4 vCPUs recommended for a working fleet. DigitalOcean does not build or support Trinity — support is via GitHub Issues (please use the do-marketplace label) and docs.ability.ai.

Software Included

Creating an App using the Control Panel

Click the Deploy to DigitalOcean button to create a Droplet based on this 1-Click App. If you aren’t logged in, this link will prompt you to log in with your DigitalOcean account.

Creating an App using the API

In addition to creating a Droplet from the Trinity 1-Click App using the control panel, you can also use the DigitalOcean API. As an example, to create a 4GB Trinity Droplet in the SFO2 region, you can use the following curl command. You need to either save your API access token to an environment variable or substitute it in the command below.

curl -X POST -H 'Content-Type: application/json' \
         -H 'Authorization: Bearer '$TOKEN'' -d \
        '{"name":"choose_a_name","region":"sfo2","size":"s-2vcpu-4gb","image":"abilityai-trinity"}' \
        "https://api.digitalocean.com/v2/droplets"

Getting Started After Deploying Trinity

1. Wait about ninety seconds

On first boot the Droplet obtains a Let’s Encrypt certificate for its own IP address and starts Trinity. No domain is needed and there is nothing to configure.

2. Open it and create your admin account

Open https://your_droplet_public_ipv4 in your browser.

There is no password to look up and no terminal to open. Trinity asks you to create the admin account — your email, a password, and whether you want product updates — and you are in. The certificate is a real Let’s Encrypt certificate issued for the IP address, so there is no browser warning and nothing to accept.

Do this as soon as the Droplet is up. Until an admin account exists, whoever opens the address first creates it. The Droplet holds nothing at that point, so if a Droplet you have never opened shows you a login page instead, destroy it and create another.

To close that window entirely, restrict port 443 to your own IP with a cloud firewall until you have signed in — leave port 80 open, the certificate is validated over it. You can also set the password up front with a cloud-init file when creating the Droplet: see Deploying on a single server.

3. Add a model credential and create your first agent

Trinity ships no model credentials — you supply your own. Add one in the browser, then create an agent from a template. The first-run guide walks through attaching a domain and serving it through a Cloudflare Tunnel when you are ready to move off the bare IP.

Updating

Over SSH (ssh root@your_droplet_public_ipv4) or in the Droplet Console. The release is pinned in .env — point it at the release you want, pull the matching tree, and restart:

cd /opt/trinity
sudo git fetch --tags && sudo git checkout <tag>
sudo sed -i "s/^TRINITY_IMAGE_TAG=.*/TRINITY_IMAGE_TAG=<tag>/" .env
sudo ./scripts/deploy/start.sh --hosted

Both steps matter: the checkout updates the scripts and the compose file, TRINITY_IMAGE_TAG updates the container images. Changing only one leaves the instance running a mix of two releases. The version shown in the web interface reflects the images, so use it to confirm the upgrade landed.

Database backups run nightly and before every migration, under /opt/trinity/trinity-data/backups/. They sit on the same disk as the database, so they protect against corruption and mistakes, not against losing the Droplet — take Droplet snapshots as well.

Sizing

At least 4 GB RAM and 2 vCPUs; 8 GB and 4 vCPUs recommended for a working fleet. Memory scales with the number of agents, not with traffic. Disk can be increased on a running Droplet, never decreased.

Support

• Issues and questions: https://github.com/abilityai/trinity/issues — please use the do-marketplace label
• Documentation: https://docs.ability.ai
• Hardening walkthrough: https://docs.ability.ai/getting-started/deploying/hardening

DigitalOcean does not build or support Trinity. Support is provided by Ability AI through the channels above.