Welcome to PhyStack

Prompt your AI agent

Working with Claude, Cursor, or another coding agent? These docs are published in an agent-readable format. Paste this to get your agent up to speed:

Read https://build.phystack.com/llms-full.txt to learn the PhyStack platform, CLI, and docs. Then help me build a PhyStack app from scratch:

1. Set up my machine following the dev environment setup guide. Check what I already have before installing anything.
2. Get me authenticated, with a working tenant, following the getting started guides.
3. Ask me what I'm building, then pick the right app type with me.
4. Scaffold the app following the tutorial for that app type, run it locally the way that tutorial shows, and iterate with me until it does what I want.

What is PhyStack?

The infrastructure layer for physical AI.

PhyStack is one platform to deploy intelligence to any device, from a sensor to a robot, connect every system in a space, and give AI agents control of the physical world. Build and operate real-world applications across edge, cloud, and AI, at scale.

Why build on PhyStack?

The few who deploy physical AI today stitch together point solutions: one vendor for the edge OS, another for fleet, a third for analytics, a fourth for device control. Each speaks a different protocol. Each has its own dashboard.

We fix that with:

1. Edge-native OS (PhyOS) with OTA + GPU
2. Digital twins + MCP for real-world context
3. One CLI, API, and Console to manage it all
4. Built-in signals + remote ops
5. Secure, compliant, multi-region data

Core concepts

PhyStack is everything you need to build for the real world. As easily as you build for the web.

PhyOS

PhyOS runs on Intel, ARM, or custom hardware. It’s a secure, GPU-accelerated container OS with OTA updates and built-in failover. Perfect for edge AI, high-performance logic, and hardware control. Dig deeper in PhyOS.

PhyHub

PhyHub is your cloud-native backend. It manages digital twins, streams real-time data, powers ML pipelines, and handles everything from identity to products, checkout, and media. See how apps talk to PhyHub in Communication.

Signals and Spaces

Signals track every event, drive analytics, and fine-tune your models. Spaces map your environment from region to room, so you can target content, apply permissions, and generate rich reporting. Learn more in Signals.

Peripherals

Doors, cameras, printers, sensors, all become controllable through simple APIs and digital twin models. Your apps interact with them just like software objects. Learn more in Peripherals & Descriptors.

Developer toolkit

It’s all tied together by a complete toolkit for developers: use the CLI, REST API, drop-in SDKs, the intuitive Console UI, or connect agentic workflows via the MCP server. Start with the dev environment setup.

Quickstart for developers

PhyStack apps come in four types. Pick the one that matches what you’re building:

• Screen apps are the user-facing layer: full-screen interactive UIs on displays, kiosks, and shelf screens. Built with React, installed on PhyOS devices.
• Edge apps are headless services that run on devices. They talk to peripherals, run local logic and AI, and keep working offline. Packaged as containers.
• Cloud apps are backend services hosted on PhyStack cloud: APIs, integrations, and logic that spans your whole fleet. TypeScript or Rust.
• Web apps run in the browser: mobile-web companions and QR-code handoffs connected to the same platform. See Web Apps for the session model.

Build it by hand

Each app type goes from scaffold to published in less than 10 minutes:

Screen

Log in, then scaffold your screen app from the official template:

phy login
phy app init my-screen-app --type screen
cd my-screen-app
bun install

Run it locally on a simulated device. Start the device simulator in a separate terminal and leave it running:

phy-simulator start

Then start the app in your app folder. It keeps running while you work on the app:

bun run dev

Register the app, then build and publish:

phy app create my-screen-app --type screen
bun run pub

Full walkthrough: Screen App tutorial.

Edge

Log in, then scaffold your edge app from the official template:

phy login
phy app init my-edge-app --type edge
cd my-edge-app
bun install

Run it locally on a simulated device. Start the device simulator in a separate terminal and leave it running:

phy-simulator start

Then start the app in your app folder. It keeps running while you work on the app:

bun run dev

Register the app, log in to your registry, then build and publish:

phy app create my-edge-app --type edge
phy registry login docker.io
bun run pub

Connect to a device shell. This needs a device that is already connected to your tenant:

phy device shell <device-name>

Full walkthrough: Edge App tutorial.

Cloud

Log in, then scaffold your cloud app from the official template:

phy login
phy app init my-cloud-app --type cloud
cd my-cloud-app
bun install

Register the app, then copy the printed credentials into .env:

phy app create my-cloud-app --type cloud

Run it locally. Cloud apps do not use the device simulator. The app keeps running while you work on it:

bun run dev

Publish:

bun run pub

Full walkthrough: Cloud App tutorial.

Web

Log in, then scaffold your web app from the official template:

phy login
phy app init my-web-app --type web
cd my-web-app
bun install

Run it locally on a simulated device. Start the device simulator in a separate terminal and leave it running:

phy-simulator start

Then start the app in your app folder. It keeps running while you work on the app:

bun run dev

Register the app, then build and publish:

phy app create my-web-app --type web
bun run pub

Full walkthrough: Web App tutorial.

From here, you can iterate, publish new versions, and deploy at scale. All from the CLI or Console.

Edge AI

1. Deploy AI models to edge devices. Go from prototype to live edge inference in minutes.
2. Run inference and stream analytics. Manage your entire model lifecycle right from PhyStack.
3. CLI and SDK support. Automate deployments, scaffold apps, upload models, and bind to devices with Node or Python.
4. Roll out to thousands of devices. PhyStack handles orchestration, health checks, rollbacks, and fleet scaling.
5. Build adaptive edge apps. Use MCP to make your models environment-aware and responsive to real-world signals.
6. Install and manage via Console or CLI. Keep full control over where and how your apps run.

Data, security & compliance

1. End-to-end encrypted. Data is secure in transit and at rest (WSS, HTTPS).
2. Anonymized user IDs. Easy consent management and withdrawals.
3. Global data residency. Choose where your data lives: EU, US, AU, IN, UAE.
4. Signed containers with RBAC. Secure deployments and role-based access.
5. CLI and SDK level control. Encrypt, deploy, and audit with Node and Python.
6. ISO 27001 certified. Independently audited security and privacy management.
7. Firewall and threat detection. Azure WAF, IDPS, and Sentinel SIEM.
8. Outbound-only networking. One port to whitelist, secure by default.

Ready to build?

It only takes a few steps to get up and running with PhyStack.

1. Set up your tenant Register your tenant and create your user account.
2. Prepare your dev environment Install the CLI and connect to your tenant.
3. Provision your first device Install PhyOS on your hardware and connect your device.

Now head to our tutorials to deploy your first edge app, screen app, or connect them into a complete real-world experience.

Learn more

1. Check out our guide to using PhyStack Console.
2. Follow PhyStack on social media: X, LinkedIn, YouTube, Instagram.

Contact us

If you have any questions, please contact us at [email protected].