Signal Hub is one Streamlit app that puts all twenty-four Signal tools behind a single link: a front page, a sidebar menu by
family, and every released tool running inside it with its fictional demo already loaded. It assembles apps that
already exist. Each tool stays its own repository and Python package, and the Hub pins released versions.
Everything runs locally with open-source Python packages. There is no account, telemetry, external AI call, remote
database, or built-in persistence. Uploads stay in your session's memory.
Brand
| App | Question | Repo |
|---|
| Track Signal | Is the brand moving, or is the tracker just noisy? | brand-tracking |
| Position Signal | Where do brands sit relative to competitors? | brand-positioning |
Market
| App | Question | Repo |
|---|
| Prospect Signal | Which Norwegian companies fit your ideal customer, and which first? | b2b-prospecting |
| Listen Signal | Who is talking about the brand in Norwegian media, and in what tone? | media-listening |
| Influence Signal | Which creators delivered, and was every post labelled properly? | influencer-campaigns |
| Season Signal | What does the Norwegian marketing year look like, worked backwards? | marketing-calendar |
| Adopt Signal | When will a new product be adopted? | adoption-forecasting |
| Rival Signal | Which rivals matter, and how could they respond? | competitor-analysis |
| Reach Signal | Where could a new location reach, and how would it share demand with existing sites? | location-catchment-analysis |
Customer
Research
Decide
How the apps fit together
Apps hand off rather than overlap: a tracking contrast in Track Signal is not a causal effect, so it points to
Experiment Signal; construct scores need Measure Signal evidence first. Each README names its siblings under
Read this first.
Run the Hub locally
You need Python 3.10 or newer.
macOS: double-click run_app.command. Windows: double-click run_app.bat.
The first launch creates a private .venv and installs every released app from its GitHub tag archive. Or use a
terminal:
python3 -m venv .venv
source .venv/bin/activate # Windows: .venv\Scripts\activate
python -m pip install -r requirements.txt
python -m streamlit run hub/app.py
The Hub prefers local port 8610. The launchers accept SIGNALHUB_PORT, and SIGNALHUB_DEBUG=1 shows technical
details when a tool fails.
Large files. Run on your own computer, the tools have no built-in data limits: memory is the limit. Uploads go
up to 10 GB by default (SIGNALHUB_MAX_UPLOAD_MB changes it), big tables on screen show a shortened view with a
note, and every calculation and export uses all of the data. The public demo image sets SIGNAL_PUBLIC=1, which
turns on demo limits in every tool; an internal company deployment runs it with
-e SIGNAL_PUBLIC=0 -e STREAMLIT_SERVER_MAX_UPLOAD_SIZE=10000 (see deploy/README.md).
Docker
docker build -t signal-hub .
docker run --rm -p 8501:8501 signal-hub
Then open http://127.0.0.1:8501. The container runs as a non-root user. See deploy/README.md.
How it works
apps.yaml is the only list of apps. The sidebar, the front page and the smoke tests read it;
python scripts/sync_suite.py writes everything else from it: the app tables above, the requirement pins, the
theme's app list, topics, repo descriptions, and the suite table in every app's README.- Adding an app takes one registry entry and a few commands: docs/ADDING_AN_APP.md.
python scripts/scaffold_app.py <slug> gives a new repo the standard files.
- An app joins the Hub by exposing
<package>.ui.render(): the app contract. Inside the Hub
apps run in Hub mode (SIGNAL_HUB=1): session memory only, fictional demo data, no network calls or disk writes.
- To update an app: release it (version, CHANGELOG, tag
vX.Y.Z), change its tag: in apps.yaml, run
python scripts/sync_suite.py, test, redeploy. Unfinished work in an app never reaches the Hub.
- Current state per app: docs/STATUS.md.
Shared design
signal-theme/ is the master copy of the suite's look: signal_theme.py (theme, lockups, chart palette), marks,
README banners, social previews, the README template, the app template (signal-theme/app-template/) and repo topics.
python scripts/sync_suite.py copies it into every app clone; --check reports stale copies. Rollout recipe: docs/BRAND_ROLLOUT.md.
Development
python -m pip install -r local-apps.txt -e ".[test]" # apps as editable sibling clones
python -m pytest
python -m ruff check .
pytest -m "not apps" runs the Hub's own tests without the apps installed. The apps tests render every embedded
app inside the Hub wrapper and check its version against apps.yaml.
Privacy
The Hub has no telemetry, analytics scripts, accounts or external AI calls, and it never writes uploads to disk. On
a hosted deployment, the operator is responsible for the server. See PRIVACY.md.
Originality and license
The software and documentation are free under AGPL-3.0-or-later. The suite is built with AI-assisted development:
Ulrik Erlingsen specifies, reviews and ships each release. It is new and makes no real-user or traction claims.
All repos carry the signal-suite topic: browse them. Freddo CRM is a
separate product (demo).
By Ulrik Erlingsen · AGPL-3.0-or-later
