SMTP Relay: Starter
Dedicated IP, manual warmup
- Volume
- 50,000 emails/mo
- Dedicated IPv4
- 1
- Warmup
- Manual schedule provided
- Custom rDNS
- ✓
- Bounce + FBL
- ✓
- IP rotation
- ✗
- Monitoring
- Basic
- Datacenter
- BG / RO
Pick line items, pick a pre-engineered bundle, or assemble a stack from scratch. Pricing is in EUR; conversion to your preferred cryptocurrency happens at invoice. Anything quoted as "from €X" is the entry tier. Most customer setups are at or slightly above the listed price after addons.
Three tiers covering 50K to multi-million monthly volumes. All ship with custom rDNS, DKIM, SPF, DMARC and bounce handling pre-configured.
Dedicated IP, manual warmup
Managed warmup, dedicated pool
Multi-IP rotation, custom architecture
For when you don't want to assemble a deliverability stack piece by piece. Every bundle is a complete configuration we've delivered before, with predictable outcomes.
New IP → 50 K/day in 30 days, or your money back
For agencies running multi-mailbox campaigns
Launch your own Email Service Provider
Damaged IP/domain rehabilitation
GDPR Article 28 DPA + SOC 2 evidence + ISO 27001 alignment for enterprise procurement.
Operational privacy as engineering: Tor hidden service mirror, Monero billing, clearnet/onion isolation, log discipline.
Migrate from Mailchimp/Klaviyo/HubSpot to self-hosted PowerMTA + MailWizz without a deliverability cliff.
Active-passive or active-active email infrastructure across two or three datacenter regions with DNS health-check failover.
Coordinated infrastructure for 10-25 sending domains: registration, DNS, hosting, brand isolation in one operational unit.
Bare-metal servers in our datacenters. Configurable within reasonable bounds; if you need a specific NIC, RAID controller or RAM density, ask before ordering.
Dedicated bare-metal
Dedicated bare-metal
Dedicated bare-metal
KVM-virtualised, NVMe storage, dedicated CPU cores at the higher tiers. Suitable for MailWizz, PowerMTA front-ends, monitoring stacks, and supporting infrastructure.
Engineering work scoped as a discrete deliverable. Useful when you need a specific outcome rather than ongoing infrastructure. Click any item for the full scope.
Monthly addons for specific operational needs. Stack on top of any SMTP tier or server. Click for the full scope of each.
The three structural ways to engage with us are SMTP tiers (Starter, Pro, Scale) for ongoing sending operations, bundles for specific situations (cold outreach, newsletter migration, reputation recovery, privacy stack), and assembled stacks built from individual line items. Each fits a different customer situation and the wrong choice produces unnecessary cost in one direction or operational friction in the other.
SMTP tiers are the right fit for senders who know their volume envelope, have stable sending patterns, and want predictable monthly costs. Starter covers 50K to 250K monthly sends with one dedicated IPv4, Pro covers 250K to 1M with two dedicated IPs and bounce processing, Scale covers 1M+ with multi-IP rotation and per-pool monitoring. Senders with seasonal volume swings or unclear volume projections often start at one tier and migrate to another within the first six months; the migration is free and carries no warmup penalty because the IPs are already warmed.
Bundles are the right fit for senders with a specific operational situation that matches one of the four bundle shapes: cold outreach at scale, migration from a managed platform, recovery from an incident, or greenfield privacy-positioned launch. Bundles are not strictly cheaper than assembling equivalent line items, but they remove the design work of figuring out which line items are needed and in what configuration. For a customer engaging us for the first time with a defined situation, the bundle is almost always the better starting point even if a custom stack might shave 5-10% off the cost.
Assembled stacks are the right fit for senders with unusual requirements that none of the standard tiers or bundles address cleanly: multi-region deployments, custom hardware specifications, hybrid configurations across our infrastructure and customer-owned equipment, regulatory compliance overlays. These engagements start with a discovery conversation rather than a service order, and pricing reflects the specific configuration rather than following the published rate card.
Pricing across the catalogue is in EUR. The actual amount payable depends on the cryptocurrency selected at invoice; conversion happens at the time of invoice generation rather than at the time of payment, which protects both sides from short-term volatility. Customers who pay in stablecoins (USDT, USDC, DAI) see effectively the same amount month to month; customers who pay in volatile cryptocurrencies (BTC, ETH, XMR) see amounts that fluctuate with market conditions over their billing period.
The price on each line item is the operating price, not a marketing entry point. SMTP tiers include the dedicated IPv4, 30-45 days of pre-warmup before customer traffic begins, custom reverse-DNS aligned to HELO, DKIM keypair generation and rotation, SPF and DMARC tuning, bounce processing in the Pro and Scale tiers, and monitoring dashboards. Server tiers include the hardware, bandwidth allocation, basic infrastructure support, and customer- accessible management tooling. Specific add-ons (extra IPs, managed monitoring, blacklist insurance, DKIM rotation, subdomain pool architecture) are itemised separately because they apply to some customers and not others.
We do not run discount programmes, promotional pricing, or contract-length discounts on the standard catalogue. The reasoning is operational: the cost of providing the service does not vary by customer commitment length, so neither does the price. Customers with unusual volume commitments (3+ year contracts, dedicated multi-IP pools beyond Scale, exclusive jurisdictional capacity) can negotiate custom terms during discovery; published pricing is the standard pricing for standard configurations.
Annual prepayment is available and produces a 5% discount for the prepayment commitment, which reflects the operational value to us of receiving the year's payment upfront rather than the perceived value of locking the customer in (we do not believe lock-in is real or valuable; customers stay because the service works, not because they paid in advance). Refunds on prepaid annual terms are pro-rated to actual service time used, with no additional penalty beyond the difference between the prepaid rate and the standard monthly rate.
The procurement path for standard catalogue items is deliberately short: open a conversation on Telegram or submit a ticket, share the sending profile or the specific line items required, receive a quote and an invoice with payment instructions, complete payment in the selected cryptocurrency, receive infrastructure provisioning details within 4-72 hours depending on the order type. VPS provisioning runs 4-24 hours typically. Dedicated server provisioning runs 24-72 hours depending on jurisdiction and hardware configuration. SMTP relay packages include 30-45 days of pre-warmup on assigned IPs before customer traffic begins, which means IPs are accumulating reputation while the customer completes DNS configuration and domain authentication setup.
Onboarding tasks the customer needs to complete in parallel with our pre-warmup work: DNS configuration for SPF, DKIM, DMARC, and MTA-STS records pointing to our infrastructure; domain authentication verification through DNS TXT records that we provide; suppression list import if migrating from another platform (we accept CSV uploads through encrypted channels); template adjustments to comply with bulk-sender requirements (one-click unsubscribe header, List-Unsubscribe-Post handling, RFC-compliant From and Reply-To configuration). We provide checklists for each of these and answer configuration questions through Telegram during the onboarding window without additional charge.
Customers with existing infrastructure being migrated rather than greenfield deployments follow a different path. The newsletter migration bundle and the migration line-item service both include parallel-period operation where both old and new infrastructures run simultaneously for 30 days while traffic shifts progressively. This eliminates the deliverability dip that flat cutover migrations produce on equivalent infrastructure. The newsletter-migration case study in our case-study library documents one specific 45-day migration in detail.
Yes. Tier migrations are free of charge and produce no warmup penalty because the IPs assigned at any tier are already warmed before customer traffic began. The most common upgrade path is Starter to Pro after 4-6 months when monthly volume crosses 250K; the migration completes within 24 hours and produces no deliverability impact because the underlying infrastructure remains the same. Downgrades are similarly straightforward; customers with seasonal volume swings sometimes oscillate between tiers to match actual operating volume.
We do not offer free trials because the pre-warmup work (30-45 days of building IP reputation before customer traffic begins) is structurally expensive and represents real operational cost that needs to be recovered. We offer pro-rata refunds for the unused portion of any billing period if customers decide to terminate, and we honour these consistently across all tiers and services. The refund policy in our legal documents describes the specific terms; the short version is that customers pay for service they receive and receive a refund for service they do not.
Tier limits are envelopes, not hard caps. Occasional spikes (one-time campaign blasts, seasonal peaks, product launches) are accommodated without surcharge as long as the underlying IP reputation supports the volume. Sustained operation above tier capacity for more than 2-3 weeks triggers a conversation about migrating to the appropriate tier. We do not silently throttle, charge overage fees without notice, or terminate service for crossing volume thresholds; the operational reality is that volume management requires actual coordination rather than billing automation.
For domains, yes; every customer brings their own sending domains because that is where reputation lives. We provide the SMTP infrastructure, IP addresses, and authentication handling; customers provide the domain and configure DNS. For IP addresses, generally no. The dedicated IPs included in our SMTP tiers are sourced from ranges we own or contract directly, with documented allocation history that supports deliverability. Customer-provided IPs would require us to run the warmup and reputation work on infrastructure we do not control, which produces results we cannot guarantee. Customers who own existing clean IPs typically use them for separate purposes (web hosting, application traffic) while our IPs handle the sending.
For greenfield SMTP relay deployments: 30-45 days because of the pre-warmup work on the IPs that the customer will use. The IPs are pre-warming during this period so that when customer traffic begins, the IPs have already accumulated clean reputation. For VPS or dedicated server orders without SMTP relay services, 4-72 hours depending on jurisdiction. For one-time services (audits, blacklist delisting, consultations), 24-72 hours to first deliverable. For bundles that include pre-warmed infrastructure as a structural component, the pre-warmup window applies in the same way.
Procurement for services follows the same operational patterns as our broader infrastructure offerings. Customers familiar with our hosting services find the procurement model consistent; new customers benefit from the structural overview.
Contract structure: monthly or annual subscriptions for recurring services (monitoring, managed rotation, retention, etc.), fixed-price project engagement for one-time work (audit, migration, setup, recovery), tier upgrades through standard billing changes without separate contract amendments. The structural consistency reduces customer-side administrative overhead compared to vendors with complex per-service contracts.
Payment terms: monthly billing for monthly subscriptions, annual prepayment with 10% discount for annual subscriptions, milestone billing for multi-week project engagements. All payment terms accept the cryptocurrencies documented in the payment methods page; fiat payment available for customers with specific operational requirements.
Our service portfolio evolves based on operational requirements that customer engagements surface rather than aspirational feature expansion. New services enter the portfolio when sustained customer demand justifies them; existing services occasionally evolve their scope when operational reality differs from initial expectations.
Recent additions reflect 2025-2026 industry developments: log retention compliance addresses tightened compliance frameworks, MTA-STS plus TLS-RPT managed reflects 2025 receiver-side TLS enforcement maturation, reputation insurance addresses the operational reality that incidents require coordinated response rather than ad-hoc engagement.
Service deprecations are rare but do occur. Services occasionally lose operational viability as industry conditions change; deprecated services continue serving existing customers through committed terms while not accepting new engagements. The deprecation pattern protects existing customer commitments while preventing the portfolio from accumulating services that no longer match operational requirements.
Most customers reach us with a sending profile rather than a service order. Tell us what you do (volume, audience, current setup) and we propose the configuration before you commit to anything.