# White-Label SaaS Source Delivery: What Real Pruning Has to Get Right > Selling generated source code is a delivery problem, not a marketing claim. The failure modes are dead links, leaked branding, leaked generator code and a paywall that follows the customer home. - Author / publisher: make1day (company) - Published: 2026-11-07 - Canonical: /blog/white-label-saas-source-delivery - Category: Guide - Tags: white label SaaS boilerplate, boilerplate generator, source code without vendor branding, configurable starter - Language: en "White label" is easy to write on a landing page and surprisingly hard to deliver. When the ZIP IS the product, four things have to be true. ## 1. Pruning is real, not a feature flag Unselected modules must be absent from the archive, not merely disabled behind an env flag. A customer who unchecked an admin console should not receive its routes, its nav entries or its imports. In this project the skip list is declarative and every generated package is type-checked; 18 representative configurations are downloaded and compiled in CI. One hard-learned rule: a rewrite step may only modify files that are ALREADY in the ZIP. An early version fell back to reading pruned files from disk, quietly re-adding them to the customer package. ## 2. Brand removal includes generated pages Home, pricing, sitemap, robots and legal pages in a customer build are generated from that customer's own configuration, not inherited from our marketing site. Even a comment inside a generated template containing our old brand name used to break the whole matrix. Assertions now scan customer pages for our brand, competitor brand names, dead links and generator files. ## 3. Never ship the factory The ZIP contains the product, not the machine that makes it. The generator directory, the builder route and the generate API are removed. A purchase grants one generated project, not a license to run the factory. ## 4. The paywall must not follow the customer Our site requires an HMAC license key, an active subscription or an email claim before it emits a source ZIP, and production fails closed even when the signing secret is missing. The customer's own project ships with that gate defaulted to off — in source, not just in .env.example, which nobody copies. Anonymous visitors can still take a source-free preview: the file inventory and design tokens, with a signed visitor token and a two-bucket quota. ## Verify it yourself Unzip the build and search for the vendor's brand, the generator directory and any link to a route that does not exist. Then run the type checker and a production build inside the extracted project. If any of those fail, the white-label claim was marketing. ## FAQ ### Does the generated ZIP contain the generator itself? No. The generator modules, the builder page and the generate API are pruned. Buying one build gives you one project, not the factory that produces builds. ### Is the license gate active in the downloaded project? No. The customer's own lib/env.ts is rewritten so licenseGateMode() defaults to off in source. Only this site enforces the paywall, and it fails closed in production. ### What is in the anonymous preview? A source-free package: the complete file inventory for your configuration, design tokens and a README-style PREVIEW.md. No source files. It is rate-limited by a signed visitor token plus a trusted-network bucket. --- Source: make1day. See /llms.txt and /llms-full.txt for the full machine-readable product description.