The systems Nightjar composes with.
GitHub, GitLab, Jenkins, Datadog, PagerDuty — each partner maps to one or more agents in the fleet. Source control feeds the review lane, CI gates the ship lane, and observability drives the intake queue. Integrations don’t act; they route signals to the right agent.
How integrations compose · 01
Integrations don’t run the fleet. They route signals to the right agent.
Every integration in this directory maps to one or more agents in the fleet. Source hosts feed the PR reviewer lane; CI providers gate the fix shipper lane; observability and on-call platforms drive the issue wrangler queue.
The same handoff discipline that runs between agents runs between Nightjar and each partner system. Agents stay in their own lanes; humans stay in the merge seat.
The directory · 02
Five partners · five responsibilities covered.
Source control and CI on one half of the diagram, observability and on-call on the other. Each card below names exactly which agents in the fleet benefit from that partner.
Wire Nightjar into the systems your team already runs.
Pilot scope covers the partners we can light up on day one: source control, CI, observability, and the on-call rotation. Join the waitlist and we’ll sketch a wiring plan against your fleet.