Skip to Content
🔗

Pools that depend on other pools

Updated 2026-11-20

What one pool delivers is often what another pool consumes. An application hosted for customers runs on servers; the servers are a pool of their own. Add a recurring cost with the source Output of another pool, choose the Upstream Pool and its output, and enter how much is used.

The cost follows the upstream unit cost. When the server costs change, the cost of the application changes with them, and so do the cost of its products and its margin.

What the other pool takes counts in this one too: it is used capacity, shown as internal use, and paid at the unit cost the other pool is charged. The room left in the servers is what is really left once the application has its share.

Note: A pool cannot depend on itself, directly or through other pools; Lynx refuses the link.

Was this article helpful?
Thank you for your feedback. Still stuck? Contact us