# Perpetual workflows - one per customer

**URL:** <https://community.temporal.io/t/perpetual-workflows-one-per-customer/13374>\
**Category:** Community Support\
**Created:** [September 3, 2024, 3:39pm UTC](https://community.temporal.io/t/perpetual-workflows-one-per-customer/13374 "2024-09-03T15:39:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rebecca](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/rebecca/32/5797_2.png) [@rebecca](https://community.temporal.io/u/rebecca)\
**Post date:** [September 3, 2024, 3:39pm UTC](https://community.temporal.io/t/perpetual-workflows-one-per-customer/13374/1 "2024-09-03T15:39:30Z")

</div>

I am currently evaluating Temporal and I’m considering how to use it in our domain - Utilities.

Would it be a bad design to treat every customer we have (millions) as an individual separate and perpetual workflow? As long as they remain a customer.

We would have a number of child workflows that require human intervention (signals) either by our customers or by internal employees:

- double opt in
- various during the onboarding / sales process
- risk management
- extending customer delivery contracts

Or is there a better way to model this?

---

<div class="post-metadata">

**Author:** ![maxim](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/maxim/32/8_2.png) [@maxim](https://community.temporal.io/u/maxim)\
**Post date:** [September 3, 2024, 5:03pm UTC](https://community.temporal.io/t/perpetual-workflows-one-per-customer/13374/2 "2024-09-03T17:03:14Z")

</div>

It is hard to give 100% reliable recommendation without understanding the details of the use case. Having a perpetual workflow per customer (we call them entity workflow) is a common pattern. Temporal has no performance problems with billions of open workflows. So millions is absolutely fine.