Ecosystem & Repo Map
HQ is no longer a single combined repository. It is a set of independently versioned repos that compose through published npm packages, GitHub Releases, and one shared AWS Cognito identity. Each repo ships on its own cadence — a CLI release does not require touching the desktop app, and the cloud apps deploy independently of the scaffold.
The repos at a glance
| Repo | Ships as | What it is |
|---|---|---|
| hq-core | npx create-hq scaffold | The starter kit / seed for a new HQ instance. Ships minimal; rich capabilities install as packs. |
| hq-cli | @indigoai-us/hq-cli | The hq CLI — module management and cloud sync, the operator’s entry point. |
| hq-cloud | @indigoai-us/hq-cloud | The bidirectional S3 sync engine behind the CLI and the menubar app. |
| hq-sync | macOS app (GitHub Releases) | Tauri 2 menubar app — a friendly GUI over hq sync for non-technical users. |
| hq-console | Next.js app (hq.getindigo.ai) | Admin UI for HQ deployments, teams, and usage. |
| hq-deploy | AWS data plane | Serves deployed web artifacts on subdomains; deploy-management API. |
| hq-pro | SST app on AWS | The vault, team platform, and shared Cognito identity. |
| hq-packages | @indigoai-us/hq-pack-* | Content packs installed into an HQ instance via hq install. |
Each product has a dedicated page under Products.
How they compose
Composition rules
- The scaffold seeds, it does not run.
hq-coreis copied once bynpx create-hq. After that it has no runtime relationship to the other repos — upgrades flow through/update-hq, not a shared dependency. - The CLI owns sync; the engine does the work.
hq-clidepends on@indigoai-us/hq-cloudand lazily imports it only when ahq syncsubcommand runs.hq-cloudships ahq-sync-runnerbinary that emits ndjson sync events. - The menubar app is a GUI over the same engine.
hq-sync(Tauri 2) spawnshq-sync-runnerand renders its progress events. It is distinct from the engine itself — see hq-sync and hq-cloud. - One identity, many apps.
hq-proprovisions the shared Cognito pool and the vault.hq-consoleauthenticates against it (NextAuth/OIDC) andhq-deploytrusts JWTs minted by it — neither owns its own user store. - Capabilities install as packs. Rich add-ons (design styles, Slack bots, etc.) live in
hq-packagesand install viahq install @indigoai-us/hq-pack-*— see hq-packages.
Versioning
There is no single shared version anymore. Each repo carries and releases its own:
| Repo | Current version | Release mechanism |
|---|---|---|
| hq-core | hqVersion 15.x (core.yaml) | npx create-hq pulls the latest scaffold |
| hq-cli | @indigoai-us/hq-cli 5.x | npm publish from its own repo |
| hq-cloud | @indigoai-us/hq-cloud 5.x | npm publish from its own repo |
| hq-sync | 0.1.x | v* git tag → signed/notarized DMG + latest.json auto-update |
| hq-console / hq-deploy / hq-pro | per-repo | Vercel / SST deploys |
| hq-packages | per-pack version in package.yaml | npm publish per pack |
A package’s
repository.urlmay still point at the archived combined repo in older metadata — that is stale and not the source of truth. The split repos above are canonical.
Where to go next
- hq-cli deep dive — module management + sync bridge internals
- hq-cloud deep dive — the S3 sync engine
- Module system — how external repos plug in
- Products — concise per-product pages