Trigger.dev through Squiid

What Trigger.dev is

Trigger.dev runs your background jobs on its own infrastructure so serverless timeouts stop being a constraint. Tasks are plain TypeScript functions deployed from your repository, invoked from your app or on a schedule, with retries, concurrency keys, queues and idempotency built in. Realtime run status can be streamed into your interface, and the dashboard shows each run's logs, duration and failure reason without you building an admin page for it. Version control is built into deployment, so a run records which version of the task code executed it.

For AI-coded products this is the answer to the most common architectural complaint: the model call takes ninety seconds and the host kills the request at thirty. Video generation, document processing, batch embedding, long agent loops and scheduled report generation all move here, while the web app keeps returning immediately and shows progress from the run status. Checkpointing and resumable runs also keep a long job from restarting from zero after an infrastructure event. It also removes the temptation to fake background work with a fire-and-forget promise, which quietly loses jobs when the instance recycles.

Why connect it through Squiid

Trigger.dev is on the Squiid roadmap. When it is connected, Squiid will provision the project, hold the API key and route calls through https://api.squiid.io/v1/trigger-dev/... with Authorization: Bearer $SQUIID_API_KEY, with the SDK working by base URL swap (gateway convention). Compute and plan cost will bill at Trigger.dev's listed price on one Squiid invoice, which keeps the background half of the system on the same bill as the providers those jobs call. Concurrency keys per user or per tenant prevent one heavy customer from starving everyone else's jobs.

• One account, one key, one bill, one dashboard. Trigger.dev sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Trigger.dev credentials. Your code carries SQUIID_API_KEY, so TRIGGER_API_KEY, TRIGGER_PROJECT_ID, TRIGGER_SECRET_KEY never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what Trigger.dev costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• A provisioned Trigger.dev project with keys held by Squiid
• TypeScript tasks with no execution timeout
• Retries, queues and concurrency controls
• Run dashboard with logs and realtime status
• Trigger.dev list pricing, no markup

How to connect Trigger.dev

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces TRIGGER_API_KEY, TRIGGER_PROJECT_ID, TRIGGER_SECRET_KEY
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/trigger-dev/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

Trigger.dev charges a plan fee plus compute time consumed by runs, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Trigger.dev usage, with no markup and no per-request margin.

Trigger.dev has no subscription attached on Squiid today. If a plan is required for a feature you need, it passes through at the provider’s listed price with no Squiid fee.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so Trigger.dev usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Export: tasks are redeployed from your source into a project in your own Trigger.dev account. Squiid never owns your code, your schema or your domain, and the gateway speaks Trigger.dev's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

Trigger.dev through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on Trigger.dev usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.