Confirm source and license access
Begin with the repositories or delivery artifacts named by the purchased package. Verify that every team member accessing commercial source is permitted by the applicable license.
Use the release or commit reference supplied with delivery so the first evaluation is reproducible.
Install the declared toolchains
Platform uses separate Go and Next.js toolchains plus PostgreSQL. Follow the versions pinned by the delivered source and lockfiles instead of substituting newer dependencies during the first run.
Install frontend workspaces from the committed lockfile and build the Go service before changing configuration.
Create local-only configuration
Copy the provided environment templates, then use development credentials and isolated provider accounts. Never place production database, OAuth, email, cloud, or payment secrets in a local example file or commit.
The browser-facing application uses a same-origin API boundary; configure the server-only upstream separately.
Run migrations, services, and gates
Apply migrations with the documented owner and runtime roles, start the required services, and exercise a complete identity, tenant, authorization, and billing test path using non-production data.
Before customization, run the repository’s tests, type checks, build, security checks, and clean-clone validation. That baseline distinguishes environment issues from later product changes.