Inngest through Squiid

What Inngest is

Inngest turns a normal function into a durable workflow. You send an event, and the function runs as a series of steps, each of which is retried on failure and remembered once it succeeds, so a crash halfway through does not repeat the work already done. Sleeps can last days, waitForEvent pauses until something else happens, and concurrency, throttling and debounce controls are declared on the function rather than implemented by hand. A local dev server replays events with full step traces. Functions can also fan out across many events and batch them, which keeps per-item processing efficient without custom queue code.

This fits AI workloads unusually well. A generation pipeline that calls a model, stores a file, sends an email and updates a record is exactly the shape that breaks on a serverless timeout or a rate limit, and where retrying the whole thing means paying for the model call twice. Step memoization means a retry resumes after the expensive part, and concurrency limits keep a burst of jobs from exceeding a provider's rate limit. Observability is part of the product, with every run showing which step failed and what it received.

Why connect it through Squiid

Inngest is on the Squiid roadmap. When it is connected, Squiid will provision the environment, hold the event and signing keys, and route calls through https://api.squiid.io/v1/inngest/... with Authorization: Bearer $SQUIID_API_KEY, with the SDK working by base URL swap (gateway convention). Runs and steps will bill at Inngest's listed price on one Squiid invoice, alongside the model providers the workflow is orchestrating.

• One account, one key, one bill, one dashboard. Inngest sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Inngest credentials. Your code carries SQUIID_API_KEY, so INNGEST_EVENT_KEY, INNGEST_SIGNING_KEY, INNGEST_ENV 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 Inngest 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 Inngest environment with keys held by Squiid
• Durable steps with independent retries
• Sleeps, waits and event-driven cancellation
• Concurrency and throttling per function
• Inngest list pricing, no markup

How to connect Inngest

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 INNGEST_EVENT_KEY, INNGEST_SIGNING_KEY, INNGEST_ENV
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

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

Pricing through Squiid

Inngest charges a plan fee plus runs and steps executed above the included allowance, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Inngest usage, with no markup and no per-request margin.

Inngest 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 Inngest 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: functions are redeployed from your source and re-registered against your own Inngest account. Squiid never owns your code, your schema or your domain, and the gateway speaks Inngest'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

Inngest 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 Inngest 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.