Skip to content
BUNDLE · GUARANTEED OUTCOME

Fresh IP to production in 30 days.
Engineered warmup at €199 setup + €199/month.

New IPs require warmup. Skip it and the receivers throttle you immediately, or worse, flag the IP as snowshoe and damage reputation before sending starts. Most senders know this; few have the discipline to run a clean 30-day warmup with engagement simulation, daily volume controls, and monitoring at every step.

We handle the discipline. You get a dedicated IPv4 from a clean range, custom rDNS aligned to your sending domain, DKIM/SPF/DMARC/MTA-STS configured, automated warmup schedule ramping to ~1,500 daily by day 30 (with extension path to 50K daily over 60-90 days), engagement signals from a curated network, and weekly Telegram reports. €199 one-time setup, €199/month for the warmup period. No recurring cost after warmup completes if you keep the IP.

Order on Telegram → See the schedule
setup fee €199 one-time
monthly €199 / month
duration 30 days standard
target volume ~1,500/day day 30
why warming exists

The mechanic that makes warming necessary.

Receivers (Gmail, Outlook, Yahoo, Apple, AOL, and the long tail of smaller providers) treat new IPs with caution. The rationale is reasonable: an IP that has never sent mail before could be anything. Could be a legitimate new sender; could be a botnet that just spun up. Receivers don't know, so they hedge. Volume from new IPs gets throttled aggressively, content classifiers apply higher scrutiny, placement tilts toward spam folder until reputation accumulates.

Reputation accumulates from observed behaviour: volume sent per day, complaint rate from recipients, engagement (opens, replies, not-spam markers), authentication consistency, list quality signals. Over weeks, these signals aggregate into a per-IP reputation that determines placement decisions. Established IPs with months of clean history get inbox placement at high volumes; new IPs with no history get throttled until they earn that placement.

Warmup is the discipline of building reputation without triggering the early-IP suspicion mechanisms. The pattern works: start with low daily volume that won't trigger throttling, ramp logarithmically over weeks, send to engaged recipients who generate positive signals (opens, replies, not-spam markers), maintain consistent authentication, stay below complaint thresholds. After 30 days of disciplined warmup, an IP has enough history to handle production volume at ~1,500 daily; over 60-90 days, extends to 50K+ daily depending on engagement quality.

The shortcut path (skip warming, send full volume from day 1) fails predictably. Receivers throttle, queue depths climb, messages defer or bounce, content classifiers flag the unusual pattern, RBL listings appear within days, reputation enters a damaged state that takes 60+ days to recover from (Reputation Recovery, €999). The warmup fee is small relative to the cost of skipping it.

30-day warmup curve

Daily volume schedule.

Hover or tap any day to see target volume for that day, cumulative sent, and what's happening at the receiver side. The curve is logarithmic, not linear, because reputation builds non-linearly with volume signal.

day 15 of 30

Mid-warmup acceleration

By day 15, daily volume reaches ~700 messages. IP has accumulated 2 weeks of consistent signals: authenticated mail, low complaints, positive engagement from curated network. Receivers begin shifting placement from "cautious" toward "established sender" treatment.

Postmaster Tools shows rating climbing toward "high"; SNDS score improving. Engagement signal from curated network is at peak intensity here: ~85% open rate, ~30% reply rate from real opt-in mailboxes that mark mail as not-spam.

Schedule is approximate; actual day-by-day volume adjusts based on observed reputation signals. If complaint rate spikes or RBL listing appears, schedule pauses until issue investigated. About 5% of warmups extend beyond 30 days due to slower-than-expected reputation accumulation; we don't charge extra for the extension.

where the €199 + €199 goes

Cost breakdown.

Click each component to see what the fee covers and what it would cost separately if you assembled it yourself. Total DIY equivalent: ~€450 setup + ~€280/month, before counting your time managing the warmup.

component detail

Dedicated IPv4 from clean range

IPv4 allocation from a /24 block with no shared-tenant history, pre-checked across 84 RBLs at allocation time. Jurisdiction selectable (BG, RO, MD, PA, HK, SG, UA). Reserved exclusively for your warmup through completion; remains yours after warmup at €8/month ongoing.

DIY equivalent: most VPS providers include shared IPs (€0 incremental but reputation-shared). Clean dedicated IPs from boutique providers cost €15-40 setup + €5-15/mo ongoing depending on quality of range and pre-checking discipline.

