Resources

Developer guide.

How Project OS actually works when you sit down in the IDE, not a classroom, not a prompt box.

01

Open the same project

A Piye project is a folder with Git and a .piye workspace. The founder can be in Low Code while you are in Developer. There is no export step. If a file changes on the Blueprint, it is a real file in the tree.

02

Low Code, then the door

Comm-Link takes a plain-language change. Architect plans it. Builder writes it. Blueprint shows the nodes. Preview is web or both phones. The mode menu on the project name is the door into Developer: Explorer, terminal, Git, and the same preview.

03

Run it for real

Use Preview for a fast loop. Use Apps when you need the actual iOS Simulator and Android emulator: gestures, camera, store binaries. Websites open in the browser, not inside a fake phone chrome.

04

Ship from Deploy

Connect the host once. Deploy can push web, server, TestFlight, and Play. Env values stay in the OS keychain. The agent sees key names, not secrets. EU-resident hosts are available when the product must stay in Europe.

05

Watch Operations

Probes read the providers you already use: GitHub, Vercel, Railway, Stripe, stores. When Railway is down, the stream says so. Fix it in the same project, not in twelve dashboards.

06

AI without giving the repo away

Ask / Architect / Build / Debug run inside Piye. BYOK and Ollama are available. Privacy Mode blocks cloud and keeps work on the machine. We do not train public models on your tree.

07

Handoff

Invite a developer with a project link. They clone the Git remote and open Developer. The founder’s Blueprint history is still there. You review the diff like any other repo.

Developer guide · Piye