Skip to main content
Your license comes with a plan. The Engine applies the plan’s limits to all traffic it receives. Plans don’t charge per thread or per token, and don’t cap how many threads you create. How much history you can keep depends on your own PostgreSQL storage.

When you reach a limit

Requests over the limit get 429 Too Many Requests. Short bursts above your requests-per-second limit are rejected until traffic drops. Once a monthly bandwidth allowance is used up, requests are rejected until the next month starts or your plan changes. People signed in to the dashboard aren’t affected by the requests-per-second limit, so you can still investigate while integrations are being throttled. Dashboard traffic does count toward bandwidth. Sessions opened with Sign in with API key are limited like the key itself. Plan changes reach a running Engine within a few minutes. You don’t need to restart it.

If the Engine can’t reach Threadify

A running Engine keeps working with its last known plan if it briefly can’t reach Threadify’s licensing service. It needs to verify the license when it starts, so a restart during an outage will fail until the connection is back.