MaploMaplo
Get started
Back to Maplo
Email

Send from your own inbox.

Bring your own SMTP — Gmail, Outlook, or any custom server. No shared sender reputation. No spam-folder roulette. Your domain, your deliverability, your replies.

Connect your inboxSee email setup
Gmail
david@yourcompany.com
184 / 500
37%
Outlook
hello@yourcompany.com
47 / 300
16%
Custom SMTP
postmaster@yourcompany.com
12 / 1000
1%
AI Draft
Fromdavid@yourcompany.com
Toinfo@bakersyard.co.uk
SubjectQuick question about The Baker's Yard
Hi James, ran a quick audit on bakersyard.co.uk. WordPress 2014, no SSL, 4.2s mobile load. New visitors are likely bouncing…
Sent via your inboxSend
3 ways to connect

Pick the provider you already use.

No new mailboxes to provision. Connect what you have via OAuth or SMTP credentials — Maplo sends through it.

Gmail

OAuth · Google Workspace ready
Free Gmail500/day
Workspace2,000/day
AuthOAuth 2.0

Outlook

OAuth · Microsoft 365 ready
Personal300/day
M36510,000/day
AuthOAuth 2.0

Custom SMTP

Any provider · AWS SES, Postmark, Sendgrid
LimitYour call
AuthPassword
EncryptedAES-256
Deliverability

Your domain reputation. Untouched.

Tools that proxy your mail share their sender reputation with spammers. Maplo sends through YOUR account — your domain, your IP, your SPF/DKIM. No shared pool.

No shared SMTP pool

We never route your mail through Maplo's servers. Every email goes through your own provider's outbound.

SPF / DKIM / DMARC ready

Set them once on your domain. Maplo respects all three. Your sender reputation only depends on your own sends.

Credentials encrypted

OAuth tokens or SMTP passwords stored encrypted at rest (AES-256). Decrypted only at send time, never logged.

Reply-to is you

No 'maplo-noreply@…' headers. Recipient sees your real address, your name, your signature. Replies hit your inbox normally.

The compose flow

Subject + body, generated together.

The AI writes both the subject line and the body in one pass. Each subject is hooky and audit-specific — not “Quick question”.

Fromyou@yourcompany.comSent via your inbox
Toinfo@bakersyard.co.uk
SubjectQuick question about The Baker's Yard
Hi James,

Ran a quick audit on bakersyard.co.uk. WordPress 2014, no SSL, 4.2s mobile load. New visitors are likely bouncing before they see the menu.

We build mobile-first sites for bakeries in 14 days, with two real case studies I can send. Open to a 15-min call this week?

Best,
David
189 wordsNo slop terms
Generated in 4.2s
Why BYO inbox wins

Email that lands in the actual inbox.

Your reputation, not ours

Cold email tools that share IPs get burned together. Maplo never shares — your domain is the only signal recipients' filters see.

Multiple inboxes, one queue

Connect 2-3 inboxes for higher daily throughput. Maplo balances sends to respect each provider's limit.

Unsubscribe + GDPR built-in

Auto-inserted unsubscribe link. Opt-outs tracked in your dashboard. CAN-SPAM and GDPR compliant by default.

Sent looks like sent

Emails appear in your Sent folder normally. Forward, reply, delegate — all native. No black-box behavior.

Common objections

We've heard it before.

The honest answers to the concerns that keep teams on the fence.

“Why BYO instead of Maplo SMTP?”
Shared SMTP pools get burned when one bad-actor user sends spam. Your deliverability depends on strangers. BYO means YOUR domain is the only thing the recipient's filter sees — your sender reputation is yours alone.
“Gmail will block bulk sending.”
Gmail free allows 500/day, Workspace 2,000/day. Maplo respects these limits, randomizes delays (3-7 min between sends), and warms up new addresses. We don't push you past safe thresholds.
“What if I want to send 10,000 emails a day?”
Connect a dedicated SMTP provider (AWS SES, Postmark, Sendgrid) and configure your domain for that volume. Maplo sends through it. The Scale tier supports unlimited daily throughput when paired with proper SMTP.
“Will my Gmail password be safe?”
We never see your password — Gmail/Outlook use OAuth 2.0. You authorize Maplo to send via Google's consent screen. Tokens are stored encrypted (AES-256), revokable from your Google account anytime.
“What about email warm-up?”
If you're sending from a fresh domain, we recommend warming up first (200+ sent to existing contacts over 2-3 weeks). Maplo doesn't auto-warm — that's a separate problem better solved with tools like Mailwarm.
“Can I reply from Maplo?”
No — replies land in your normal Gmail / Outlook inbox. Reply there as usual. Maplo handles outbound only, deliberately. Your conversations stay in your client.
FAQ

Common questions.

  1. 01

    Which providers are supported?

    Gmail (free + Workspace) via OAuth, Outlook (personal + M365) via OAuth, and any custom SMTP server with username/password.

  2. 02

    How are my credentials stored?

    OAuth tokens / SMTP passwords encrypted at rest with AES-256. Decrypted only at send time, never logged or sent anywhere outside our infrastructure.

  3. 03

    What daily limits apply?

    Gmail free: 500/day. Gmail Workspace: 2,000/day. Outlook personal: 300/day. M365: 10,000/day. Custom SMTP: your provider's limit.

  4. 04

    Does Maplo include unsubscribe links?

    Yes — auto-inserted. Tracked in your dashboard. CAN-SPAM and GDPR compliant by default.

  5. 05

    Can I send from multiple addresses?

    Yes. Connect multiple inboxes — Maplo balances sends across them.

Cold email, sent from your own domain.

100 leads/month forever. No credit card required. Cancel anytime.

Connect your inbox free
30-day money-back guarantee