BYOS — Bring Your Own Sending Infrastructure

Bring your own SMTP. Keep control of your sending infrastructure.

Connect Amazon SES, SendGrid, Mailgun, Postmark, or your own SMTP server. AledaMail provides the campaigns, automations, subscriber management, and analytics. You keep ownership of the delivery layer underneath.

What BYOS means

Two layers. You own the bottom one.

An email stack has at least two distinct layers. Most bundled platforms control both and charge accordingly. AledaMail lets you bring your own delivery infrastructure and you pay for the software layer only.

Layer 2 — AledaMail manages this
Email marketing platform
Campaigns, automations, subscriber lists, segmentation, templates, analytics, transactional API, landing pages, bounce handling, unsubscribe management, suppression lists, permissions, MCP integration.
Layer 1 — You own this
Sending infrastructure
Amazon SES, SendGrid, Mailgun, Postmark, or custom SMTP. Your account, your IPs, your sending domain, your reputation, your costs.
Your business
Your application or product
Your CRM, ecommerce platform, SaaS product, customer database, or website. Events flow from here into AledaMail automations.
Why businesses choose BYOS

Reasons to own your sending infrastructure.

BYOS is not always the right choice — but for certain teams, the reasons are substantial.

Cost at scale

Amazon SES charges around $0.10 per 1,000 emails. At meaningful volume, the gap between BYOS delivery costs and bundled-platform costs becomes significant. BYOS gives you full cost transparency: you see the infrastructure bill separately from the software bill.

Sender reputation control

With dedicated IPs on your own account, your sending reputation belongs to you. You are not sharing IP pools with other senders on a shared platform. Warming, throttling, and reputation management are under your control.

Infrastructure portability

Your Amazon SES account, your SendGrid account, your sending domains, and your reputation do not disappear if you switch marketing software. You can change the platform above the infrastructure without rebuilding the delivery layer.

Dedicated sending domains

BYOS makes it straightforward to configure separate sending domains for different use cases — one for marketing email, another for transactional email — with appropriate SPF, DKIM, and DMARC records per domain.

Agency client separation

Agencies can assign separate sending infrastructure to each client. Separate sending infrastructure per client helps isolate reputation and deliverability issues between accounts. Each client's infrastructure can be billed directly to that client's own account.

Existing infrastructure reuse

If your engineering team already uses Amazon SES or SendGrid for transactional email, you can connect AledaMail to the same account. No need to create separate infrastructure for marketing email if it fits your volume and domain strategy.

What AledaMail manages

You do not have to build any of this yourself.

Connecting your own SMTP does not mean building an email platform. AledaMail handles the entire application layer above delivery.

Subscriber management

Import, segment, and manage contact lists. Double opt-in flows, custom fields, tagging, and list hygiene tools built in.

Campaigns and sequences

Drag-and-drop email builder, HTML editor, template library, scheduling, and send-time optimization.

Automations and journeys

Visual automation builder with conditional branching, event triggers, journey variables, wait steps, and multi-branch logic.

Unsubscribe and suppression

Automatic unsubscribe link injection, suppression list management, and compliance with CAN-SPAM and GDPR unsubscribe requirements.

Bounce and complaint handling

Processes bounce and complaint feedback from your sending provider. Hard bounces are suppressed automatically. Complaint rates are tracked.

Analytics and reporting

Open rates, click rates, bounces, unsubscribes, and conversion tracking per campaign. Automation performance reporting included.

Transactional email API

A separate REST API for sending transactional messages — password resets, receipts, notifications — through the same infrastructure with separate tracking.

Landing pages

Visual landing page builder for signup forms, lead capture, and opt-in pages. Connect directly to subscriber lists.

Segmentation

Segment by subscriber properties, engagement history, custom events, tags, and journey state. Combine conditions with AND/OR logic.

Supported sending providers

Connect the provider that fits your infrastructure.

AledaMail connects to the major transactional email providers and any standard SMTP server. Each provider has its own strengths for different situations.

Amazon SES

Very low cost at scale. Part of the AWS ecosystem. Good choice if your team already runs infrastructure on AWS. Requires more configuration work upfront — sandbox removal, feedback loops, dedicated IPs are optional add-ons.

AledaMail + Amazon SES →

SendGrid

Well-documented API with a generous free tier. Strong deliverability tooling. Good for teams that want a straightforward setup and do not want to manage raw AWS infrastructure.

