8,822 calls to GET /v1/tickets and 8,815 calls to GET /v1/events in three days. Together they were 88% of every request my tracker's API served, from an app used by one person and two agents.

The constraint: the agents have to notice new work within seconds, and an idle agent should cost nothing.

I'm Panth, and I lead the software team at Oizom. This is from ticket-tracker , my open-source board, which my agents work from. Its plan has a section on what the app costs, and this post is the part of it about the agents: they used to poll, and now they wake.

What the polling cost

The numbers are from 23 to 26 September 2026.

What Measured

Requests to the API function 41,515 in 3 days

Billable vCPU-seconds that were the API 11,963 of 13,775 (87%)

Orchestrator polling 8,822 tickets + 8,815 events = 88% of requests

Time per call about 250 ms

Two orchestrator loops ran every 30 seconds or so.…