Deploy OpenConnector on Pethost in one click

What happens

1. You sign in to Pethost or make an account, with a passkey, GitHub or Google.
2. No machine yet? You pick a plan, and we prepare one for you. The link waits in your browser until it is ready.
3. New project opens at the app. You fill in what it asks for and click Create project: Admin password.
4. In a minute or two the app is live at its own address with HTTPS. Its secrets are made for it at random, and its data is in the nightly backup.
5. It is a project like any other: its compose.yaml, its .env, its logs and a terminal are in the panel, and your agent can change it, roll it back or restore it.

First steps

Open the address and sign in to the console with the admin password you gave, then add the services’ API keys or OAuth apps. Agents connect to the address’s /mcp with a token from the console’s Access tab, or with RUNTIME_TOKEN from the project’s .env.

What it runs

The template is this compose.yaml and the variables it writes into the project’s .env. Pethost runs the file as it is written.

services:
  open-connector:
    image: ghcr.io/oomol-lab/open-connector:v1.8.0
    restart: unless-stopped
    environment:
      # The redirect URLs of OAuth and the examples in the action guides.
      OOMOL_CONNECT_ORIGIN: ${URL}
      OOMOL_CONNECT_DATA_DIR: /app/data
      # Encrypts the stored credentials: losing it loses them.
      OOMOL_CONNECT_ENCRYPTION_KEY: ${ENCRYPTION_KEY}
      # The web console and the admin API.
      OOMOL_CONNECT_ADMIN_TOKEN: ${ADMIN_PASSWORD}
      # Agents' calls to /mcp and /v1, so that they are never open.
      OOMOL_CONNECT_RUNTIME_TOKEN: ${RUNTIME_TOKEN}
    # SQLite, the connections and the transit files.
    volumes:
      - data:/app/data

volumes:
  data:

compose.yamlSee it on GitHub