Integrations
Integrations — today and next
Zentro is useful without a wall of logos: you can run incidents, runbooks, and guarded automations on day one. Below is what works now versus what we expect to add as teams adopt the platform.
Available today
Configure these from the console after sign-in. Nothing here sends data to vendors until you set URLs and keys.
HTTP alert ingest
Bearer-token ingest to open or dedupe incidents from your own webhooks and scripts (paid-gated with Supabase).
Settings →SIEM & EDR shapes
Normalize common alert payloads into Zentro incidents. Vendor-specific OAuth connectors are planned, not implied as live.
API docs →Reasoning & robot HTTP endpoints
Optional internal endpoints for extended reasoning and guarded remediation execution, health-checked from the console.
Connectors →Supabase & billing
Accounts, incidents, services, audit append, and Lemon Squeezy sync when you configure keys.
Console →
Roadmap (vendor integrations)
Names below are targets for first-party connectors or supported webhooks — not live product claims. Shipping order follows customer demand and safety review.
Monitoring
- PlannedDatadog
- PlannedPrometheus / Grafana Alerting
- PlannedNew Relic
Chat & paging
- PlannedSlack
- PlannedMicrosoft Teams
- PlannedPagerDuty (events)
Cloud control planes
- PlannedAWS
- PlannedAzure
- PlannedGCP
ITSM / tickets
- PlannedJira
- PlannedServiceNow
- PlannedLinear (change tasks)
Security & exposure
- PlannedSplunk (webhook)
- PlannedMicrosoft Sentinel
- PlannedCrowdStrike Falcon
- PlannedQualys / Tenable findings
How users connect vendors
- Create an ingest token or configure an internal HTTP endpoint from Settings.
- Send alert, deploy, or remediation payloads with service and environment context.
- Use approvals and audit capture so high-impact actions stay reviewable.
Want a vendor prioritized? hi@zentro.run with your stack and incident volume — it helps us sequence OAuth scopes, webhook shapes, and audit requirements.