Support Agent on Your Stack

Support Agent on Your Stack An architecture diagram generated by Archify. Platform user · analyst, PM, engineer · Architecture component · no source access Platform user analyst, PM, engineer no source access Chat · their own login · Architecture component Chat their own login Support agent · plans and fetches · Architecture component Support agent plans and fetches Gateway · the only way out · Credentials and per-user scope live here · identity + budget Gateway the only way out identity + budget GitLab · repositories · Systems your users cannot reach directly · GitLab GitLab repositories Confluence · internal docs · Systems your users cannot reach directly · Confluence Confluence internal docs Jira · tickets · Systems your users cannot reach directly · Jira Jira tickets Slack · team channels · Systems your users cannot reach directly · slack.com Slack team channels DB · records and metrics · Systems your users cannot reach directly DB records and metrics Trace store · kept for every run · Architecture component Trace store kept for every run asks in plain language every call results answers, never source code what it did, what it cost Systems your users cannot reach directly Credentials and per-user scope live here Legend Frontend Backend Database Security External

The access line

  • • Users never gain access to any boxed system
  • • The agent holds the credentials; the gateway narrows them per person
  • • Code is read to be understood, never returned

One connector per system

  • • Each system gets one adapter speaking a common protocol
  • • Adding a system is a connector and a line of config, not a rewrite
  • • The systems shown are an example set, not a fixed list

What users stop asking in chat

  • • Why did this start failing after the last release
  • • Where is this configured, and what is it supposed to be
  • • Has anyone hit this error before, and what did they do