A multi-platform ecosystem spanning client, server, architecture and self-hosted infrastructure. Vault-sealed secrets, loopback-only networking, and one repo per concern.

A batteries-included platform for building and running production-ready services:

• Infrastructure (infra-* repos) — Docker Compose stacks for Vault, Postgres, Redis, Kafka, Consul, Prometheus, Grafana and Kong, all wired together on a shared kafka-network and bound to loopback only.
• Microservices (nest-* repos) — Domain services built with NestJS/TypeScript and wired into the infrastructure.
• Shared packages (@sca/*) — Zero-logic plumbing libraries (core, contracts, connections, clients) consumed by every microservice.
• Documentation (sca-docs) — The Obsidian knowledge base that maps the entire ecosystem; topology lives here, depth lives in each repo.
• Dev tools (local-dev-tools) — MinIO (S3) and MailHog (SMTP) for local use.

Every service follows the same pattern: own folder, own Makefile, own compose.yml, secrets from Vault via AppRole, .env generated at runtime, loopback-only ports, Consul health checks, and Prometheus scrape targets.

Framework-first naming: the framework implies the platform (nest-* = backend API, react-* = frontend web, next-* = fullstack web, react-native-* = mobile).

flowchart LR
  subgraph Secrets
    V[Vault]
  end

  subgraph Data
    PG[(Postgres)]
    RD[(Redis)]
  end

  subgraph Streaming
    K[Kafka]
    KC[Kafka Connect]
    UI[Kafka UI]
  end

  subgraph Gateway
    KO[Kong]
  end

  subgraph Discovery
    CO[Consul]
  end

  subgraph Observability
    P[Prometheus]
    G[Grafana]
  end

  subgraph Dev
    MI[MinIO]
    MH[MailHog]
  end

  subgraph Services
    AUTH[nest-auth]
    NOTI[nest-notifications]
    LOG[nest-logging]
    AI[py-ai]
  end

  V -.->|secrets| PG
  V -.->|secrets| RD
  V -.->|secrets| K
  V -.->|secrets| KO

  K -->|CDC| KC
  KC -->|captures| PG

  KO -->|routes| AUTH
  KO -->|routes| NOTI
  KO -->|routes| LOG
  KO -->|routes| AI

  CO -.->|discovers| K
  CO -.->|discovers| PG
  CO -.->|discovers| RD
  CO -.->|discovers| KO

  P -->|scrapes| V
  P -->|scrapes| PG
  P -->|scrapes| RD
  P -->|scrapes| KC
  G -->|queries| P

  AUTH -->|reads| RD
  AUTH -->|writes| PG
  NOTI -->|sends| MH
  AI -->|stores| MI

git clone https://github.com/sca-templates/infra-vault.git
cd infra-vault && make dev

git clone https://github.com/sca-templates/infra-postgres-app.git
cd infra-postgres-app && make all

git clone https://github.com/sca-templates/infra-redis.git
cd infra-redis && make all

git clone https://github.com/sca-templates/infra-kafka.git
cd infra-kafka && make all

git clone https://github.com/sca-templates/infra-consul.git
cd infra-consul && make all

1. Fork and branch off main.
2. Follow the conventions above (Makefile targets, Vault secrets, loopback).
3. Run make validate in your service.
4. Open a PR and fill the checklist.

See CONTRIBUTING.md for the full definition of done.

MIT © sca-templates