White label in GoFeed is three pieces, bought separately and in any combination. The Branding pack puts your palette, your logo and your name on the portal, on the emails and on the documents. Email domain makes those emails leave from an address of yours. Custom domain puts the app and the portal on app.youragency.com. With all three, the client sees no other product underneath.
Three pieces, not a switch
When an agency asks about white label it usually pictures a button: you press it and the product disappears. In GoFeed there is no button but three add-ons, and it is worth knowing what each one does before buying any of them, because each answers a different part of the same question: what does your client see when they work with you.
The Branding pack decides the look. Your palette, your logo and your banner, your heading font and your agency's name instead of ours on the client portal, on every email the workspace sends to third parties and on the quotes, contracts, invoices and reports it issues. The Email domain add-on decides the sender: those same emails leave from hello@mail.youragency.com instead of from GoFeed's address with your name in front. And the Custom domain add-on decides the address: the whole app, portal included, answers on a subdomain of yours such as app.youragency.com.
They are bought separately and in whatever order you like. You can have only the pack, only the domain, both domains without the pack or all three together. There is no courtesy subdomain on our domain and no tier in between: each piece is an add-on with its price on the pricing page, which reads the live catalogue, and full white label is having all three.
| Piece | What it decides | Where it is set up | What it needs from you |
|---|---|---|---|
| Branding | Which palette, logo and name everything wears | Settings, Branding section | Your logo and a choice of colours |
| Email domain | Which address the emails leave from | Settings, Email domain | Three DNS records on a subdomain |
| Custom domain | Which address the app and the portal answer on | Settings, Custom domain | One CNAME record on a subdomain |
All three belong to agency workspaces. A creator workspace does not have them because there is nobody to stand in front of: branding is worth something when another person, your client, opens what you send them.
What the Branding pack dresses
The pack opens a section under Settings with four screens, and the first, Image, is the only one every workspace has without paying anything: the trade name, the logo and the banner are saved there on any plan. What the pack buys is that those images get used.
The Theme screen is the palette: the primary colour, the secondary and the two warning colours, the heading font, the corner radius and whether the interface reads in light or dark ink. It has a preview and nothing changes until you save. The theme applies to the app your team sees, to the portal your client sees and to the public pages the workspace serves, such as a quote shared by link.
The Emails screen decides which image heads each email that leaves in the workspace's name. There are twelve templates: the monthly report, the shared quote, the invitation to the portal and to the team, the brief and its reminders, the pending approval notice, the invitation to set up billing and the chat digest. For each one you choose the logo, the banner, the name alone or automatic, which is the banner if there is one, else the logo, else the name. The sender name and the reply address the client sees live here too.
The Documents screen does the same for the five documents the workspace issues: quote, contract, invoice, brief and report. The issuer stamped on them, with its legal name and tax id, comes from the workspace details; what the pack adds is that the letterhead is yours and not ours.
There is one detail that shows more than it seems: the name. With the pack, the browser tab, the footer of every email, the support address offered when something fails and the signature on the documents say your agency's name and the support email you wrote under Settings. Without the pack they say GoFeed. That is what the next section explains.
Without the pack, your domain shows the product whole
Here is the rule that saves the most questions. Custom domain and Branding are independent, so an agency can have the app on app.youragency.com without having bought the pack. In that case app.youragency.com shows GoFeed as it is: the name, the mark, the default theme and the product's support address. All of it, never half.
It is a decision, not a gap. The alternative would be a hybrid, your logo over our name or your palette with our support address underneath, and a hybrid is the worst version of both brands: the client does not know who they are writing to and you do not control what is shown. The app decides once, on reading which address somebody came in through, whether that workspace holds the pack; if it does, everything painted is yours, and if not, everything is the product's. No screen can show a thing by halves.
The most common order, and the one with the fewest surprises, is to buy the pack first and the domain after. That way, the day the CNAME points and app.youragency.com answers, it already does so wearing your brand. The other way round works just as well, but in the gap your clients will see our name at your address.
The same happens if the pack lapses. The colours, the logo and the per template choices stay saved, the app stops reading them and goes back to the default look; if you buy it again, they apply again with nothing to rewrite. The domains behave similarly and each guide gives its own deadlines: a verified domain is kept for thirty days and reactivates without repeating the DNS if you come back before then.
Everything in this article happens in one place in GoFeed.
Try it freeThe two domains, each with its own guide
The two domain add-ons have guides of their own with the table of records and where to paste it in Cloudflare, IONOS, GoDaddy, Namecheap and Squarespace. Here, only what you need to know to decide.
Custom domain is one CNAME record on a subdomain of yours, and the subdomain is mandatory: app.youragency.com yes, youragency.com no, because pointing the root would send your whole website at the app. Any label works, clients.youragency.com or portal.youragency.com do the same job. As soon as the record points, the certificate issues itself, the team signs in at your address, the client opens their portal at your address and the links that go out by email, such as a quote to accept, are built on it.
Email domain is three DNS records, DKIM, SPF and an MX for the bounces, on another subdomain such as mail.youragency.com, plus a recommended DMARC that is not checked. Here too the root is refused, and for a practical reason: the mailbox you already write from by hand has its records there, and this way they are left alone. You choose a sending region once, European Union or United States, and when the three records are verified the sender changes on its own.
Each can be had without the other. An agency that sells mostly by email and whose clients barely enter the portal may want only the sender; one that has its clients live in the portal may want only the address. And the two use different subdomains, so they never collide: one for the app, another for the email.
What stays GoFeed's, even with all of it
With the three pieces, a client opens app.youragency.com, sees your brand, receives a quote from hello@mail.youragency.com on your letterhead and accepts it at your address. Two places remain where the product shows through, and it is better to know them before a client asks.
The first is the "Continue with Google" button. Google only returns the sign-in to a registered address, which is the product's, and the consent screen it shows carries the name of the registered app, which is GoFeed. When somebody presses that button on your domain, the app takes them for an instant to app.gofeedapp.com, Google answers there and a single use ticket brings them back to your address with the session open. Those are two redirects the person never gets to read, but Google's screen is Google's and it says our name. Somebody who signs in with email and password never sees it.
The second is the sending address while you have no verified email domain. In that case, every email that leaves in your workspace's name carries your name as the sender and the product's address underneath, equipo@app.gofeedapp.com, with your support email as the reply address. The client who presses Reply writes to you; the client who reads the address with a magnifying glass sees ours. That is exactly the gap the Email domain add-on closes, and it is also what happens, temporarily, if one day your domain stops signing: that email is resent once from the product's address instead of being lost.
Sign-in emails follow the domain the person came in through. An access code, a password reset or an email verification requested from your domain leaves with your brand if you hold the pack, and from your address if you also have a verified email domain; requested from the product's domain, it leaves from the product. What never changes are the notices about your subscription: GoFeed sends those to you, from its own domain.
Bio pages and the GoFeed mark
The link in bio pages are a case apart, because they have their own mark and their own add-on. With Custom domain, every Bio page in the workspace also answers at your address, app.youragency.com/t/ followed by the page's code. The address on the product's domain keeps working, so the links already placed in a profile do not break.
What the domain does not remove is the "Made with GoFeed" mark in the corner of the page, and neither does the Branding pack. That mark is removed by Bio Pro, which is the add-on of the pages themselves: the pack covers the portal, the emails and the documents, and the Bio page is a different surface with a sale of its own. An agency that wants the three pieces and unmarked Bio pages on top buys all four things.
What to buy, depending on what your client sees
The shortest way to decide is to ask where your client enters your work. If what they receive is quotes, invoices and reports by email and they hardly set foot in the app, the pack and the email domain are the two pieces they see; the app's domain would make no difference to them. If they live in the portal, approving posts and opening the monthly report, the pack and the custom domain are the ones they notice, and the email sender takes second place.
If they do both, which is the norm for an agency that runs social media and invoices from the same place, the three pieces are the answer, and the pack is the first because it is what makes the other two visible. A custom domain with the default brand is an address of yours with our product inside; an email domain without the pack is your address signing an email on our letterhead. Neither is a mistake, but neither is white label.
What no combination changes is what sits underneath: the same permissions, the same data, the same quotes and invoices with your series and your VAT. White label in GoFeed is not another version of the product for agencies, it is the same product with your name in front, and that is why it is sold in pieces: each one changes one thing your client sees and none changes what you do.