DIY assembly total ~€450 setup + ~€280/month
WaaS bundled price €199 setup + €199/month
Savings ~€250 setup + ~€80/month + your time
vs alternatives

WaaS vs DIY warmup vs Mailwarm/Lemwarm.

Different products, different scope, different cost structures. Toggle to highlight what matters for your case. Mailwarm/Lemwarm are mailbox warmup tools (different category); we list them anyway because customers often confuse the two.

  us
Warmup-as-a-Service		 DIY warmup
(your team)		 Mailwarm / Lemwarm
(mailbox warmup tools)
Warms what Dedicated IPv4 (infrastructure layer) Whatever you set up Mailbox (Google Workspace, Outlook 365)
Includes IP allocation Yes (clean range) You source separately No (use existing mailbox)
Includes DNS authentication Yes (SPF, DKIM, DMARC, MTA-STS) You configure separately You configure (mailbox-side)
Includes engagement signals Yes (curated network) You source or skip Yes (peer warmup network)
Setup cost €199 one-time €450+ DIY assembly $0 setup
30-day cost €199 (warmup period) ~€280/mo equivalent + your time $29-79/mo per mailbox
Ongoing cost after warmup €8/mo (IP retention) or cancel Whatever you maintain $29-79/mo (continues)
Volume cap enforcement MTA-level hard cap Self-discipline (often slips) Tool-level (fine for mailboxes)
RBL monitoring during warmup 84 RBLs every 15 min Manual checks usually Limited (mailbox doesn't get RBL'd)
Risk of DIY mistakes Low (delegated to specialists) Real (warmup mistakes are common) Different category (no IP-warmup risk)
Day-30 outcome ~1,500 daily, established reputation Variable (good if disciplined) Mailbox warm but no IP reputation
Best for Self-hosted MTAs, dedicated infrastructure Operations with deliverability engineer Cold outreach via Google Workspace
Wrong fit when Single Google Workspace mailbox warmup Limited deliverability expertise Self-hosted MTA infrastructure

Mailwarm and Lemwarm are good products for what they do. They warm individual mailboxes for cold outreach via Google Workspace or Outlook 365 by simulating peer engagement. They don't warm IPs; they don't apply to self-hosted MTA infrastructure. WaaS is the right product for self-hosted sending; mailbox warmup tools are right for SaaS-mailbox sending. The two categories don't compete; they solve different problems.

honest fit assessment

Who orders WaaS, who shouldn't.

good fit
  • Self-hosted MTA operations (PowerMTA, MailWizz, Postfix, custom) needing fresh IP brought to production reputation. Most common WaaS customer profile.
  • Existing operations adding capacity. Already running on warmed IPs, scaling to add another. WaaS handles the new IP without disrupting existing operations.
  • Recovery customers (post Reputation Recovery) wanting fresh IP after damaged-IP rehabilitation completes. Clean restart with no historical baggage.
  • Operations valuing predictable timeline. Fixed €199 + €199 over 30 days vs unpredictable DIY duration with possible rework if mistakes made.
  • Operations without deliverability engineer. WaaS replaces the engineer-time required for disciplined warmup. Common case for ops where deliverability falls between roles.
  • Multi-IP fleet builds. Order WaaS for each IP needed; bulk pricing applies past 5 IPs (€169 setup + €169/mo each).
poor fit
  • Single Google Workspace mailbox cold outreach. Mailwarm or Lemwarm fits this case better. WaaS warms IPs; mailbox warmup tools warm mailboxes. Different categories.
  • You don't have a sending stack ready. Warming an IP without traffic to send afterwards wastes the warmup; reputation decays without sustained sending. Build the stack first; warm second.
  • You expect day-31 sending at 50K daily. Day 30 reaches ~1,500 daily. Extending to 50K daily requires another 30-60 days of continued ramping. We can extend warmup at €199/month if needed; most customers don't need that capacity immediately.
  • You plan to send unsolicited bulk after warmup. Receivers detect content patterns regardless of IP warmth. Warmed IP sending unsolicited mail still gets RBL-listed within days. Warmup is necessary but not sufficient; sending practices matter more.
  • Operations under 5K daily. Warmup overkill at this scale. SMTP relay shared-IP service or hosted ESP fits better; dedicated IP only justified at higher volumes.
  • You want immediate (day-1) sending. Warming takes 30 days. If business need is "send 10K today," WaaS won't help; consider managed SMTP relay temporarily while a separate WaaS proceeds in parallel.
