Oyren Features

Notes, boards and cloud machines for app development.

Shop and pre-order pages built with a coding agent

A coding agent builds a product page from photos, prices and an existing payment or waitlist link. The page opens at a public URL for review, and its code remains editable. Payments stay with the chosen provider; Oyren does not process them through this workflow.

See plans and usage pricing
Run client code use-case poster
Illustrative run client code use-case poster from the Oyren video collection.
App preview use-case poster
Illustrative app preview use-case poster from the Oyren video collection.

Product information and purchase destinations

A product brief records the name, price, photo and explanation needed for a buyer to decide. It also identifies the next step: purchasing an available product or registering interest before launch. That decision defines the destination linked from the page. A focused first version can describe the offer and point to the existing payment or waitlist tool rather than implementing payment processing.

A kanban card holds the product list and existing payment or pre-order link, such as a provider’s checkout page or waitlist form. Product photos and copy can be attached as workspace files. Oyren does not process payments itself; the page links out to the tool responsible for that step.

Pages built from product source files

Assign to agent can send the card to a coding agent, or the task can be described to Claude Code, Codex CLI, opencode, Cursor CLI or Qwen Code, with Antigravity available from the terminal. A task can specify a product list, individual product pages and visible payment or pre-order links. A scoped page or product group provides a result to check against the brief.

The codespace runs Linux. Agent sign-ins or API keys are supplied separately, and tools such as an image library can be installed for the build. VS Code provides access to inspect the layout or a price in the files before further changes.

Price, link and layout review

Every codespace has a public URL. The Public site panel points it at the page’s port. Product descriptions and prices need comparison with the source list, and the payment or pre-order link needs checking against its intended destination. These checks remain part of review before the page is shared.

A phone-width view provides a layout check for the product list. Runtime is billed by the hour while the codespace runs. A snapshot supports pausing the machine and returning to another product or page later, with the brief and source files still available in the workspace.

Questions about shop and pre-order pages built with a coding agent

Does Oyren process payments or take orders?
No. The page links to an existing payment or pre-order tool. A coding agent adds that link or button; this workflow does not provide a checkout or ordering system of its own.
Can I list several products with different prices?
Yes. Product names, prices, descriptions and photos can be supplied on the board card or as files. The agent can build pages or sections for the products, with prices checked against the source list before sharing.
How is a pre-order page different from a shop page?
The layout can be similar; the destination differs. A shop page links to a checkout for an available product, while a pre-order page can link to a waitlist or deposit form before shipping. The board card records the intended destination.