Jabuti

Install

Install Jabuti on your own server.

Every option runs the same Docker Compose file: Jabuti, its sandboxed shell runner and Caddy, which gets HTTPS certificates on its own. You need a server with ports 80 and 443 open, and an Anthropic API key.

Server
Ubuntu or Debian VPS; 4 GB of RAM on DigitalOcean
Disk
Persistent: database, notes and workspaces live on disk
Model
Your Anthropic API key, added in Settings
Domain
Optional at first: an sslip.io address works right away

Where to install

Any VPS

As root on Ubuntu or Debian, run the line below. It prints the address and the setup code.

curl -fsSL https://raw.githubusercontent.com/guilhermemauro/jabuti/main/deploy/install.sh | sh

Hostinger

Deploy on Hostinger

The setup code is in Docker Manager → jabuti → logs.

AWS

CloudFormation → Create stack → uploaddeploy/aws.yml. The address is in the stack's Outputs; the setup code in the instance's system log.

DigitalOcean

Create a Droplet (Ubuntu 24.04, 4 GB) and, under Advanced options → Add initialization scripts, paste this line:

curl -fsSL https://raw.githubusercontent.com/guilhermemauro/jabuti/main/deploy/install.sh | sh

Then open the Droplet's console and run this for the setup code:

cd /opt/jabuti && docker compose logs jabuti

Your machine

You need Docker with Compose and anAnthropic API key.

git clone https://github.com/guilhermemauro/jabuti.git
cd jabuti
cp .env.example .env          # set ANTHROPIC_API_KEY (or set it later in Settings)
docker compose up -d --build
docker compose logs jabuti    # prints the one-time setup code

Open http://localhost:4317, enter the setup code and choose the owner password. This setup binds to 127.0.0.1 only.

Then

  1. Open https://<the server's IP, dots as dashes>.sslip.io, such ashttps://203-0-113-10.sslip.io. HTTPS works before you have a domain.
  2. Enter the setup code and choose the owner password right away: until then, whoever has the code claims the instance.
  3. Settings → Model keys: add your Anthropic key.
  4. Settings → Domain: point a domain of your own at the server (anA record) and save it there.

Platforms whose disk is wiped on restart, like Heroku, do not fit: Jabuti keeps its database, notes and agents' workspaces on disk. Full instructions, configuration and the secret key setup are in the README.

First steps

From a fresh install to an agent at work.

  1. Settings → Agents

    The assistant agent comes ready. Ask it to create an agent for your site: it reads the site, proposes a brief and writes the profile, and you approve each change. An SEO agent template is included.

  2. Settings → Variables

    Add the keys your connectors need (each connector says where to get its key), scoped to the agents that may use them.

  3. Settings → Skills and Connectors

    Turn on the methods and MCP servers each agent should have: Search Console, Analytics 4, PageSpeed, Serper, DataForSEO and more.

  4. Start a conversation

    Pick the agent and give it work. When it has a plan, approve its milestones and turn on its routine so it keeps going on a schedule.

Updating

Settings → Version shows the running version and, when a newer release exists, what changed. To update, run this in the folder with the compose file (/opt/jabuti for the install script), or update the project in Hostinger's Docker Manager:

docker compose pull && docker compose up -d

To check for releases, the server asks GitHub twice a day: an anonymous request that sends nothing about your instance.

Keep the secret key apart

Model keys, connector tokens and variables are stored encrypted. By default the key that opens them lives in the data directory, and Settings warns about it. Move it into the environment, without generating a new one, as described in theREADME.

Found a vulnerability? Report it privately, as described inSECURITY.md.