White Label setup for partners

You can use PILOT under your company’s brand, with your own domain and visual identity. This setup is called White Label.

To prepare for launch, you will need:

a domain name
access to your DNS settings
an SSL/TLS certificate
your logo and brand materials
contact details for the person who will approve the final design

If your company has an IT administrator, we recommend involving them in the DNS setup and SSL/TLS certificate preparation.

1. Prepare your domain name

Choose the domain your customers will use to access the platform. For example, app.company.com or company.com.

The domain should be registered in your company’s name. To help your company retain access to it, we strongly recommend that you:

register the domain through a company account
enable two-factor authentication
keep the account email address up to date
enable automatic domain renewal

Avoid registering the domain through an employee’s, contractor’s, or third party’s personal account, as access to that account may be lost.

What to send to PILOT Support

Send the exact domain name you want to use.

PILOT Support will confirm the IP address your domain should point to and any additional DNS records you need.

2. Connect your domain to PILOT

Once PILOT Support provides the IP address, update your domain’s DNS settings. These are usually available through your domain registrar or DNS provider.

What you need to do

1. Open your domain’s DNS settings

2. Create or update an A record

3. Complete the Name / Host field:

Platform address	Field value
Root domain, such as company.com	@
Subdomain, such as app.company.com	app

4. In the Value / IP Address field, enter the IP address provided by PILOT Support

5. Check for other A or AAAA records for the same domain or subdomain. If they point to another server, they may need to be removed

6. Save your changes

Do not delete DNS records unless you know what they are used for. Some records may be required for email, domain verification, or other services.

If you use a content delivery network (CDN), proxy, or web application firewall (WAF) service, such as Cloudflare, enable proxying for the new hostname only after agreeing this with PILOT Support.

DNS changes can take from a few minutes up to 24 hours to take effect.

What to send to PILOT Support

Send either:

a screenshot of the DNS records
a text copy of the records you configured

PILOT Support will check that your domain is configured correctly.

3. Prepare an SSL/TLS certificate

An SSL/TLS certificate is required for secure HTTPS access to your branded platform.

The certificate must cover every domain name your users will use to access the platform. For example, if both company.com and www.company.com need to work, both names must be covered.

You can use:

one certificate with both names included as Subject Alternative Names (SANs)
separate certificates, if agreed with PILOT Support

If you are unfamiliar with SSL/TLS certificates, share this section with your IT administrator, hosting provider, or certificate provider.

1. Confirm the certificate requirements

Before purchasing a certificate, confirm the required domain names and Certificate Signing Request (CSR) parameters with PILOT Support.

2. Purchase the certificate

Purchase a publicly trusted SSL/TLS certificate from a trusted Certificate Authority (CA) or an authorized reseller.

The following certificate types can be used:

DV — Domain Validation
OV — Organization Validation
EV — Extended Validation

Unless you have specific requirements, a DV certificate is usually sufficient.

3. Create the CSR and private key

When requesting the certificate, you will usually need to create:

a CSR (Certificate Signing Request)
a private key

Keep the private key secure. The Certificate Authority cannot recover it if it is lost.

4. Verify domain ownership

The Certificate Authority may ask you to confirm ownership of the domain using:

a DNS record
a file uploaded to your website
an email confirmation

If DNS verification is required, PILOT Support can help if needed.

5. Download the certificate files

Once the certificate is issued, download the complete certificate package.

What to send to PILOT Support

Provide the files in PEM/Base64 format. Common file extensions are .pem, .crt, and .cer.

The following files are usually required:

File	Contents
Server certificate	The certificate issued for your domain
Intermediate certificates / certificate chain	All intermediate CA certificates, in the order provided by the Certificate Authority
Root certificate	The root CA certificate corresponding to the certificate chain
Private key	The key created together with the CSR

If your Certificate Authority provides all files in one archive, you can send the original archive with a description of each file.

If the root CA certificate is missing, download it from your Certificate Authority’s official repository.

Before sending the files, check that:

the certificate was issued for the agreed domain;
all required domain names are included;
the private key matches the certificate.

A certificate issued for another domain, or one that does not include the required SAN, cannot be used.

The private key is sensitive information. Do not send it through an unsecured public channel. Use the secure transfer method agreed with PILOT Support.

4. Provide your brand materials

Send your current brand guidelines or brand book in PDF format, if available, together with your original brand assets.

Ideally, include:

your logo in a vector format: SVG, AI, or EPS
your logo in PNG format with a transparent background
logo versions for light and dark backgrounds
brand colors
minimum logo size and clear-space requirements
a favicon — the website icon
mobile application icons, if applicable
contact details for the person who will approve the final visual materials

If you do not have brand guidelines

You can prepare the materials without a brand book. Please send at least:

your logo
your main brand colors
the company or product name you want to use
a favicon, if available
contact details for the person responsible for design approval

PILOT Support will let you know if any additional materials are needed.

5. Review and launch

Once you have provided everything, PILOT Support will review:

the domain name
the DNS configuration
the SSL/TLS certificate files
the brand materials

PILOT Support will confirm whether everything is ready for the White Label setup. If any information or files are missing, you will receive details of what to add or update.

Once everything has been verified, PILOT Support will configure the platform under your brand and agree on a launch date with you.

After the configuration has been approved, inform PILOT Support before you:

— change the DNS records used to connect the platform

— reissue or replace the SSL/TLS certificate