scope of warmup

What's in the €199 + €199.

01

IP allocation from clean range

IPv4 from a /24 block we maintain with active monitoring for clean reputation. Pre-checked across 84 RBLs at allocation time; if any listing detected, IP gets swapped before delivery. Jurisdiction selectable: Bulgaria, Romania, Moldova, Panama, Hong Kong, Singapore, Ukraine.

IP is reserved exclusively during warmup. After day 30 handover, IP remains yours at standard €8/month (Extra Dedicated IPv4 pricing). Most customers continue ongoing operations rather than cancel.

02

DNS authentication setup

SPF record published with explicit ip4: declarations. DKIM keypair generated (2048-bit RSA), private key in HSM, public key DNS record published under your domain. DMARC record published at p=none with rua= reporting initially; can shift to quarantine/reject after warmup stabilises.

MTA-STS policy file at canonical .well-known location with mode=enforce. TLS-RPT record for delivery reports. BIMI record bootstrapped if eligible. All authentication verified before first warmup send via independent test from external infrastructure.

03

Custom rDNS configured

Per-IP PTR record matching your sending domain pattern. Examples: mta.brand.com, send01.brand.com, your custom convention. FCrDNS (forward-confirmed reverse DNS) verified: PTR points to hostname, hostname resolves to original IP. HELO/EHLO in MTA configured to match.

04

30-day automated warmup schedule

Logarithmic ramp from ~50 messages day 1 to ~1,500 day 30. Daily volume cap enforced at MTA-level pickup directory; you cannot accidentally overshoot the schedule. Schedule adjusts based on observed reputation signals (Postmaster Tools rating, SNDS score, RBL status, complaint feedback).

About 5% of warmups extend beyond 30 days due to slower-than-expected reputation accumulation (often related to specific receiver behaviour at that moment). Extension included in original price; we don't charge for extra time.

05

Engagement signals from curated network

~14 ISPs, ~8,400 real opt-in mailboxes generating opens, replies, and not-spam markers throughout warmup. Network participants receive contextually appropriate messages during the warmup; engagement is genuine rather than simulated, which receivers can distinguish.

Engagement intensity peaks at days 10-20 when reputation building benefits most from positive signals. By day 30 engagement settles toward typical commercial sending patterns; the curated network gradually disengages as real recipients begin generating signals.

06

84-RBL continuous monitoring

All 84 major RBLs polled every 15 minutes throughout warmup. Spamhaus (SBL, CSS, XBL, DBL), Barracuda, SORBS, UCEPROTECT (1, 2, 3), SURBL, Invaluement, Lashback UBL, and the rest. Listings detected within 15 minutes of appearing.

Listings during warmup are rare on properly-run programs (under 1% of warmups) but do happen. We handle delisting at no charge for listings caused by external factors (range listings, false positives). Self-inflicted listings (caused by content sent through warmup network) require investigation; rare in practice.

07

Weekly Telegram reports

Sent each Monday during warmup. Includes: volume sent previous week, engagement metrics from curated network, current Postmaster Tools rating, current SNDS score, RBL status across all 84 lists, week-ahead schedule, any anomalies or concerns flagged.

08

Final attestation document at handover

Day-30 deliverable. PDF document showing: warmup completion confirmation, final daily volume reached, Postmaster Tools and SNDS final ratings, RBL status (clean), authentication verification results, recommended ongoing volume strategy, recommended pace for ramping toward higher volumes if needed.

Document is audit-ready format suitable for compliance reviewers, vendor due diligence, internal QA. Format refined through customer use across multiple compliance and audit contexts.

questions before you order

Frequently asked.

Why does warming take 30 days, not less?

Receivers track sending patterns across days and weeks. A new IP that sends 50K on day 1 looks suspicious; the same IP sending logarithmically ramping volume across 30 days looks like a legitimate sender establishing reputation. Compressing the timeline below 30 days produces fragile reputation that collapses under volume.

Some vendors offer "rapid warmup" in 7-14 days. The outcomes don't hold; reputation built that fast doesn't survive sustained volume. We've audited operations using rapid-warmup services and found 60-70% of them needed Reputation Recovery within 90 days. The slow path is the efficient path.