AledaMail + SendGrid →

Mailgun

Developer-focused provider with strong routing and inbound email features. Good for SaaS products that need both outbound marketing and inbound reply processing on the same infrastructure.

AledaMail + Mailgun →

Postmark

Focused exclusively on transactional deliverability. Strong reputation for reliable inbox placement on account notifications, password resets, and receipts. Higher per-email cost than SES but simpler to operate.

AledaMail + Postmark →

AledaMail also connects to any standard SMTP server, including private mail servers, self-hosted infrastructure, and providers not listed here.

Responsibility split

What your provider handles. What AledaMail handles.

Understanding the boundary between the two layers helps you plan your infrastructure and troubleshoot issues correctly.

Responsibility Your sending provider AledaMail
Message transport and delivery✓ Provider
IP infrastructure and reputation✓ Provider
SMTP / API submission endpoint✓ Provider
Bounce event feedback✓ Provider (webhook)✓ Processes and suppresses
Complaint feedback✓ Provider (feedback loop)✓ Tracks and suppresses
Dedicated IP provisioning✓ Provider
SPF / DKIM / DMARC setupConfiguration on your domain✓ Guidance and verification
Subscriber list management✓ AledaMail
Campaign creation and scheduling✓ AledaMail
Unsubscribe link injection✓ AledaMail
Suppression list management✓ AledaMail
Automations and journeys✓ AledaMail
Analytics and reportingDelivery stats only✓ Full campaign analytics
Transactional email APIRaw send API✓ Template-driven REST API
Landing pages✓ AledaMail
Common questions

Questions about BYOS email marketing.

What is BYOS email marketing?

BYOS (Bring Your Own Sending infrastructure) means connecting your own email delivery provider to an email marketing platform. You supply the account with a provider like Amazon SES, SendGrid, Mailgun, or Postmark. The marketing platform — AledaMail in this case — handles everything above delivery: campaigns, automations, subscriber management, analytics, and compliance tooling.

Can I use my own SMTP server with an email marketing platform?

Yes. AledaMail connects to any standard SMTP server. You configure the host, port, credentials, and sending domain once. AledaMail routes all campaign and transactional email through it. This includes Amazon SES SMTP endpoints, custom mail servers, and private infrastructure.

Why use software on top of Amazon SES?

Amazon SES is a message delivery API — it accepts email and delivers it. It does not manage subscriber lists, build campaigns, run automations, process unsubscribes, or generate analytics. If you want to run email marketing on SES, you need a platform above it. AledaMail provides that platform while keeping your SES account under your control.

Does bringing my own SMTP mean I have to build unsubscribe and bounce management myself?

No. AledaMail handles unsubscribe link injection, suppression list management, bounce classification, and complaint tracking automatically. Your sending provider delivers the messages. AledaMail processes the compliance and deliverability signals that come back.

Can different clients use different sending infrastructure?

Yes. In agency mode, each client workspace can have its own sending server configuration. One client can use their Amazon SES account, another can use SendGrid, and another can use shared infrastructure you manage. Reputation and billing remain separate per client.

Can I use dedicated IPs with BYOS?

Yes, if your sending provider offers dedicated IPs. Amazon SES and SendGrid both offer dedicated IP options. You configure the dedicated IPs on your provider account. AledaMail routes through whatever infrastructure your provider account has configured.

What happens to my sending infrastructure if I stop using AledaMail?

Your sending provider account, your dedicated IPs, your sending domains, and your sender reputation remain yours. They are not tied to AledaMail. You can connect a different marketing platform to the same infrastructure without starting over.

When BYOS is not the right choice

BYOS requires more initial configuration — setting up a provider account, verifying domains, configuring feedback loops, and in some cases getting out of sandbox mode. It adds an operational layer your team needs to manage.

If you want a fully managed sending experience where the provider handles reputation, deliverability, and IP management without any configuration on your side, a bundled platform like Mailchimp or Klaviyo may be simpler to start with.

BYOS is most valuable when you have meaningful volume, need cost predictability, want infrastructure portability, or need client-level sending separation. At low volume with simple requirements, the configuration overhead may not be justified.

Related

Go deeper on the infrastructure question.

Start with your own sending infrastructure.

Connect Amazon SES, SendGrid, Mailgun, Postmark, or your own SMTP server. Free to start.

Start free →