Temporal Cloud alternatives: self-hosted Temporal, run by engineers
Self-hosted Temporal with the PostgreSQL underneath it, run 24/7 by engineers in your environment.
45 minutes with an engineer: we review your workload and sketch the design.
- ✓Operated by AceMQ
- ✓Temporal on PostgreSQL
Temporal Cloud bills Actions and storage on top of a plan: pay as you go, Business from $500 a month, Enterprise and Mission Critical by quote. The alternative is self-hosted Temporal, which is open source but needs a database underneath. OSStend runs Temporal on managed PostgreSQL in your environment, priced per design.
- PostgreSQL
- MySQL
- MongoDB
- Redis
- Valkey
- OpenSearch
- Kafka
- RabbitMQ
- AWS
- Google Cloud
- Azure
- Kubernetes
- OpenShift
- Prometheus
- Grafana
- Datadog
- Dynatrace
- Splunk
Temporal Cloud and OSStend at a glance
Temporal Cloud is Temporal's own usage-billed service. OSStend runs the open source Temporal server on managed PostgreSQL, in your environment.
| OSStend | Temporal Cloud | |
|---|---|---|
| Model | Self-hosted Temporal on managed PostgreSQL, run for you | Managed service by plan (Temporal pricing) |
| Where it runs | In your environment, such as your cloud account or your data center | Temporal Cloud, multi-cloud and multi-region (Temporal pricing) |
| Pricing | Quoted per design. See pricing | Per million Actions and per GB-hour of storage, plus plan support fees |
| Run by | OSStend engineers, 24/7 | Temporal |
Source: Temporal pricing, checked 17 Nov 2026.
How much does Temporal Cloud cost?
Temporal Cloud has a pay-as-you-go plan with no base fee, a Business plan from $500 a month, and Enterprise and Mission Critical by quote. Usage is billed in Actions per million and storage per GB-hour, with volume tiers.
| Plan | Base | Included | Support listed |
|---|---|---|---|
| Pay as you go | $0 a month | 500 APS On-Demand capacity, 99.9% SLA (99.99% HA options) | Support costs 10% of usage |
| Business | From $500 a month, or 10% of monthly usage if greater | 2.5M Actions, 2.5 GB Active Storage, 100 GB Retained Storage | P0 response 2 business hours |
| Enterprise | Contact sales | 10M Actions, 10 GB Active, 400 GB Retained | 24/7, P0 response under 30 minutes |
| Mission Critical | Contact sales | As Enterprise, plus a dedicated Platform Architect | P0 response under 15 minutes |
Source: Temporal pricing, checked 17 Nov 2026. The page's billing FAQ also mentions an Essentials plan that is not in its plan list, so it is not shown here. A startup program offers $6,000 in credits for startups with under $30M in funding; the trial is $150 in credits for 90 days.
| Actions in a month (per million) | List price |
|---|---|
| First 5M | $50 |
| Next 5M | $45 |
| Next 10M | $40 |
| Next 30M | $35 |
| Next 50M | $30 |
| Next 100M | $25 |
| Over 200M | Contact sales |
Source: Temporal pricing, checked 17 Nov 2026. Storage overage is $0.042 per GB-hour Active and $0.00105 per GB-hour Retained; 1 GB of allocation is 744 GB-hours. Arithmetic, not a quote: 10 million Actions at these rates is $250 plus $225, or $475, before included allowances, the plan minimum and storage.
Why do teams look for a Temporal Cloud alternative?
The usual reasons are the Actions bill as workflows grow, a plan minimum, and workflow history that has to stay in your own environment. Self-hosting removes the per-Action fee and moves the work to a database and an operations team.
| Area and managed service | Documented limit | What OSStend does instead | Source |
|---|---|---|---|
| Billing follows volumeTemporal Cloud | Actions are billed per million with volume tiers from $50 down to $25, and storage is billed per GB-hour. | What OSStend does insteadA price for the design you sign off, not per Action. | Temporal pricing, checked 17 Nov 2026 ↗ |
| Plan minimum and supportTemporal Cloud | Business starts at $500 a month or 10% of usage if greater; pay as you go charges 10% of usage for support. | What OSStend does insteadSupport is part of the service. See [service levels](/service-levels). | Temporal pricing, checked 17 Nov 2026 ↗ |
| Where workflow data livesTemporal Cloud | Workflows and history run in Temporal Cloud, which the page describes as multi-cloud and multi-region without listing regions. | What OSStend does insteadRun in your environment, such as your cloud account or your data center. | Temporal pricing, checked 17 Nov 2026 ↗ |
What does self-hosted Temporal need?
Self-hosted Temporal needs a persistence database and a visibility store. PostgreSQL can be both, which is why OSStend runs Temporal on managed PostgreSQL.
- Temporal's persistence docs list Cassandra, PostgreSQL ("PostgreSQL 13.18, 14.15, 15.10 and 16.6") and MySQL as supported databases (Temporal docs, checked 17 Nov 2026).
- Advanced Visibility runs on PostgreSQL v12 or later with Temporal Server v1.20 or later, as well as MySQL, Elasticsearch, OpenSearch and SQLite (Temporal docs, checked 17 Nov 2026).
- The Temporal server is MIT licensed (GitHub, checked 17 Nov 2026). The software is free; the cluster, upgrades and schema migrations are what you operate.
OSStend runs the Temporal server and the managed PostgreSQL beneath it. See managed PostgreSQL for how that database is run.
From our on-call engineers: the Temporal limits you cannot change later
Two Temporal decisions are expensive to reverse: the history shard count, and how long a workflow's event history is allowed to grow. We settle both before go-live because the cost of changing them is a rebuild or a failed workflow.
- ✓Temporal documents that shard capacity is set at build time and cannot be adjusted later, and adding shards means building a new Temporal Service and migrating to it.
- ✓The service logs a warning at 10,240 events in a workflow's history and terminates the workflow beyond 51,200 events.
- ✓A workflow is also terminated beyond 2,000 updates or 10,000 signals in its history, so high-signal workflows need a plan.
- ✓Long-running workflows use Continue-As-New to close and restart with fresh history, and we make that a design rule rather than an emergency fix.
- ✓We watch persistence_requests, persistence_errors and persistence_latency first when throughput drops, and load-test with Temporal's Omes tool or our own workload before sizing.
Full comparison: OSStend and Temporal Cloud
OSStend is listed first. The Temporal Cloud column states only what its pricing page says, with the date checked.
| Factor | OSStend | Temporal Cloud |
|---|---|---|
| Good fit | Workflow data that must stay in your environment, steady high Action volume, a team that does not want to run Temporal and its database | Teams that want Temporal to run it, bursty or small usage, a startup with credits |
| Poor fit | A free trial or a card sign-up | Workflow history that cannot leave your environment |
| Where it runs | In your environment, such as your cloud account or your data center | Temporal Cloud (Temporal pricing) |
| Service levels | Written per plan. See service levels | Pay as you go lists a 99.9% SLA with 99.99% HA options; response targets by plan (Temporal pricing) |
| Pricing model | Price drivers on pricing, sized per design | Actions, storage and a support fee |
How we compared: Temporal's pricing page and docs, checked 17 Nov 2026. OSStend's price is set after a workload review.
How does OSStend run Temporal?
OSStend designs the Temporal cluster and its PostgreSQL around your workflow volume, then runs both: history retention, scaling, backups and version upgrades. The first step is a 45-minute workload review with an engineer: the current setup is reviewed, the design is sketched, and a price follows for that design.
There is no fixed menu here: the history retention, service sizing and upgrade dates your workload needs are written into the design you sign off before anything is built, and that design is what OSStend runs.
Contact us if
- ✓Workflow volume is steady and high enough that per-Action billing grows every month.
- ✓Workflow state must stay in your cloud account or data center.
- ✓You want Temporal and PostgreSQL run by one team to one written design.
Not a fit if
- ✕A small or bursty workload, or a team with credits: Temporal Cloud will cost less.
- ✕You want a free tier, a card sign-up or a self-serve console.
What other options are there?
Besides OSStend, the choice is between Temporal Cloud's plans and running the server yourself.
- Stay on Temporal Cloud and change plan.
- If the base fee, not the Action volume, is the problem, compare pay as you go with Business at your volume.
- Run Temporal yourself
- on PostgreSQL, MySQL or Cassandra, taking on upgrades, schema migrations and on-call.
- Aiven, Instaclustr and other platforms
- run databases such as PostgreSQL, but the Temporal server on top is still yours to run. See the alternatives hub.
How does moving off Temporal Cloud work?
The new Temporal cluster is built beside Temporal Cloud and workers are pointed at it in stages. Workflows already running finish where they started, and new ones start on the new cluster once it is verified.
Review
An engineer reviews the current setup: sizes, settings, modules or plugins, versions, traffic and where it must run.
Design
The cluster design is written and signed off before anything is built: size, topology, configs, versions and upgrade calendar.
Move
The new cluster runs beside the old one and stays current while the old service stays live. Traffic switches only when the new side is verified.
Run
Named engineers operate it 24/7: backups, patching, scaling and incident response, with upgrades on the customer's change calendar.
Questions about Temporal Cloud pricing and alternatives
These are the questions teams ask when they price Temporal Cloud.
How much does Temporal Cloud cost?
Pay as you go has no base fee and a support charge of 10% of usage; Business starts at $500 a month; Actions cost $50 per million for the first 5 million, falling to $25 (Temporal pricing, checked 17 Nov 2026).
Can Temporal run on PostgreSQL?
Yes. Temporal's docs list PostgreSQL for persistence and for Advanced Visibility (persistence, visibility, checked 17 Nov 2026). OSStend runs Temporal on managed PostgreSQL.
Is there a self-hosted Temporal service run for me?
Yes. OSStend runs Temporal and its PostgreSQL in your environment, such as your cloud account or your data center, to a design you sign off.
Is Temporal free to self-host?
The server is MIT licensed (GitHub, checked 17 Nov 2026). Running it still means infrastructure, upgrades and on-call.
When is Temporal Cloud the better choice?
When usage is small or bursty, you want the vendor to run it, or startup credits cover the bill.
Related pages
- PricingDatabase as a service pricing: dedicated, tailoredDatabase as a service pricing from OSStend: dedicated, tailored clusters priced by engine, size, SLA tier and location. Enterprise only, with no free tier.
- PostgreSQLManaged PostgreSQL service and Postgres hostingManaged PostgreSQL service, compared: how to choose between RDS, Aiven, Crunchy Bridge, Neon and a tailored cluster run 24/7 in your cloud or ours.
- Service levelsService levels: two tiers, a written SLAOSStend service levels: fully managed and co-managed tiers, what each one covers, who is on call and how incidents are handled, with a written SLA for each.
- OverviewAlternatives to the managed service you run todayAlternatives to Amazon RDS, ElastiCache, Amazon MQ, Confluent, Instaclustr and MongoDB Atlas: open source tailored to your workload, in your cloud or on-prem.
Review your Temporal workload with an engineer
45 minutes: workflow volume, retention and placement are reviewed and the Temporal design is sketched.
- ✓A design sketch for your workload, not a plan menu
- ✓A zero-downtime cutover path for what you run today
- ✓A price for that design, after the review