Your workflows run to completion, no matter what
Temporal is the durable execution engine that ensures your long-running business processes reach their conclusion, even in the event of a crash, redeployment, or network outage. Installed, monitored, and hosted in France by DINAO.
What is Temporal?
Temporal is an open-source engine for workflow orchestration and durable execution. It enables the construction of resilient applications where state, retries, and long-running logic are first-class citizens: your processes run reliably even across failures, redeployments, and crashes.
In practice, Temporal eliminates the need to manually write retry queues, state machines, and scheduling glue. You define your workflows and activities in standard code (Go, Java, TypeScript, PHP, Python, .NET), and the engine persists each step so it can resume exactly where it left off.
Designed for production and adopted by major platforms, Temporal is self-hostable, scales with containers or Kubernetes, and provides a Web UI to inspect and debug each execution. It relies on a persistence layer (PostgreSQL or Cassandra) and offers namespace isolation, signals, timers, and scheduling.
Host Temporal at DINAO
Resource tiers compatible with Temporal prerequisites (minimum 2 vCPU / 2 Go / 10 Go). Hosted in France, fully managed.
- 2 dedicated vCPU
- 4 Go RAM
- 40 GB NVMe
- Daily backups
- Managed & monitored by DINAO
- 4 dedicated vCPU
- 8 Go RAM
- 80 GB NVMe
- Daily backups
- Managed & monitored by DINAO
- 8 dedicated vCPU
- 16 Go RAM
- 160 GB NVMe
- Daily backups
- Managed & monitored by DINAO
1 hidden tier(s) (insufficient resources for this app) : Découverte
Technical details
You may also like…
Other applications managed by DINAO in the same category, hosted in France and GDPR compliant.
You might be wondering…
What is durable execution?
It is the guarantee that a started workflow will run to completion despite failures. Temporal records each step: if a server goes down, the execution resumes exactly where it was, without replaying or losing any action.
In which languages are workflows written?
In yours: Go, Java, TypeScript, PHP, Python, or .NET via official SDKs. You write business logic in standard code, and Temporal handles making it reliable and resumable.
Where is execution data hosted?
The Temporal cluster and its persistence database (workflow history) are on DINAO's infrastructure in France. Your data does not leave the territory.
Do I have to manage the infrastructure myself?
No. DINAO deploys the cluster, the persistence database, the Web UI, and monitoring. You connect your workers and deploy your workflows; we handle the rest.
Can I scale to high availability?
Yes. We start with a single node and then switch to a multi-node cluster with Cassandra persistence to handle high volume and guarantee availability, without changing your code.
