This catalog enumerates the active repositories under gitlab.avvyland.com/avvy. A repo is listed here if it is currently deployed in production (per the avvy/argocd repo) OR is a core dependency of a deployed service.
DomiDo lives in separate namespaces: gitlab.avvyland.com/domido (group 3) and gitlab.avvyland.com/domido-v2 (group 1294). See DomiDo.
Sourced from avvy/argocd Application manifests. See Deployed Services for the full deployment detail (images, ports, namespaces, ingress hosts).
state-server — Go scene/state backend. Page. The R0 Soft Financial backend (wallet / billing / commerce / entitlements / earnings + Stripe + typed ledger) lives on branch codex/r0-soft-financial-dev-merge, awaiting merge — see Financial Model.
avvy-worker — Async 3D model processing pipeline. Page.
avvy-app — React web client; deployed as avvyapp at app.avvyland.com. Page.
avvy-landing — Landing-page site.
web-app-avvy — Deployed as webapp at webapp.avvyland.com (separate from avvy-app; role overlap not currently documented).
contask — Internal task / scheduling service; ingress contask.avvyland.com. Repo description is sparse.
content-processor — Asset-processing worker (deployed as content-processor-worker).
texture-convertor — Texture-conversion worker (deployed as texture-converter-worker).
shopify-sync — Shopify product sync; ingress sc.avvyland.com.
js-wiki — Hosts this wiki at wiki.avvyland.com.
outline — Outline knowledge-base at docs.avvyland.com.
FoundationDB cluster (via foundationdb/base/fdb.yaml + per-env overlays) — production substrate for state-server.
Redis — common/redis-*.yaml. Serves state-server cache and avvy-worker's asynq queue.
argocd — GitOps manifests; the source of truth for deployments.
monitoring — Prometheus + Grafana stack (also the OTLP destination for traces — see Observability).
autoscaler — Cluster + horizontal pod autoscaling.
cert-manager, cloudflare/external-dns, gitlab-runner — standard cluster glue (not Avvyland-authored repos).
avvy-engine — Three.js + WASM rendering library, bundled into avvy-app. Page.
# Group projects + last activity
curl -s --header "PRIVATE-TOKEN: <token>" \
"https://gitlab.avvyland.com/api/v4/groups/18?with_projects=true" \
| jq -r '.projects[] | "\(.path)|\(.last_activity_at)|\(.description // "")"' | sort
# Deployed services
curl -s --header "PRIVATE-TOKEN: <token>" \
"https://gitlab.avvyland.com/api/v4/projects/150/repository/tree?recursive=true&per_page=200" \
| jq -r '.[] | select(.type=="tree") | .path' \
| awk -F/ '{print $1}' | sort -u
A repo qualifies for inclusion above if it appears in both the "recently active" list (≤6 months) and the ArgoCD deployment tree, or is imported by a deployed service.
gitlab.avvyland.com/avvy/argocd (deployment ground truth), GitLab groups/18 API (project activity), and the four core repos' source code (state-server, avvy-worker, avvy-app, avvy-engine) for verified internal dependencies.