> ## Documentation Index
> Fetch the complete documentation index at: https://help.pipelime.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# PipeLime managed infrastructure

> Why cold outreach belongs on separate domains, and what a managed domain and mailbox include.

export const Screenshot = ({id, alt, caption, frame = 'browser', url, marks = [], lang = 'en', workspace = 'northwind-outbound'}) => {
  const src = `/images/screenshots/${lang}/${id}.png`;
  const chrome = url ? `app.pipelime.ai/${workspace}${url}` : 'app.pipelime.ai';
  return <figure className={`pl-shot pl-shot--${frame} not-prose`}>
      <div className="pl-shot__frame">
        {frame !== 'bare' && <div className="pl-shot__bar">
            <span className="pl-shot__dots">
              <span className="pl-shot__dot" />
              <span className="pl-shot__dot" />
              <span className="pl-shot__dot" />
            </span>
            <span className="pl-shot__url">{chrome}</span>
          </div>}
        <div className="pl-shot__media">
          <img src={src} alt={alt} loading="lazy" />
          {marks.map(mark => <span key={mark.n} className="pl-shot__mark" style={{
    left: `${mark.x}%`,
    top: `${mark.y}%`
  }} aria-hidden="true">
              {mark.n}
            </span>)}
        </div>
      </div>
      {caption && <figcaption className="pl-shot__caption">{caption}</figcaption>}
    </figure>;
};

PipeLime managed infrastructure is a set of sending domains and mailboxes we register, configure and warm up for you. They stay separate from your main domain, so the cold outreach you send through them never goes out from it.

<div className="pl-availability">
  <div className="pl-availability__row">
    <div className="pl-availability__label">Where</div>
    <div className="pl-availability__value"><span className="pl-path">Email Accounts<span className="pl-path__sep">→</span>Add senders<span className="pl-path__sep">→</span>Done-for-you infrastructure</span></div>
  </div>

  <div className="pl-availability__row">
    <div className="pl-availability__label">Your role needs</div>
    <div className="pl-availability__value">Read access to Done-for-you infrastructure <code>read-domains</code>. Admin, Member and Viewer have it by default.</div>
  </div>

  <div className="pl-availability__row">
    <div className="pl-availability__label">To create</div>
    <div className="pl-availability__value"><code>create-domains</code> on top of the permission above.</div>
  </div>

  <div className="pl-availability__row">
    <div className="pl-availability__label">Partner-branded workspaces</div>
    <div className="pl-availability__value">Not shown in partner-branded workspaces.</div>
  </div>

  <div className="pl-availability__note">The order wizard for PipeLime managed infrastructure, inside the Add senders overlay. Needs the managed-infrastructure flag and is hidden entirely for partner-branded tenants. The fulfilled result is the Domains page. If you cannot find this in your sidebar, your workspace may have a custom menu configuration. Contact support and we will check it for you.</div>
</div>

## How it behaves

### Why cold outreach needs its own domain

Cold outreach means sending a lot of email, and some of it always lands in spam: inbox
providers remember which domain that mail came from. Managed infrastructure keeps that away
from your main domain. The mailboxes sit on separate lookalike domains that redirect to your
real website, so replies and clicks still reach you while your main domain stays out of the
conversation. If a sending domain wears out it can be replaced, and the domain your customers
and inbox providers already trust is never the one carrying the risk.

That is an argument for managed infrastructure, not a rule the product enforces. The same
screen offers **Connect your email**, which sends from an inbox you already own, and outreach
does go out from whatever you connect there.

<Screenshot id="email-accounts/managed-infrastructure--why-dialog" frame="bare" alt="The How this protects your domain dialog: three short paragraphs explaining why cold outreach uses a separate domain, over a Got it button" caption="The plain-language version of the same idea, one tap away from the order screen." />

### What a managed domain and mailbox include

An order is built from three pieces. **Fresh domains** (1) protect your main domain's
reputation. **Ready mailboxes** (2) arrive already created, configured and connected as email
accounts, with nothing left to set up yourself. **Warmup included** (3) means each mailbox
starts building sending reputation as soon as it goes live, before it carries a campaign.

You say how much you want to send. We register the domains, create the mailboxes and configure
DNS.

Warm-up is a switch rather than a fixture. **Start warmup automatically** sits on the review
and pay step and is on by default. Turn it off and the mailboxes arrive without it.

<Screenshot id="email-accounts/managed-infrastructure--intro" url="/senders" alt="The managed-infrastructure order screen: the eyebrow PipeLime managed infrastructure, the heading Your sending engine, built for you, and three cards: Fresh domains, Ready mailboxes and Warmup included, above a Choose my domains button" caption="The three pieces an order is made of. Warm-up is the one you can switch off." marks={[{ n: 1, x: 28, y: 50 }, { n: 2, x: 50, y: 50 }, { n: 3, x: 72, y: 50 }]} />

### No screen names the vendor

Someone else registers the domains and runs the mailboxes, and no screen in the product names
them. On a domain record, the vendor, its identifiers there and its raw vendor-side status are
returned only to PipeLime's own staff: the gate is a system role attached outside any
workspace, so no workspace role of yours reaches those fields. If an order is rejected, the
reason a member of staff wrote is put through a filter that swaps the vendor's name out before
you read it.

Once a managed mailbox is live it sits on the Email Accounts list like a mailbox you connected
yourself. The small provider logo beside the address is PipeLime's own, and hovering it names
PipeLime rather than the vendor. On a partner-branded workspace both resolve to the partner's
brand instead.

<Screenshot id="email-accounts/managed-infrastructure--managed-sender-row" url="/senders" alt="A mailbox row on the Email Accounts list for a managed address, with a small PipeLime logo beside the email address where a connected mailbox shows its provider's logo" caption="Nothing on the row hints that another company registered the domain or runs the mailbox." />

## Limits

|                                                |                                                                                                           |
| ---------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
| What one order covers                          | The domains we register and their DNS, the mailboxes created on them, and warm-up                         |
| Warm-up                                        | **Start warmup automatically**, on the review and pay step: on by default, and you can switch it off      |
| If a sending domain wears out                  | It can be replaced. The domain your customers and inbox providers trust is never the one at risk          |
| Who can see which vendor backs a domain        | PipeLime staff only. The vendor fields on a domain record are never returned to a workspace, at any role  |
| What names a managed mailbox on Email Accounts | PipeLime's own logo, and PipeLime's name when you hover it. Your partner's on a partner-branded workspace |
| Where the vendor name is stripped out          | The reason shown on a rejected order                                                                      |

## Related

<CardGroup cols={2}>
  <Card title="Order managed domains and mailboxes" icon="rocket" href="/en/email-accounts/order-managed-domains-and-mailboxes">
    Walk the order wizard end to end: domains, mailboxes, review and pay.
  </Card>

  <Card title="Track provisioning and manage your domains" icon="activity" href="/en/email-accounts/provisioning-status-and-domains-page">
    The order status board, and the Domains page your mailboxes land on.
  </Card>

  <Card title="Email Warm-up: how it works" icon="mail" href="/en/email-accounts/email-warm-up">
    What the warm-up an order starts for you actually does.
  </Card>

  <Card title="Add-ons: website tracking capacity, whitelabel and managed infrastructure" icon="credit-card" href="/en/billing/add-ons">
    Where managed domains and mailboxes show up on your subscription.
  </Card>
</CardGroup>