# Starter Pro Fullstack

Starter Pro Fullstack is a one-time source licence combining the complete **Web application**, the **native iOS and Android application**, and their **shared API**. Web and Mobile use the same backend, accounts, workspace permissions and data after you configure them.

See the current tax-inclusive price on the [Fullstack product page](/starters/fullstack) and compare [source licences](/pricing#source-licences). This is source you configure and operate; hosting, third-party services and Apple/Google accounts are separate.

## Purchase, upgrade and access

Purchase Fullstack from its product page, or open an eligible Web/Mobile purchase's private access link to request the verified-order upgrade. You can obtain a fresh link through [purchase recovery](/orders/recover). A public email address or a client-supplied amount never determines upgrade eligibility or price.

Only verified payment authorizes the new order and product access. Use the Fullstack claim email to download the correct ZIP. Keep the links private. If payment is uncertain, contact [purchase support](/orders/support) before paying again. Payment confirmation, email delivery and successful download are separate checks.

## One Web backend, two interfaces

The archive root is `pycolors-starter-pro-fullstack/`:

* `README.md` and `LICENSE` describe this release's setup, operating and licence boundaries.
* `PYCOLORS_RELEASE.json` records the purchased and included products, component paths, terms version, source revision and hashes.
* `web/` is the complete Starter Pro Web source, including the shared backend under `app/api`.
* `mobile/` is the independent Expo source, retained API client and native tokens.

There is no second backend fork to synchronize. Use one configured Web backend for both interfaces. The PyColors commerce storefront and hosted provider accounts are not application modules supplied in this archive.

## Configure Web and the shared backend

Use the Node/pnpm versions and frozen lockfiles in the received release. Prepare PostgreSQL and configure the supplied environment examples for Better Auth, email, billing and the integrations you need.

From `web/`:

```sh
pnpm install --frozen-lockfile
pnpm db:generate
pnpm exec prisma migrate deploy
pnpm build
pnpm start
```

Follow [Web getting started](/docs/starter-pro/getting-started), applying its commands inside `web/`. The Web purchase licence and your own application's user subscriptions are separate. You configure your own Stripe products, prices and webhooks if you monetize the application.

## Connect Mobile to the same accounts and data

From `mobile/`, follow the [Mobile setup and qualification steps](/docs/starter-pro/mobile#native-source). Point its public endpoint at the Web application's shared backend:

```dotenv
EXPO_PUBLIC_STARTER_PRO_API_URL=https://your-web.example/api/rpc/v1
```

Use the same origin for the supported authentication lifecycle and RPC. Configure the permitted native callback/origins in the backend. A device or emulator must reach that HTTPS origin. Do not connect Mobile to the PyColors commerce API or create a second user database for the same Fullstack deployment.

Validate a real account and authorized workspace/project journey from both interfaces against your own test database. Your release's source and synthetic qualification results do not validate your provider configuration or deployment.

## Validate and distribute your own applications

Review the received manifest, hashes and exact qualification reports. Build and test Web, then run Mobile's API/token, lint, types, tests, config/dependency and Hermes export checks. Keep source versions aligned when upgrading the Web API and retained Mobile client.

Hermes exports are JavaScript/bytecode, not signed store binaries. Qualify installed-device behavior using your own native toolchains, identifiers, signing and Apple/Google accounts, and complete the stores' distribution requirements. No hosted service, native binary publication or store approval is included.

## Licence, updates and support

The current licence revision is **2026-11-20**. One individual or legal entity may create unlimited end products using the included Web, Mobile and API source. Clients need their own licence to access that source. Redistribution as a competing kit is prohibited and third-party licences remain applicable.

Updates and reasonable-effort purchase/setup support concern the products included in the order, subject to continued availability and the applicable terms. Earlier purchases retain more favourable rights from their original terms. Read the received `LICENSE`, [licence page](/license) and [terms](/terms). Deployment, custom implementation and ongoing operation are separate engagements.