Apollo Deploy
Apollo Signal · EnterpriseAWS available today

Your cloud.
Your sending infrastructure.

Route every email through your own cloud account. Keep your reputation, committed cloud spend, and audit trail—while Apollo never stores your credentials.
Read the documentation

Customer-owned sending plane

AWS
AWS IAM Identity Center
Amazon Simple Email Service
AWS Cloud

Managed delivery. Your controls stay yours.

ownership summary

Your AWS sending plane

LIVE

Apollo per-send fee

Sending and bandwidth

$0

Typical connection

Pre-filled scoped grant

~60s

Credential isolation

No keys or passwords stored

100%
Deliverability tooling, webhooks, and analytics stay managed by Signal.
Keep the delivery experience managed while your organization retains the sending plane, reputation, billing, and cloud audit trail. Security teams review a narrowly scoped connection; engineering teams keep the operational tooling around every send.
Dedicated reputation. Your sending history is isolated from every other Apollo customer.
Existing cloud economics. Sending costs count toward the agreements and discounts you already have.

One connection. Clear boundaries at every step.

Scoped cloud access

Grant email-sending permission without opening the rest of the account.

Nothing sensitive is stored

Short-lived sessions expire automatically; Apollo stores no access keys.

Automatic fallback

If the customer route disconnects, Signal moves delivery without interruption.

Your cloud economics

Cloud rates, commitments, and isolated reputation stay with your organization.

A connection your security team can inspect before it sends.

Review the narrowly scoped permission in AWS, return one connection identifier, and let Signal verify the route. No access key, secret, or password changes hands.
Start in the Apollo dashboard. An account admin or owner opens Apollo Signal settings and chooses Connect Cloud Account.
Review the pre-filled access request. Apollo opens your cloud console with the organization and sending-only permission scope already prepared. You can see exactly what will be granted before approving it.
Paste the connection ID. AWS returns a connection identifier. Paste it into Apollo to link the accounts—no access key, secret, or password changes hands.
Apollo verifies and activates sending. The connection is checked automatically, delivery tracking stays active, and every email for the organization begins routing through your AWS account.

Built for teams with real ownership requirements.

Bring Your Own Cloud fits the policies, cost structures, and operating model of enterprise teams as a first-class sending option—not a workaround.

Read the Bring Your Own Cloud guide

Amazon Web Services is supported today. Additional cloud providers are on the roadmap.

AWS

Amazon Web Services

Run sending infrastructure in the AWS region you choose, inside your account.

GRC

Compliance teams

Meet data-residency and audit requirements without building a custom email pipeline.

USD

Cloud agreements

Apply existing enterprise discounts and committed cloud spend to email delivery.

REP

Dedicated reputation

Keep your sending history isolated so no other Apollo customer can affect it.

LOG

Audit and oversight

Keep every access event visible in your own cloud account's activity history.

IAM

Security policies

Send exclusively from your account when shared outbound infrastructure is prohibited.

Questions security teams ask before approval

The connection, credential, and continuity details behind Bring Your Own Cloud.

Can't find what you're looking for? Contact our support team

Bring Your Own Cloud

Can't find what you're looking for? Contact our support team

Ready to own your sending infrastructure?

Bring Your Own Cloud is available on the Enterprise plan. An account admin or owner can configure the connection from Apollo Signal settings.
Keep the managed deliverability experience while sending through your own account, reputation, and cloud bill—with automatic fallback if you disconnect.