Temporal through Squiid

What Temporal is

Temporal is durable execution with a strong consistency model. Workflow code runs deterministically against an event history, and activities perform the side effects, so a worker crashing mid-workflow resumes exactly where it left off with all local state intact. Signals and queries let outside systems interact with a running workflow, timers can span months, and versioning lets you change workflow code while old executions are still in flight. Workers run in your own processes and poll the service for tasks, so your code and data stay where you put them.

It is the heavy option in this category and it is honest to say so. Temporal earns its place when a process must not be lost: payment settlement and reconciliation, multi-step order fulfilment, compliance workflows with human approval steps, or long agent orchestrations where losing state means redoing expensive work. For a weekend project, a queue is enough. The tooling is also mature: a CLI, a web UI showing every workflow's history, and replay testing against recorded executions.

Why connect it through Squiid

Temporal is on the Squiid roadmap. When it lands, Squiid will provision the Temporal Cloud namespace, hold the client certificates and API key, and route worker and client traffic through https://api.squiid.io/v1/temporal/... with Authorization: Bearer $SQUIID_API_KEY, with SDKs working by base URL swap (gateway convention). Actions and retained state will bill at Temporal's listed price on one Squiid invoice, and the mTLS credentials that would otherwise live in every worker's environment stay with Squiid. Namespaces separate environments, which keeps a staging workflow from consuming a production task queue.

• One account, one key, one bill, one dashboard. Temporal sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Temporal credentials. Your code carries SQUIID_API_KEY, so TEMPORAL_ADDRESS, TEMPORAL_NAMESPACE, TEMPORAL_API_KEY, TEMPORAL_TLS_CERT 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 Temporal 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 Temporal Cloud namespace
• Durable workflow state across crashes and restarts
• Signals, queries and long timers
• Workflow versioning for in-flight executions
• Temporal list pricing, no markup

How to connect Temporal

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 TEMPORAL_ADDRESS, TEMPORAL_NAMESPACE, TEMPORAL_API_KEY, TEMPORAL_TLS_CERT
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

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

Pricing through Squiid

Temporal Cloud charges per action plus retained state storage and support tier, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Temporal usage, with no markup and no per-request margin.

Temporal 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 Temporal 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: workers run in your own infrastructure already, so leaving means pointing them at a namespace in your own Temporal Cloud account. Squiid never owns your code, your schema or your domain, and the gateway speaks Temporal'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

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