What if my warmup gets RBL-listed during the process?

Rare on properly-warmed clean IPs but does happen. Our 84-RBL polling detects within 15 minutes; we handle delisting at no charge if the listing was caused by external factors (range listings, false positives).

Self-inflicted listings (caused by content patterns from warmup network engagement) require investigation. We reset the warmup if needed and continue. About 1% of warmups encounter listings; nearly all caused by external factors and resolved without warmup reset.

Can I send my own mail during the warmup?

Day 15 onward, yes, in coordination with us. The schedule includes "real customer mail" capacity from day 15; before that, only curated-network engagement runs. Customer mail integrates into the schedule rather than running in parallel; you submit to the warmup pickup directory and the MTA sends within daily volume cap.

Sending outside the schedule (overshoot the daily cap, send before day 15) breaks the warmup. The MTA-level cap prevents accidents; if you have specific business need to deviate, we discuss before warmup begins and adjust the plan.

What happens after day 30?

IP transitions to ongoing operation at €8/month (standard Extra Dedicated IPv4 pricing). All authentication remains in place. Custom rDNS continues. RBL monitoring continues as part of standalone Deliverability Monitoring (€49/mo) if you subscribe.

About 90% of customers continue ongoing operations rather than cancel. The IP retains reputation built during warmup; cancelling means another warmup later if you want a fresh IP. Most operations build IP fleet gradually rather than warm-and-discard.

What's the actual day-30 capacity?

~1,500 daily volume sustainable from day 30. Some customers stop here; for many use cases that's sufficient. For higher capacity (5K, 25K, 50K daily), continued ramping over 60-90 additional days. Standard pricing extends warmup at €199/month for additional 30-day extensions if needed.

Skipping the gradual extension and jumping to 50K on day 31 typically triggers throttling and reputation damage. The 30-day standard warmup gets you to sustainable production-grade reputation; extension pushes the volume ceiling without breaking reputation.

Do I bring my own sending domain?

Yes. You provide one or more sending domains; we configure DNS authentication for the domain(s) and warm the IP in association with the domain(s). Most customers use 1-3 sending domains during warmup; we handle that range without additional fees.

For 4+ sending domains, Multi-domain Warmup (€599) fits better than WaaS with extra-domain configuration. WaaS optimises for 1-3 domains per IP; Multi-domain Warmup optimises for 4-10 domains.

Can I cancel mid-warmup?

Yes via Telegram. Setup fee (€199) is non-refundable since the work has been done. Monthly fee prorates to cancellation date. Cancellation mid-warmup means losing the warmup work; reputation built during partial warmup decays if sending stops.

About 2% of warmups get cancelled mid-process, usually because business circumstances changed. We don't penalise; we just confirm and stop work. If you want to restart later, we'll quote fresh; warmups don't resume cleanly after multi-week gaps.

Bulk pricing for fleet warmups?

Yes. 5+ IPs simultaneously: €169 setup + €169/mo each. 10+ IPs: €149 setup + €149/mo each. 25+ IPs: custom quote. Bulk pricing reflects efficiency gains in running warmups in parallel; per-IP discipline doesn't decrease, just the per-IP cost overhead.

How does payment work?

Setup fee (€199) charged at order; first month (€199) charged at warmup start. Subsequent months billed in advance if warmup extends. Payable in any of our 11 supported cryptocurrencies via self-hosted BTCPay. Pre-paid 6-month subscription post-warmup gets 5% discount on monthly retention fee.

also relevant

Related services and references.

project

Multi-domain Warmup

For 4-10 sending domains warmed simultaneously rather than single-IP. €599.

→ one-time

DNS Authentication Setup

Standalone authentication setup if not bundling warmup. €99.

→ recurring

Extra Dedicated IPv4

Post-warmup IP retention at €8/month. Most customers continue ongoing.

→ recurring

Deliverability Monitoring

Continuous reputation tracking after warmup completes. €49/month.

→ project

Reputation Recovery

For damaged IPs needing rehabilitation rather than fresh warmup. €999.

→ reference

IP warming reference

Background on warmup mechanics, receiver behaviour, scaling considerations.

→

Warmup as a service: what we actually do during the engagement

