Will Your Self-Hosted App Run Out of Disk? A Practical Capacity-Planning Checklist

Treat this as a planning worksheet

There is no single storage estimate or alert threshold that fits every application and hosting setup. This checklist helps you organize observations and questions about your own environment; it is not a universal technical standard. Confirm measurement and operational decisions with the people responsible for your application, server, and backup process.

The calculation below is a way to summarize measurements your team has already chosen to collect. It does not establish which locations to measure, how often to measure them, or what threshold should trigger action.

• Mark each item as confirmed, estimated, or still unanswered.
• Use application- and hosting-specific documentation for decisions about measurement, backup, restoration, and cleanup.

Map the locations you want to track

Identify the application-related data and files your team wants to include. Depending on the setup, these may include a database, user-managed files, logs, temporary files, and backup copies. Do not assume they all live in one place.

For each category, record what it is, where it is stored, who is responsible for it, and whether your team considers it essential for normal operation or recovery. Ask the people familiar with your environment which locations your chosen measurements cover.

• List the application data, copies, and other files your team wants to track.
• Note the location and owner of each category, including any uncertainty.
• Record whether separate locations are measured individually or together.

Record observations and calculate the change

With your administrator, choose a measurement method and the locations it covers. Record the date, measured amount, and scope each time. Keep the method and scope consistent when comparing observations, or clearly note what changed.

To summarize change between two observations, subtract the earlier measured amount from the later amount. To express the average change over the interval, divide that difference by the time between observations. If the measurement scope changed, treat the result as not directly comparable rather than presenting it as a like-for-like change.

This calculation describes only the observations you entered. It is not, by itself, a reliable forecast: note unusual periods or changes in application use, data practices, or configuration, and treat any projection based on the observed change as an assumption to review.

• Use a table with columns for date, measured amount, location or scope, and notes.
• Calculate the difference between comparable observations and record the interval used.
• Add notes about significant activity or configuration changes that may help explain a difference.
• Keep projections separate from measured values and state the assumptions behind them.

Ask about operational and recovery needs

Discuss whether routine work—such as imports, updates, maintenance, backup creation, or restoration—changes the storage your setup needs. The answer depends on the application and procedure. Ask where each operation writes data, whether it creates additional copies, and what happens to temporary files afterward.

Do not assume a backup or restoration requires only the space occupied by active data. Ask whoever manages the procedure to explain its storage requirements and, where appropriate, how those requirements have been checked in your environment.

• Identify the operations your team considers important to plan for.
• Ask whether they use the same storage locations as the application data.
• Confirm what working space and retained copies the actual procedure requires.
• Mark untested assumptions as open questions rather than established requirements.

Agree on alerts and a low-space response

Choose alert levels with the people responsible for your system, based on its setup, your observations, operational needs, and the time your team expects to need to respond. This article does not prescribe a universal percentage or threshold.

Agree on what your team will do if a warning appears. Identify the affected location and investigate what changed. Do not remove files simply because they are large: first establish what they are, whether they are in use, and whether they matter for application operation or recovery.

If cleanup or expansion is being considered, follow an approved process for your environment. Confirm the purpose and consequences of a change with the responsible administrator before taking action.

• Decide who receives and investigates a storage warning.
• Specify what information to gather before making a change.
• Use known retention rules and approved procedures for cleanup.
• Document the cause, action, and any follow-up after an incident.

Review assumptions, including managed hosting

Revisit the worksheet when application use, data practices, or operating procedures change. Check whether the storage map, measurement scope, alert ownership, and recovery assumptions still describe your environment. If recovery requirements have not been confirmed for your procedure, keep them marked as an open question.

A managed deployment can shift some infrastructure work away from a small team, but it does not remove the need to make choices about data, access, retention, and recovery. Airbip offers managed deployment for a public catalog of business, publishing, analytics, collaboration, and AI applications. Application instances run as Docker workloads on Airbip cloud servers, with configurable daily, weekly, and monthly backups.

Those product capabilities do not establish every application-specific detail about storage location, backup scope, retention, monitoring, or recovery. Confirm the details that matter to your requirements. Review current plan and commercial information directly on the Airbip website.

• Review the worksheet after meaningful changes to application use or operating procedures.
• Ask what data and locations are included in backups and how retention is configured.
• Clarify which monitoring and response responsibilities remain with your team.