Temporal Self-Hosted
Orchestrate durable application workflows with a customer-operated Temporal Service.
5 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
Temporal security patches and namespace permissions
The patch includes security fixes and requires namespace Write access for ValidateWorkerDeploymentVersionComputeConfig.
Scope: Temporal 1.32.2; corresponding security patches are available on the 1.31 and 1.30 lines as 1.31.5 and 1.30.9.
The permission change affects callers of that API. The release notes do not establish a shared affected range for every security fix.
Action: Patch the deployed supported line and review namespace authorizations before upgrading.
Primary source · Temporal 1.31 security patch · Temporal 1.30 security patch · Reviewed 2026-11-17
What lands where
Supplied by
Vendor or project
Production Docker/Kubernetes or manual server deployment with persistence and application workers
Runs in
Documented customer environment
Customer-operated Temporal Service, persistence/visibility stores and worker services
- AWS: Customer cloud account
- AWS
Servers / containers
Operated by
Your team
Customer configures service security, persistence, worker capacity, monitoring, upgrades and disaster recovery.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Temporal server Helm chart on Amazon EKS ↗ · Source checked 2026-11-12
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Production Docker/Kubernetes or manual server deployment with persistence and application workers |
|---|---|
| Infrastructure | Servers / containers Reviewed self-hosted Temporal Service requires long-lived services and persistence. Application workers are separate customer workloads; their possible hosting models do not change this service classification. |
| Licensing model | Open Source / Open Core This listing covers the MIT-licensed self-hosted Temporal Server. The separately hosted Temporal Cloud service does not turn the listed open-source server into open-core. |
| License | MIT-licensed Temporal Server; managed Cloud offering is separate |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
5 of 12 fields researched (42%) · 4 documented · 1 unresolved. Evidence coverage is not a feature score.
- Single sign-on
AvailableEvidence and scope for Single sign-on
The self-hosted Web UI supports OIDC login when authentication is enabled. UI login does not by itself secure every Temporal service/API; configure service authentication and authorization separately.
Temporal Web UI only; not automatic service/worker access control · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The official deployment guide links samples-server Compose configurations with persistence and visibility services. Use the server image and explicitly manage schema upgrades; auto-setup/evaluation workflows are separate.
Upstream self-hosted deployment; not a provider support or production-readiness certification · Source ↗ · Deployment artifact ↗ (repository default branch (moving; select matching application release)) · Reviewed 2026-11-14
Documented · Editor reviewed.
- Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing
The self-hosted checklist requires workload testing and explicit persistence, visibility, service-role and shard planning rather than a universal CPU/RAM/storage minimum. Application workers execute separately from the Temporal service. Size workflow/history growth, task/activity rate, retention, database I/O and redundancy; 100 users and 1 TB alone do not specify capacity.
Official production planning requirements; numeric whole-stack and worker sizing remains unconfirmed · Source ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
The reviewed upstream application uses MIT licence. Review the licence and bundled-component notices for your use and distribution. Hosting, databases, delivery services, commercial support and any separately licensed additions have their own costs and terms; no hosted-plan price is treated as a self-hosted quote.
Temporal v1.32.2 server; SDKs, UI and provider packages have their own distributions; software terms only, excluding infrastructure and operations · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
The publisher-designated GitHub release checked was v1.32.2, published 2026-11-02. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package.
Upstream temporalio/temporal release record; commercial editions and deployment packages may differ · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
Show all fields (7 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
Scope & considerations
The local CLI development server is not a production installation. Self-hosted Temporal requires substantial operational ownership; the production guide notes that RBAC and audit logging are not provided out of the box. This entry excludes Temporal Cloud and does not describe a packaged end-user workflow application. Temporal v1.32.2 includes security fixes and changes ValidateWorkerDeploymentVersionComputeConfig to require namespace Write access; matching security patches are available as v1.31.5 and v1.30.9. Review namespace permissions before upgrading.
Category fit
- Workflow orchestration
- Developer-oriented durable workflow execution and retry/state orchestration; application workers and code must be supplied.
Compare within Workflow orchestration
- Apache AirflowWorkflow orchestration platform for scheduling and monitoring data pipelines and other task workflows authored in Python or supported non-Python formats.
- AWS
- DigitalOcean
- Camunda 8 Self-ManagedCommercial self-managed process orchestration and workflow automation platform.
- AWS
- Azure
- Google Cloud
- Dagster OSSData orchestration platform for developing, scheduling and observing data-asset workflows.
- AWS
- HashiCorp Nomad EnterpriseCommercial workload scheduler and orchestrator deployed as a multi-node cluster on customer cloud virtual machines.
- AWS
- Azure
- Google Cloud
- Kestra Self-HostedSelf-hosted orchestration platform for scheduled and event-driven workflows across data, infrastructure and applications.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Prefect ServerSelf-hosted workflow server and Python framework for resilient task and data pipelines.
- AWS
- Azure
- Google Cloud
- Northflank
These products address related workflows; read their category-fit notes before comparing scope. See all of Workflow orchestration →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Production self-hosted service guide ↗docs.temporal.io
- Production responsibilities and limitations ↗docs.temporal.io
- Official server license ↗github.com
- Durable workflow platform ↗docs.temporal.io
- Temporal v1.32.2 security and permission changes ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Temporal server Helm chart on Amazon EKS ↗ · AWS
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The upstream Temporal server Helm chart explicitly identifies AWS EKS as a target cluster. The current V3 chart deploys server components and requires separately provisioned persistence; it no longer installs database sub-charts. Review schema management, credentials, access controls and production operations. This is separate from Temporal Cloud.
- Temporal server Helm chart on Amazon EKS ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked