Understanding Resource Allocation
Why FlyNode gives your account one shared RAM/CPU pool instead of a fixed slice per app.
FlyNode plans are priced on a single dedicated resource pool per account, a total amount of RAM, CPU, and storage, rather than a fixed limit per individual app.
What this means in practice
Deploy as many apps as you want; every one of them bursts against your account's whole pool as needed, rather than being capped at its own slice.
An idle app uses almost nothing, leaving more headroom for the apps you're actively using.
Your dashboard shows each app's own live measured RAM/CPU usage (updated every few minutes), plus your account-wide total against your plan's ceiling.
Why not per-app limits?
Most PaaS platforms charge and cap per app, which means running five small apps costs five separate allocations even if four of them are barely used at any given moment. FlyNode's shared pool model means an agency running several light client apps side by side pays for the pool they actually need, not the sum of five worst-case slices.
Storage
Storage is measured separately from RAM/CPU (checked twice daily rather than continuously) and counts against the same account-wide plan ceiling.
Still stuck?
Open a support ticket from your dashboard and include the container name.