You can totally do this. You can have a global singleton which is your FLAME pool. For example, using :pogo:

1. Remove FLAME.Pool from your application children.

2. Add Pogo supervisor to your application children (check the pogo docs). Let’s say you called it MyApp.DistributedSueprvisor

3. Start your global singleton FLAME pool supervisor like this:

    Pogo.DynamicSupervisor.start_child(
        MyApp.DistributedSupervisor,
        FLAME.Pool.child_spec(
          name: MyApp.FlamePool,
          min: 20,
          max: 30,
          max_concurrency: 10,
          idle_shutdown_after: 2 * 60 * 60 * 1_000,
          min_idle_shutdown_after: 2 * 60 * 60 * 1_000,
          timeout: 5_000
        )
      )

Pogo will ensure unique children IDs. Flame will set the ID to be some kind of tuple like {FLAME.Pool, MyApp.FlamePool} (it uses the name opt). So if you are using the pogo supervisor which_children function, watch out for that.

Do not copy my Flame config! Decide your own values. This is just a concept BTW. I am not recommending you use a single flame supervisor on just one node. It seems at odds with the spirit of FLAME.