Skip to content

Savvy Platform Suite

Repo: savvydealer-adam/savvy-platform-suite · Path: C:/Users/adam/openclaw/ (umbrella — individual services live alongside) · Owner: Adam Status: Active dev · % Done: 25 · Last commit: 2026-02-26 Deployed: not deployed (local dev only)

What it is

Umbrella repo packaging the new internal platform components built to replace Freshdesk/notes over time with API-native services. Bundles the core data layer, knowledge retrieval, gateway, and adapters into one deployable unit.

Why it exists

Central docs + deploy target for the platform. Each sub-service is its own repo for iteration, but the suite is the canonical assembly of "what runs to replace Freshdesk."

How it works

Composition of sub-services. - core-data-api/ — canonical entity storage, workflow transitions, SLA, reply-draft approval - knowledge-api/ — semantic retrieval over canonical chunks - unified-gateway/ — single API entrypoint - adapter-freshdesk/ — backup ingest + enrichment + live sync from Freshdesk - adapter-knowledge/ — process/call/OCR/graph ingestion - knowledge/ — schema, migration docs, parity checks, chunk materializer - ops/ — preflight + nightly job scripts

What's done

  • All sub-services scaffolded with quick-start docs
  • Runtime ports locked: Gateway 8090, Core 8091, Knowledge 8092
  • Freshdesk reply writeback model (ticket_fd_<live_id>) defined
  • Env-driven writeback toggle (FRESHDESK_WRITEBACK_ENABLED)

What's next

  • Complete Freshdesk parity (see ticket-system PRD)
  • Deploy suite to Cloud Run (currently local-only)
  • Finish adapter-freshdesk live-sync path

Where the code lives

  • Umbrella: savvy-platform-suite repo
  • Sub-service deploy: each <service>/ has its own uvicorn app.main:app --port <N> entry
  • Ops scripts: ops/

Integrations

Don't rebuild this — extend it

All new internal data + knowledge services should land inside this suite behind the gateway, not as standalone apps.