Say it. See it. Ship it.

Builder (also called Low Code or Mission Control) writes a real project: Next.js, React, Angular, Expo, NestJS, or FastAPI, depending on what you need. Everything it makes is a file in a folder on your computer, saved step by step in a private history.

That matters later. When you bring in a developer, they open the same folder in the IDE and keep going. There is no export, no rebuild, and no second tool.

Templates give Builder a head start: the right roles, pages, and data from the first step.

Each template starts with a three-part map. Bookings, for example, is Customers (book online), Booking App (calendar logic), and Bookings + Staff (database and Stripe).

Build power decides which model builds your app and which passes run. There are three: Fast, the default, Auto, and Customize for choosing yourself. The same setting appears on the Welcome screen, in Comm-Link, and on the Send to Builder step. Every model is paid from the same credits as the rest of Piye.

Comm-Link is the conversation with your project. It has two voices: the Architect, who plans and asks questions, and Builder, who writes the code. You can talk to the Architect as long as you like without changing a file. Builder only changes things when you send it work.

• Attach files, images, or sheets to a message.
• Switch models and build power from the picker under the input.
• Stop a build at any time. What was done stays in the Timeline.
• Side questions can run while a build is going, without interrupting it.

The Blueprint is a live map of your app. Nodes are the parts people care about: visitors and roles, the app itself, pages, logic, triggers, and the database. Lines show how they connect. Click any node to open its inspector.

Preview runs the actual app, not a picture of it. As Builder writes files you see them appear. Logs from the running app are one click away when something looks wrong.

• Choose a device size, orientation, and light or dark appearance.
• Click through the app as a real user would. Links and buttons work.
• Websites preview in a browser frame. Piye will never put a website inside a phone frame.

Mobile projects run on a real iOS Simulator and Android emulator, side by side. Expo apps also show a QR code so you can open them on your own phone with Expo Go.

Turn on Visual Edit and click anything in the preview. The inspector adapts to what you picked: a heading gets its words and typography, an image its source and fit, a box its layout.

The Timeline lists every Builder step, newest first, in plain words: "Added checkout page", "Made the header sticky". Each step can be undone.

Underneath, it is private local Git. Nothing leaves your computer until you connect GitHub at Publish. When a developer joins, they see the same history as normal commits.

While you build, the app does not send real emails. Sign-in links, welcomes, and receipts land in the Outbox instead, so you can open and read them. A badge shows when new ones arrive. When you graduate email, real sending starts.

Choose Mobile app in Publish. Piye walks you through each account it needs, with links to sign up, then builds and submits for you. Publish the website first: the phone app talks to its live server, never to the one on your computer.

While you build, Piye runs the services for you: a development database, Google sign-in, email, payments in test mode and AI, paid from your Piye credits. Your live app runs on your own accounts instead, so it is fully yours and never depends on Piye. Your accounts, in Publish, lists only what your app uses. Each takes a few steps, and Piye checks it works before you publish.

While you build, your app takes payments in Stripe's test mode through Piye, so you can try checkout with test cards and no setup. To take real money, connect your own Stripe account in Your accounts before you publish. Your customers then pay you through your Stripe account. That relationship is between you and Stripe, separate from your Piye plan.