Most "white-label" form tools let you change a logo and a color. FieldScroll starts from the other end: the product your customers touch is yours, and the platform underneath it is ours to run. This page says exactly where that line sits, so you can promise your customers the right thing.
What carries your brand
On the Launch and Partner plans, your brand leads every surface a customer sees:
- The mobile app. iOS and Android, with your name, icon, splash screen, and bundle identifier. It is submitted to the App Store and Google Play under your developer relationship or ours.
- The web dashboard. Runs at your domain, in your colors, with your logo. This is where your customers review records, run reports, and manage their users.
- Reports. Branded PDF and HTML output from templates you control, delivered by email or webhook. See reports.
- Email. Invitations, password resets, and report deliveries go out under your sending identity once your instance is configured.
- Sign-in. Users sign in to your app and your dashboard. Nothing in the login flow says FieldScroll.
The design of the dashboard and the app is not a per-customer redesign. Layouts, navigation, and components are shared across every instance; brand tokens and configuration change what they look like. That is what keeps release operations affordable, and it is the reason the platform can be operated for you rather than by you.
Where the provider still appears
Two places name the platform provider, and both are required disclosures rather than marketing choices:
- Legal notices. The privacy policy and terms of service linked from the sign-in screen and the app store listing name the operator of the platform. Your own agreement with your customers sits on top of these; the legal pages explain how the documents fit together.
- Store metadata. Depending on who holds the developer account, the store listing may show the publisher's legal name in the developer field.
If your offer needs a fully invisible provider, say so early. It is a legal-architecture question, not a configuration switch, and it is worked through with counsel rather than promised on a web page.
What is dedicated, and what is shared
Launch and Partner run on a dedicated instance: your own database, storage, and dashboard deployment, with nothing pooled across partners. Inside that instance, each of your customers is an organization, and access is enforced by row-level security in the database itself — every dashboard and mobile query is filtered by the requesting user's organization membership, and API keys are bound to one organization. The mechanism is described in multi-tenancy and security, and the dedicated instance page goes deeper on what that means for a data-boundary conversation with a regulator or an auditor.
What is shared is the codebase. Every instance runs the same platform release, which is how monitoring, mobile release coordination, and platform updates are handled by us instead of by you.
Which plans qualify
| Plan | Branding | Environment | Commercial use |
|---|---|---|---|
| Builder | FieldScroll-branded | Shared workspace | Not permitted — learning only |
| Launch | Your brand on every surface | Dedicated instance | One production solution line, up to five organizations |
| Partner | Your brand on every surface | Dedicated instance | Scaled per engagement |
Pricing and the full comparison are on the pricing page. Early Access runs on standard Launch pricing with founder-led implementation; see Early Access.
What white-labeling does not include
- Custom screens are scoped separately. The shared app shell can mount custom mobile screens for a workflow that needs more than a form, but that is a scoped piece of work, not part of branding. The platform page describes the extension model and where it stops.
- A custom portal or CRM. FieldScroll is the field layer. Your long-term system of record, customer portal, and analytics stay in their own homes and integrate through the API, webhooks, and reports.
- Per-customer forks of the app. One app, one release train. Customers are organizations inside it, not separate builds.
The honest version for your sales conversations
You can tell your customers: the app and the dashboard are yours, their data lives in an environment dedicated to you and isolated per organization, and the platform behind it is operated by a named provider under a published set of terms. That sentence is true today and is the one FieldScroll's own documentation supports.