- Integrations connect source control, chat, work tracking and incident tools at the organization level.
- Log sources send logs, metrics and traces to Sazabi.
- MCP connectors give the Sazabi agent tools from an external service.
- Sandbox CLIs give the Sazabi agent command-line tools in its sandbox.
Integrations
Integrations are organization-level connections you set up under Settings > Integrations. They give Sazabi features rather than data: code search and pull requests from source control, the agent in your chat tool, issues in your work tracker, incident notifications in your on-call tool, and issue fixes handed to your coding agent. Each page covers setup, the features it turns on, and how to verify it. To hand an issue to a cloud agent, choose Fix on the issue. The agent works in your repository and opens a pull request, and Sazabi follows the attempt in the issue thread.- Better Stack
- Bitbucket
- Capy
- Claude Agent
- Codex
- Cursor
- Devin
- Discord
- GitCafe
- GitHub
- Hoplite
- incident.io
- Jira
- Linear
- Microsoft Teams
- PagerDuty
- Replicas
- Rootly
- Slack
- Splunk On-Call
- Tembo
- Warp Oz
Log sources
A log source is where your data comes from. Sazabi supports two ways to set one up. For a decision guide, see Choose a path.Native: connect your account
Native log sources use the connect-your-account path: authorize a supported platform account and Sazabi configures forwarding for you. There is no collector to run. Some of these vendors also have a manual path; use that one instead when you run your own collector or want explicit control over what you forward.- Amazon VPC Flow Logs
- AWS CloudTrail
- AWS CloudWatch
- AWS WAF
- Cloudflare
- Convex
- DigitalOcean
- Google Cloud
- Plain
- PostHog
- Render
- Sentry
- Vercel
Manual: send to an endpoint
Manual log sources use the send-to-an-endpoint path: Sazabi provides a keyed intake URL, and you configure your platform, collector, SDK, or agent to send to it. Copy the URL from Settings > Log streams (the public key is embedded in the URL). Use this path when you run your own collectors, instrument application code, or your platform is not in the native list. Manual describes the setup, not the delivery frequency: once configured, your sender can stream logs continuously. Telemetry from coding agents such as Claude Code, Codex, and Cursor uses the manual path and has its own coding agent telemetry list.- Amazon VPC Flow Logs
- Auth0
- AWS API Gateway
- AWS CloudTrail
- AWS CloudWatch
- AWS GuardDuty
- AWS WAF
- Buildkite
- Cloudflare
- Cloudflare Workers
- Convex
- Datadog Agent
- Daytona
- DigitalOcean
- Doppler
- E2B
- Elastic Cloud
- evlog
- Fluent Bit
- Fly.io
- GitHub Actions
- GitHub Audit Log
- GitHub Webhooks
- Google Cloud
- Grafana Alloy
- HashiCorp Vault
- Inngest
- Jamf Pro
- Jenkins
- LangChain
- Linear Webhooks
- Linux auditd
- Mastra
- Modal
- Neon
- Netlify
- New Relic
- New Relic Browser
- Northflank
- Okta
- OpenRouter
- OpenTelemetry
- OpenTelemetry Collector
- OpenTelemetry Metrics
- OpenTelemetry Traces
- osquery
- Palo Alto Networks
- Plain
- Porter
- PostHog
- PostHog SDK
- Prometheus
- Railway
- Render
- Respan
- RunsOn
- Sazabi Browser SDK
- Sazabi React Native SDK
- SentinelOne
- Sentry
- Sentry SDK
- Shopify Webhooks
- SigNoz
- Stripe Webhooks
- Supabase
- Tailscale
- Temporal
- Trigger.dev
- Unkey
- Vector
- Vercel
- WarpBuild
- Webhook Events
- WorkOS
- Zscaler
MCP connectors
An MCP connector gives the Sazabi agent tools from an external service through the Model Context Protocol, so the agent can act in that service during an investigation. Configure connectors in the dashboard under Settings > MCP connectors. To use Sazabi from your own coding agent instead, see Connect your coding agent.- AgentCat
- Airbyte
- Arize AX
- Atlassian
- Attio
- Autumn
- AWS
- Axiom
- Better Stack
- Braintrust
- Calendly
- Cekura
- Circleback
- Clay
- Clerk
- Cloudflare
- Cloudflare (API token)
- Composio
- Context.dev
- cve.now
- Datadog
- DeepWiki
- down.guide
- Drata
- Elastic Cloud
- Exa
- GitGuardian
- Google Cloud (GCP)
- Google Security Operations
- Grafana Cloud
- Granola
- GrowthBook
- Happenstance
- Have I Been Pwned
- Herd
- Honeycomb
- incident.io
- Intercom
- Langfuse
- LangSmith
- Linear
- Mercury
- Mobbin
- Neon
- Notion
- PagerDuty
- Plain
- Plain (API key)
- PlanetScale
- Porter
- PostHog
- Pydantic Logfire
- Pylon
- Railway
- Render
- RentAHuman
- Replicas
- Resend
- Respan
- Rivet
- Secureframe
- Semgrep
- Sentry
- SigNoz
- Socket
- Stripe MCP
- Supabase
- Superhuman
- The Context Company
- Tines
- Vanta
- VirusTotal
- Wiz
- WorkOS
- X
Sandbox CLIs
The Sazabi agent runs commands in a sandbox. A sandbox CLI is a command-line tool baked into that sandbox, with a place to connect the tool’s credentials; connecting one creates a CLI connection. Configure the sandbox in the dashboard under Settings > Sandbox CLIs. For how the sandbox works, see Set up the sandbox.- 1Password
- Aiven
- Argo CD
- Arize
- AWS
- Axiom
- Azure
- Bitbucket
- Braintrust
- Checkly
- Clerk
- ClickHouse
- Cloudflare (cf)
- CodeRabbit
- Codex
- Context.dev
- Convex
- Cursor
- Dagster
- Datadog
- DBOS Cloud
- Deepsec
- Devin
- DigitalOcean
- Doppler
- ElevenLabs
- Fly.io
- Gemini
- GitHub
- Google Cloud
- Google Drive
- Graphite
- Heroku
- Inngest
- Kubernetes
- Langfuse
- LangSmith
- Mercury
- MongoDB Atlas
- MongoDB Shell
- MySQL
- Netlify
- Notion
- OpenCode
- PlanetScale
- Porter
- Postgres
- PostHog
- Railway
- Redis
- Render
- Respan
- RunPod
- Sentry
- Stream
- Stripe
- Supabase
- Tailscale
- Temporal
- Terraform
- Twilio
- Vercel
- Wrangler
- X