temporal
The official Temporal server image — a durable execution platform that runs long-lived, fault-tolerant workflows written as ordinary code, with automatic retries and state recovery.
What is Temporal?
The Temporal image packages the Temporal server, a durable execution platform that lets developers write long-running business logic as ordinary code in Go, Java, Python, TypeScript, or .NET while the platform handles retries, timeouts, state persistence, and recovery from failures. A Temporal deployment consists of several services — frontend, history, matching, and worker — backed by a persistence store such as PostgreSQL, MySQL, or Cassandra, with companion images for the Web UI and admin tools. It is used by application and platform teams to orchestrate payment flows, data pipelines, infrastructure automation, and AI agent workflows, and to run a reproducible, version-pinned Temporal cluster on Kubernetes.
What is Echo's Temporal image?
Echo's Temporal image is a hardened build of Temporal on Echo's hardened base. Echo images are designed to be a drop-in replacement: swap the image reference in your Dockerfile or deployment manifest and CVEs go to zero without disrupting your namespaces, dynamic configuration, persistence settings, and worker connectivity. Every image is tested across clouds, image use cases, and deployment targets. Echo ships every image in two variants:
- Distroless variant — optimized for runtime use, with the smallest possible attack surface
- Default variant — includes essential build tools, package managers, and shells for teams that need operational access
For production Temporal deployments, the distroless variant keeps all runtime operations — workflow scheduling, task queue matching, history persistence, timers, and retries — fully intact while minimizing exposure; the default variant suits application and platform teams that need shell access for using tctl or the Temporal CLI, inspecting workflows, or debugging task queues.
What is the difference between Echo's Temporal image and the public Temporal image?
Public Temporal images ship on bases that include OS-level tooling convenient for development but which contribute CVEs that accumulate on a workflow orchestration server used in production. Temporal images run continuously with access to workflow state, business payloads, and database and TLS credentials. OS-level CVEs in the base image — particularly in libraries such as openssl, zlib, and libc, along with the Go runtime dependencies — create exploitable paths that bypass application-layer controls entirely, allowing attackers to move from a network-reachable service to host-level access. For teams running Temporal across many environments, the image is also a steady source of scanner noise in the CI pipeline — every package in the base becomes a finding your security team must triage, even when none of it is reachable from the service. Echo's build retains everything Temporal needs for workflow scheduling, task queue matching, history persistence, timers, and retries while removing the packages that don't belong in a production Temporal workflow orchestration server. As we covered in our post on how to protect your company from software supply chain attacks, long-running services that hold sensitive data and listen on the network are among the widest attack surfaces in the container stack. Echo commits to a 7-day SLA for critical and high severity vulnerabilities, and 10 days for medium, low, and unknown — with vulnerabilities triaged within 24 hours. Echo images are recognized by all major scanners and mirrored to all major registries, so they fit into existing pipelines without changing your registry, scanner, or runtime tooling.
FAQ
Can I replace my Temporal image with Echo's Temporal image?
Yes. Echo's Temporal image is a drop-in replacement. Update the FROM line in your Dockerfile and your workloads keep running. namespaces, dynamic config, persistence drivers, SDK worker connections, and the Web UI all continue to work without changes to your workflow code or cluster manifests.
Is Echo's Temporal image FIPS-validated?
Yes. Echo's FIPS-validated images use cryptographic modules with an active FIPS 140-3 CMVP certificate, making them fit for federal use — unlike FIPS-compliant images that haven't been validated. This matters for teams running Temporal workloads inside FedRAMP boundaries, where a workflow orchestration server that coordinates long-running workflows and persists their state across failures must meet cryptographic requirements across the full stack — including the OpenSSL and TLS libraries bundled with the Temporal image.
What is Echo's vulnerability management SLA on the Temporal image?
Echo commits to a 7-day SLA for critical and high severity vulnerabilities, and 10 days for medium, low, and unknown — with vulnerabilities triaged within 24 hours. Patches are mirrored automatically into your private registry so you're always running a clean version — critical for a long-running service that holds workflow state, business payloads, and database and TLS credentials and is reachable over the network.
Is Echo's Temporal image distroless?
Echo ships every image in two variants: a distroless variant optimized for runtime use, and a default variant that includes essential build tools, package managers, and shells. For production Temporal deployments, the distroless variant is the leaner, more secure choice; for application and platform teams that need shell access for using tctl or the Temporal CLI, inspecting workflows, or debugging task queues, the default variant is the right fit.
How does Echo achieve such a drastic CVE reduction in Temporal?
Echo's Temporal image is built from source with only the absolute essentials needed to run the Temporal workflow orchestration server, which significantly shrinks the attack surface. Echo also patches aggressively over time, with backports available so you can stay on the Temporal version your applications and their dependencies are certified against — avoiding a disruptive upgrade forced purely by OS-level vulnerabilities in the base image rather than by your own requirements.
Will Echo's Temporal image help us achieve FedRAMP?
Yes. The hard parts of FedRAMP — managing vulnerabilities, applying fixes, and using FIPS-validated cryptography — are baked into Echo images, including STIG-hardened configuration and ConMon/POA&M-ready reporting. For application and platform teams running Temporal under an ATO — whether that's payment orchestration, data pipeline control, or infrastructure automation handling government data — Echo's hardened Temporal image keeps the workflow orchestration server layer in-boundary and compliant without requiring custom hardening scripts or manual base image patching between compliance cycles.
.avif)