/dashboard/settings/integrations).
Integrations are platform-scoped — they live on the Guardway cloud, not on an individual gateway. Set them up once per organization.
GitHub
Guardway’s GitHub integration scans connected repositories to identify which LLM providers, models, and SDKs your codebase already depends on. Results feed into discovery dashboards across the platform.
Connect
| Field | Required | Notes |
|---|---|---|
| Personal Access Token | Yes | Classic GitHub PAT with repo and read:org scopes. Entered as a password field (placeholder ghp_...). |
- On success: the card flips to Connected, showing “Connected as {username}” and the connection timestamp.
- On failure: an inline toast shows Invalid token. The input stays populated so you can fix it.
- Any GitHub-side warnings (missing scopes, rate-limit hints) surface as individual warning toasts.
Connected state
- Status badge — Connected (icon) or Disconnected.
- Metadata — connected username and
connected_atdate. - Disconnect — destructive button that revokes Guardway’s use of the token.
Limits
- One GitHub PAT per organization at a time.
- No event filtering or per-repo routing today — the integration is used only for discovery.
- No separate “Test” button once connected; to revalidate, disconnect and re-add.
Coming soon
Slack
Push budget alerts, guardrail violations, and audit events into a channel.
PagerDuty
Page on-call when a gateway goes offline or a budget is exceeded.
Datadog / Grafana
Stream gateway metrics into your existing observability stack.
Jira / Linear
Open tickets from guardrail violations.