Durable Workflow Orchestration
How do I contact Temporal sales for Enterprise/Mission Critical, and what should we prepare (APS/Actions, retention, regions, SSO/SAML, SLA)?
6 min read
Quick Answer: You can contact Temporal sales for Enterprise or Mission Critical needs through the Get in touch or Get Cloud forms, or by talking directly with our team after a Community or product call. To move fast, come prepared with rough numbers for Actions per second (APS), data retention needs, regions, SSO/SAML requirements, and uptime/SLA expectations.
Frequently Asked Questions
How do I contact Temporal sales for Enterprise or Mission Critical workloads?
Short Answer: Use the Temporal contact form or the Get Cloud flow and indicate that you’re interested in Enterprise / Mission Critical usage.
Expanded Explanation:
If you already know you need Temporal for critical workloads (payments, customer data, AI pipelines, etc.), the fastest path is to reach out directly to the Temporal team. The public forms route you to sales, solutions engineering, and product so we can quickly qualify your needs and propose the right Temporal Cloud or self-hosted support plan.
You can also begin from open source, then engage sales once you’re ready to move production or mission-critical traffic to Temporal Cloud. Either way, the earlier we understand your reliability, compliance, and scaling requirements, the better we can shape a deployment that won’t hit a wall 6–12 months in.
Key Takeaways:
- Start with the contact or Get Cloud forms and select Enterprise / Mission Critical.
- Early conversations help align on reliability, scale, and security before you move critical workflows into production.
What should we prepare before talking to Temporal sales (APS/Actions, retention, regions, SSO/SAML, SLA)?
Short Answer: Come with rough estimates for your peak Actions per second, data retention window, preferred regions, identity/SSO setup, and any uptime/SLA or compliance constraints.
Expanded Explanation:
Temporal is built to handle demanding workloads—high APS, long-running Workflows, strict compliance, and aggressive SLAs. To size and design the right Temporal Cloud configuration, we don’t need perfect numbers, just realistic ranges and expectations. Think in orders of magnitude, not exact counts.
The more clarity you have on Actions per second, data retention, regions, SSO/SAML, and SLA expectations, the faster we can move from “interesting technology” to a concrete deployment plan. These inputs drive everything from multi-region setup and high-availability posture to cost modeling and integration timelines with your existing identity and observability stack.
Steps:
- Estimate your current and near-future Actions per second (APS) and total Workflows.
- Decide how long you need Workflow and event history retained for debugging, audit, or compliance.
- List preferred cloud regions, identity providers (for SSO/SAML), and any required uptime, RPO, and RTO targets.
How should we estimate APS/Actions and scale needs for Temporal Cloud?
Short Answer: Treat APS (Actions per second) as an approximation of how many Workflow and Activity steps you’ll execute per second under normal and peak load, then add headroom for growth.
Expanded Explanation:
Temporal’s unit of scale is “Actions”—things like starting a Workflow, scheduling an Activity, completing an Activity, firing timers, recording signals, and so on. Temporal Cloud is designed to automatically scale to very high volumes (300k Actions/second and beyond), but we still need to understand your order of magnitude so we can recommend the right setup and pricing model.
Don’t overcomplicate this. Look at existing systems: orders per second, payment attempts per second, user signups per second, jobs per second in your current orchestrator or queues. Then translate those into Temporal steps: for example, each order might trigger a Workflow and several Activities (validate, charge card, reserve inventory, notify systems). We’ll help you map that into Actions in the sales or solutions engineering conversation.
Comparison Snapshot:
- Low/Moderate Scale (up to ~1k Actions/s): Typical for early adoption, internal tools, or a few core business workflows.
- High Scale (10k–100k+ Actions/s): Transactional workloads like payments, order fulfillment, fleet management, or AI pipelines across many tenants.
- Best for: Share your current and projected ranges; we’ll design for current reality with a path to your expected future scale.
How do regions, SSO/SAML, and SLA/HA expectations affect an Enterprise/Mission Critical deployment?
Short Answer: Your region choices, identity setup (SSO/SAML), and uptime/SLA targets shape the Temporal Cloud configuration, including which regions we deploy in, how we set up access and security, and what high-availability and disaster recovery posture we recommend.
Expanded Explanation:
Temporal Cloud is “reliable, scalable, serverless Temporal in 11+ regions,” with built-in replication and disaster recovery to help you meet uptime and compliance goals. For Enterprise and Mission Critical workloads, region and HA choices are rarely “just infrastructure”—they’re tied to data residency, latency to your Workers, and your regulatory environment.
SSO/SAML requirements determine how your engineers, operators, and support teams authenticate into Temporal Web UI and related tools. SLA requirements (uptime, RPO, RTO) influence whether you need multi-region failover configurations and how aggressive your recovery objectives should be. The sales and solutions engineering teams use this information to map you to the right service tier and architecture.
What You Need:
- A list of preferred and/or required regions and any data residency constraints (e.g., EU-only, US-only, specific cloud provider regions).
- Your identity provider details (e.g., Okta, Azure AD) and SSO/SAML expectations, plus target uptime/SLA and DR requirements (e.g., 99.9%+, specific RPO/RTO).
How should we think about retention, pricing, and long-term strategy for Enterprise/Mission Critical with Temporal?
Short Answer: Decide how long you need Workflow histories retained for debugging, audit, or compliance, then work with Temporal sales to align retention and scale with a consumption-based pricing model that fits your growth curve.
Expanded Explanation:
Temporal’s core advantage is durable execution history: every Workflow step is recorded so you can replay, inspect, and rewind. For critical systems—moving money, provisioning infrastructure, managing AI agents—this history is often essential: you want to know exactly what happened and why, even months later. At the same time, retention has cost and operational implications.
Temporal Cloud uses a consumption-based model, so you avoid over-provisioning databases or hardware just to be “safe.” Instead, we right-size around your Actions volume and history retention window. For compliance-heavy environments, sales and solutions engineering can help reconcile audit requirements with practical retention policies (e.g., keeping full histories for X days and summarized data longer). The goal is simple: no lost progress, no orphaned processes, and clear traceability when something goes wrong.
Why It Matters:
- The right retention and pricing model lets you keep the visibility you need—full histories, replay, and debugging—without paying for oversized infrastructure you don’t use.
- A clear long-term strategy (scale, regions, retention, SLAs) prevents painful migrations later and lets you safely grow from initial adoption to core, mission-critical workloads.
Quick Recap
To contact Temporal sales for Enterprise or Mission Critical use, start with the contact or Get Cloud forms and indicate your need for high reliability and scale. Come prepared with rough estimates for APS/Actions, data retention windows, required regions, SSO/SAML setup, and uptime/SLA expectations. Those inputs allow the Temporal team to propose a Temporal Cloud configuration—with built-in high availability, replication, and consumption-based pricing—that fits both your current workloads and your long-term strategy.