Licensing & FAQ

Answers about licenses, local data, product updates, and how StellarFlow relates to pi Agent and StellarMesh API.

01 How does licensing work?

Desktop builds include a trial. Afterward, they require a signed license bound to the current machine ID. One order covers one device. The license itself does not expire and remains valid for future public versions.

Reinstalling the operating system or making major hardware changes can produce a new machine ID that no longer matches the original license.

02 Can I purchase and activate today?

The in-app trial, machine-ID display, and license import flow are complete. Until the Stripe merchant account and production checkout are live, this website will not show a payment button that cannot complete an order.

03 Where is my data?

Sessions are stored as JSONL files under ~/.pi/agent/sessions by default. Model configuration, authentication, skills, and other pi Agent resources also remain in the local pi Agent data directory.

04 How does StellarFlow relate to pi Agent?

StellarFlow currently builds on the pi Agent development toolkit and session format, adding a StellarMesh-designed desktop experience, local-service lifecycle, packaging, licensing, and product workflow. We will continue enhancing and evolving our own agent runtime.

05 Is StellarMesh API required?

No. StellarFlow works with model providers you configure yourself. StellarMesh API is an optional unified access service in the same product family and can also be used independently.

See the changelog for the latest public release updates.