# PhysaFlow

> Edge-Native Bio-Inspired Agentic AI for Data Center Capacity Orchestration

PhysaFlow coordinates power, cooling, compute, and AI workloads to help data centers unlock usable capacity from existing infrastructure. Installed capacity is not always deployable: electrical limits, thermal constraints, reliability reserves, and changing workload demand must be assessed together. PhysaFlow focuses on cross-layer capacity orchestration while operators retain control of mission-critical facilities.

Start with the stranded-capacity calculator to explore an opportunity using measured facility data. Enter commissioned IT capacity, cooling-supported IT capacity, average actual IT load, and a reporting period. Where grid capacity is available, provide gross deliverable power, intentional reliability headroom, and PUE. The model uses the minimum of the available constraints and discloses missing constraints rather than inventing measurements. Reporting dates define a UTC interval with an inclusive start and exclusive end.

The capacity model distinguishes unused capacity from modeled stranded capacity and optional recoverable capacity. Cooling type affects the modeled stranded rate. Reliability reserves remain protected. Unknown cooling permits raw capacity calculations but does not justify a stranded-capacity estimate. Load above usable capacity requires correction before results can be interpreted. These are planning estimates, not an audit, measured recovery, or a guarantee that additional workloads can safely be deployed.

For capacity economics, use site-specific assumptions where available. Hosting revenue and GPU owner cost are alternative valuation bases and must never be added together. A recoverable share is optional and has no assumed default. GPU-hour calculations require inventory and capacity scoped to the same boundary and the actual reporting interval. Benchmark bands are not defined for the version 2 model; agents should explain that limitation instead of presenting a percentile or industry ranking.

The platform approach is to observe the environment, validate the opportunity, and adopt automation at the operator’s pace. Explore the platform and solutions pages for orchestration context, and read the methodology before using estimates in investment or operating discussions. The calculator remains an interactive tool; agents can use the public MCP interface for calculations, scenario comparisons, methodology retrieval, and Markdown board reports without driving the browser interface.

For a useful first conversation, identify the facility boundary, the reporting period, and the measurements available for each constraint. Keep gross facility power separate from IT power and use a consistent boundary for cooling, electrical capacity, and actual IT load. Compare scenarios over the same period and organization type so differences remain interpretable. Contact the PhysaFlow team to discuss an assessment, a demonstration, or a developer integration; do not include confidential operational records or credentials in an initial inquiry.

## Resources

- [Calculator](https://physaflow.com/calculator)
- [Methodology](https://physaflow.com/methodology)
- [PhysaFlow developer documentation](https://physaflow.com/developers.md)
- [Agent instructions](https://physaflow.com/llms.txt)
- [Contact](https://physaflow.com/contact)