3 ms·

I think it's a sane practice to keep the marketing landing page on a separate domain than the product in case of SaaS.

declan_roberts 2y ago
Why? I always get frustrated when I end up in some parallel universe of a website (like support or marketing) and I can't easily click back to the main site.
- playingalong 2y ago
  The non-technical reason is that these are usually owned by different teams in your org (after you mature beyond a 5-person startup). The technical perspective is that things like wildcard subdomains (e.g. to support yourcustomername.example.com), or DNSSec if your compliance requires it, etc. cause an extra burden if done for these two use-cases at a time. > can't easily click Http pages don't have problems with having a link to example.net from within example.com. Or the opposite. Seems like an unrelated problem.
- thayne 2y ago
  One potential reason is that marketing teams often want to do things that are higher risk than you may want to do on your main application domain. For example, hosting content (possibly involving a CNAME pointing to a domain outside your control) on a third party platform. Using a framework that may be less secure and hardened than your main application (for example WordPress or drupal with a ton of plugins) using third party Javascript for analytics, etc.
stagalooo 2y ago
Could you elaborate on why? The companies I have worked for have pretty much all used domain.com for marketing and app.domain.com for the actual application. What's wrong with this approach?
- darkr 2y ago
  If there’s any scope for a user to inject JavaScript, then potentially this gives a vector of attack against other internal things (e.g admin.domain.com, operations.domain.com etc)
  - CountVonGuetzli 2y ago
    Also, if for example the SaaS you’re running sends a lot of system emails that really shouldn’t end up in spam filters, you can’t afford to let things like marketing campaigns negatively influence your domain’s spam score. Easier and safer to have separate domains.

Why? I always get frustrated when I end up in some parallel universe of a website (like support or marketing) and I can't easily click back to the main site.

playingalong 2y ago
The non-technical reason is that these are usually owned by different teams in your org (after you mature beyond a 5-person startup). The technical perspective is that things like wildcard subdomains (e.g. to support yourcustomername.example.com), or DNSSec if your compliance requires it, etc. cause an extra burden if done for these two use-cases at a time. > can't easily click Http pages don't have problems with having a link to example.net from within example.com. Or the opposite. Seems like an unrelated problem.
thayne 2y ago
One potential reason is that marketing teams often want to do things that are higher risk than you may want to do on your main application domain. For example, hosting content (possibly involving a CNAME pointing to a domain outside your control) on a third party platform. Using a framework that may be less secure and hardened than your main application (for example WordPress or drupal with a ton of plugins) using third party Javascript for analytics, etc.

stagalooo 2y ago

Could you elaborate on why? The companies I have worked for have pretty much all used domain.com for marketing and app.domain.com for the actual application. What's wrong with this approach?

darkr 2y ago
If there’s any scope for a user to inject JavaScript, then potentially this gives a vector of attack against other internal things (e.g admin.domain.com, operations.domain.com etc)
- CountVonGuetzli 2y ago
  Also, if for example the SaaS you’re running sends a lot of system emails that really shouldn’t end up in spam filters, you can’t afford to let things like marketing campaigns negatively influence your domain’s spam score. Easier and safer to have separate domains.