Warmup as a service handles the operational work of bringing new sending infrastructure to production reputation. The service covers what operators frequently underestimate: the daily attention required during the 30-45 day warmup window plus the diagnostic work when warmup encounters obstacles.

Daily operations during warmup: monitoring receiver-side reputation across the major signal sources, executing the warmup volume progression on schedule, diagnostic investigation when reputation indicators deviate from expected patterns, adjustment of warmup volume when receiver-side feedback indicates necessary changes, coordination with customer-side teams when content or list adjustments would support warmup progression.

The daily attention matters because warmup is not a passive process. Volume progression schedules that look reasonable in advance often need adjustment based on actual receiver-side behavior; the adjustment requires daily observation rather than schedule-execution alone. Customers who attempt warmup without daily attention typically extend the warmup window by 30-50% or produce reputation events that require additional remediation work beyond the originally-scoped warmup.

Beyond daily operations, the engagement covers: warmup completion validation when reputation indicators confirm stable production-ready status, transition planning to customer ongoing operations, documentation of warmup outcomes and lessons learned for future infrastructure additions, follow-up support during the first 30 days of post-warmup production operation.

Warmup progression schedules and the reasoning behind them

The warmup progression schedules we use have evolved through 2024-2026 as receiver-side enforcement has tightened. The schedules below capture current best practice rather than the more aggressive schedules that worked in earlier periods.

Standard 30-day warmup (most common): Day 1-7 starting at 50-100 daily volume to most-engaged recipient segments, Day 8-14 scaling to 500-1000 daily, Day 15-21 reaching 2500-5000 daily, Day 22-30 reaching production volume up to 10K-15K daily. The pacing matches receiver tolerance for new sender introduction without triggering rate limits or anomaly detection.

Extended 45-day warmup (for higher target volumes): Day 1-10 starting at 100 daily, Day 11-20 scaling to 1000 daily, Day 21-30 reaching 5000 daily, Day 31-40 reaching 20000 daily, Day 41-45 reaching production volume up to 50K daily. The extended schedule supports target volumes above the standard 30-day window can reach without producing reputation events.

Compressed 14-day warmup (for warm-handoff scenarios): suitable when migrating sending from existing infrastructure with established domain reputation to new infrastructure that needs IP reputation built. The compression works because the domain reputation already exists; only the IP reputation needs warmup. Day 1-3 at 500 daily, Day 4-7 at 2500 daily, Day 8-14 at production volume.

Custom schedules for specific situations: ESP migrations with simultaneous infrastructure and domain changes, multi-region warmup with different schedules per region, operational constraints affecting timing (audit windows, customer-facing communication requirements). Custom schedules are designed during engagement scoping based on specific operational requirements.

Pricing structure and engagement timing

Warmup as a service runs as a project engagement with fixed pricing based on scope rather than time-and-materials billing. The fixed pricing produces predictable customer cost without exposure to scope expansion during the engagement.

Standard 30-day warmup for single sending infrastructure: EUR 1,200. Covers the daily operational work plus the diagnostic capacity for typical warmup progression. Suitable for new IP allocation, new sending domain, or new infrastructure deployment within standard operational parameters.

Extended 45-day warmup for higher-volume targets: EUR 1,800. Covers the longer engagement window plus the additional complexity of higher-volume operations. Suitable for senders building toward 50K+ daily volume on new infrastructure.

Multi-pool warmup engagements (warming multiple IPs or domains simultaneously): pricing reflects the operational scope. Two-pool warmup runs EUR 2,000; three to five pools run EUR 800-1,200 per additional pool beyond the first; larger multi-pool engagements are quoted case-by-case.

Engagement timing: optimal warmup engagement starts before the infrastructure is needed for production traffic. Last-minute warmup engagements (infrastructure already deployed and underperforming, need to recover quickly) are possible but typically take longer because the infrastructure has accumulated suboptimal initial reputation that complicates the warmup. We can engage on both schedules but recommend planning ahead when operationally possible.

Ready to warm your IP properly?

Telegram order takes 10 minutes. IP allocated within 24 hours, DNS authentication published within 48, warmup begins on confirmed sending domain. Day-30 handover with attestation document. Cancel anytime, setup fee non-refundable.

Order on Telegram → Submit ticket

# Median Telegram response: 12 minutes during operating hours