DOCUMENTATION / Self-hosting

Self-host 10Signals

Install the full project and research worker on your own computer.

Runs on

Your own computer; localhost only

Before you start

Git, Docker with Compose 2.24+, your own provider key for research

Which key do I need?

1. 1

   Choose where research runs

   Local execution means the application and worker run on your infrastructure. AI/search requests still need your own provider account and may cost money. You do not need access to the company Trigger project for local self-hosting.

2. 2

   Clone 10Signals

   The default public main branch includes the local quickstart and AI provider settings; no feature branch is needed. Choose a new folder name if 10signals already exists. This is a local preview, not a hardened public-server release.

   git clone https://github.com/10claws/10signals-self-host.git 10signals

   Copy

   You should see A new 10signals folder containing the project and local-only compose.yaml.

3. 3

   Open the project folder

   Run all following commands from this folder.

   cd 10signals

   Copy
4. 4

   Configure 10Signals

   Docker pulls the prebuilt image and creates private .env configuration automatically. No key is requested in the terminal. Existing configuration is never overwritten.

   docker compose run --rm setup

   Copy

   You should see Private configuration saved, with the address http://localhost:8787.

5. 5

   Start 10Signals

   Starts the app, storage and worker together. Open http://localhost:8787 only after all three services are healthy, then create a local account. If the port is allocated, an older installation may open instead: stop it from its own folder or choose a free port with setup --port before first configuration. Keep the loopback-only binding; do not expose this HTTP preview to the network.

   docker compose up -d --wait

   Copy

   You should see Web, worker and gateway are healthy. Without a provider key, the app explains that research is disabled.

6. 6

   Connect your AI provider

   Open your local installation at its chosen localhost address, then Account → AI provider. You should see a masked OpenAI API key field and Test & save. Enter your own key there, not in a terminal command. Authentication and required model access are checked without generating a report. Billing credit and inference are checked when you run a report. Keys are encrypted per account; replacing or removing one needs no worker restart.

   You should see Key and model access checked. Saved for your account. You can now create a report.

7. 7

   Acceptance checklist

   Start with empty storage; create an account; add your provider key; run a real-domain report; test private/share access; restart and verify persistence. Scheduled watches are not enabled in this local preview. A home page loading successfully is not full installation acceptance.