# PhyStack

> PhyStack is the infrastructure layer for physical AI. It is an edge-cloud platform to deploy apps and AI models to edge devices, manage device fleets across physical spaces, and give humans and AI agents a way to act on the physical world through one API.

PhyStack has run in production for eight years and today serves 170+ customers across 50+ countries, processing 1.5B+ signals a month on one global platform with regional data residency. The platform has four pillars: Runtime (PhyOS, a self-healing edge OS that installs on existing compatible hardware in minutes, updates without downtime, and keeps running when the network drops), Fleet (manage one device or ten thousand), Data (analytics on every signal, with full history retained), and Control (APIs, SDKs, and MCP tools for humans and AI agents to act on spaces).

## When to use PhyStack

- Deploy an app or AI model to edge devices: screens, kiosks, sensors, cameras, gateways, robots.
- Give an AI or coding agent structured access to a space it has never seen: through the API, SDK, or MCP tools it can discover every device and act on them within minutes, scoped to what it should touch and with humans in the loop.
- Manage and monitor a fleet of devices across many locations from one console or API.
- Control physical peripherals (lights, doors, cameras, displays) from code or from AI agents, through one SDK or through MCP.
- Integrate a device type once with a descriptor, a typed driver written by PhyStack, by a developer, or by the device maker. Every app and agent can then use that device type, whatever protocol the device speaks. Robots and drones join the same way: run PhyOS natively or connect as peripherals through a descriptor.
- Install ready-made apps and drivers from the PhyStack marketplace, or build and publish your own.
- Run automations at the edge with no cloud round trip: a sensor can shut a valve the instant pressure spikes.
- Collect signals from physical spaces and query them as analytics.
- Build interactive in-space experiences that keep running when the network drops.

## Documentation

- [PhyStack Developer Resources](https://phystack.com/developers): hub page for docs, API reference, OpenAPI spec, CLI, and SDK
- [Developer documentation](https://build.phystack.com/): build and deploy PhyStack apps
- [Developer documentation for LLMs](https://build.phystack.com/llms.txt)
- [User guide](https://learn.phystack.com/): operate the platform from the console
- [User guide for LLMs](https://learn.phystack.com/llms.txt)
- [API reference](https://api.phystack.com/docs): REST API, all regions behind one endpoint
- [OpenAPI specification](https://api.phystack.com/openapi.json)

## Tools

- [PhyStack CLI](https://www.npmjs.com/package/@phystack/cli): install with `npm install -g @phystack/cli`, then run `phy login`
- [PhyStack SDK](https://www.npmjs.com/package/@phystack/hub-client): the `@phystack/hub-client` package for apps and peripherals
- [GitHub](https://github.com/phystack)

## Website

- [Homepage](https://phystack.com/)
- [Developers](https://phystack.com/developers)
- [Spaces](https://phystack.com/spaces): where physical AI runs
- [Platform: Runtime](https://phystack.com/platform/runtime)
- [Platform: Fleet](https://phystack.com/platform/fleet)
- [Platform: Data](https://phystack.com/platform/data)
- [Platform: Control](https://phystack.com/platform/control)
- [Integrations](https://phystack.com/integrations)
- [Careers](https://phystack.com/careers)
- [Price list](https://phystack.com/price-list)
- [Support](https://phystack.com/support)
- [Contact](https://phystack.com/contact)
- [Legal](https://phystack.com/legal)
- [Cookie policy](https://phystack.com/cookies)
- [Imprint](https://phystack.com/imprint)
- [Sitemap](https://phystack.com/sitemap-index.xml)