Question 1

How is this different from SendGrid, Mailgun, or Postmark?

Accepted Answer

Those are US-based ESPs. Their account data, logs, and DPAs run through US infrastructure, which means Schrems II and the US Cloud Act apply, regardless of which region you "select" for sending. We are a Austrian GmbH headquartered in Vienna with EU-only sub-processors. If your compliance team has flagged Schrems II as a concern, we are the answer to that flag. If you do not care about that, we are still cheaper at scale for most volume profiles above 1M emails per month.

Question 2

KumoMTA, PowerMTA, or MailerQ — which one do you recommend?

Accepted Answer

For new builds, KumoMTA. It is open-source, written in Rust, built by ex-PowerMTA engineers, and at this point feature-complete for 95% of sending workflows. PowerMTA still wins when you need specific commercial integrations or regulatory comfort with paid licensing. MailerQ fits if you are on RabbitMQ-heavy stacks. We run all three. The honest answer for most teams in 2026 is KumoMTA unless your procurement specifically requires a commercial MTA license for compliance reasons.

Question 3

Are these IPs really dedicated, or am I sharing the /24?

Accepted Answer

Dedicated means assigned to your tenant, with no other customer sending from them. Our /29, /28, and /27 blocks are fully yours for the contract period. We do not rotate IPs in and out of dedicated assignments; once you have them, they stay yours. Shared pools (when used for SMTP Relay or some cold email plans) are a separate, clearly labeled product with shared pool documentation upfront. The labeling is deliberate; ambiguous "shared but feels dedicated" pricing is the trick most providers use to charge dedicated rates for shared infrastructure.

Question 4

How fast can I be sending?

Accepted Answer

In-stock cold email plans: 30 minutes from payment confirmation. SMTP Relay: 5 minutes. Pre-warmed inboxes: 60 to 90 minutes including DNS configuration. Custom MTA configurations: 12 to 24 hours including DNS and rDNS setup. Custom dedicated server builds: 24 to 72 hours. Migration engagements: 4 to 6 weeks for the full engagement including warming. We publish provisioning ETAs on every plan card and refund prorata if we miss them.

Question 5

What is your stance on outbound marketing? Are you another shady "bulk email" host?

Accepted Answer

No. We work with legitimate B2B outbound, transactional senders, ESPs, and high-volume marketing operations. We do not work with: list-bombing, scraped consumer lists without consent, financial scams, phishing infrastructure, anyone whose volume comes from purchased "leads" from data brokers, or B2C cold email regardless of jurisdiction. Our AUP is short, we enforce it, and applications that look like they will violate it get rejected during signup screening. We would rather lose the deal than lose the netblock.

Question 6

How does the Panama datacenter fit with the EU sovereign positioning?

Accepted Answer

The Panama site is for our /offshore-hosting product specifically, which is a separate product line for customers who need Panama jurisdiction (typically for predictable due-process workflows outside US and EU). The rest of the operation is EU-jurisdiction: Vienna HQ, EU sub-processors, EU IP allocations. Customers using our EU sovereign products never touch the Panama infrastructure. Customers using offshore hosting know they are choosing the Panama option and the documentation is explicit about jurisdiction.

Question 7

Do you sign DPAs and BAAs?

Accepted Answer

DPAs yes, signed during onboarding for any customer in scope of GDPR (which is most customers in our segment). BAAs yes, for healthcare-adjacent customers running PHI through their email infrastructure (rare but happens, requires custom contractual structure). Custom contracts negotiated for regulated industries with specific procurement requirements (financial services audit trails, public sector compliance, defense industry restrictions). The custom contracts add 1 to 4 weeks to onboarding depending on complexity but they are real, signed, and enforceable.

Question 8

What if we already use SendGrid and we are fine? Why would we move?

Accepted Answer

You probably should not move if it is working. Migration is operationally costly, takes 4 to 6 weeks of focused work, and the outcome at best is parity with what you had. The reasons customers move to us are usually one of three: Schrems II compliance flagged by procurement (we solve that, but only if your team has flagged it), pricing pressure at high volume (we are cheaper above 1M monthly emails for most profiles), or specific operational requirements that mass-market ESPs cannot accommodate (custom MTA configurations, multi-IP block warming, regulated industry compliance). If none of those apply, staying on SendGrid is the right answer and we will tell you that during the discovery call.

Question 9

How does pricing work? Is everything monthly subscription?

Accepted Answer

Mixed. Sending products (Email API EU, SMTP Relay, Email Sending Servers, Cold Email Infrastructure, Pre-warmed Inboxes), DNS and domain products, and recurring services (Managed DMARC, Deliverability Monitoring) bill monthly with optional annual prepay at 15% discount. One-time services (Deliverability Audit, IP Warming, Reputation Recovery, Migration Service) bill at engagement signing with documented warranty terms. Hardware (Dedicated Servers, Offshore Hosting) bills monthly with optional setup fees on custom configurations. Custom enterprise contracts get negotiated upfront with explicit SLAs and service credits.

Question 10

What happens if we want to migrate off your infrastructure later?

Accepted Answer

We help you migrate. The /migration-service product runs in either direction; we have helped several customers migrate explicitly off our infrastructure to other ESPs or self-hosted setups, for reasons unrelated to satisfaction (cost optimization, regulatory consolidation, internal mandates). The migration runs the same way as inbound migrations: documented architecture, clean cutover, full warming on the destination, 30-day warranty on the new infrastructure. Your data exports cleanly, your domains transfer cleanly, and we do not run retention games. Customer references for outbound migrations are available on request during sales conversations.

Question 11

Do you offer pilots or trials?

Accepted Answer

Limited. SMTP Relay starting tier is cheap enough (€19/mo) that committing to a month is functionally a paid trial. Pre-warmed Inboxes Pack 10 has a 14-day quality guarantee. Most other products do not have formal trials because the products require setup work that does not amortize over a short trial period; we discuss the technical fit during the discovery call instead. For Enterprise tier customers, we offer paid pilots scoped as a 30-day engagement with explicit success criteria.

Question 12

How do you handle customer support compared to large ESPs?

Accepted Answer

Email and chat support during business hours (Vienna time, with extended coverage from US-time engineers for North American customers). Average first-response time on tickets in 2025 was 18 minutes during business hours and under 90 minutes outside business hours. PagerDuty integration on Pro and Enterprise tiers for genuine emergencies. Slack Connect direct line for Enterprise customers. The trade-off versus large ESPs: we are smaller, our response times are faster on technical issues, but we do not have 24/7 phone support staffed by hundreds of agents. For genuine 24/7 incident support, Enterprise tier is the right fit.

Question 13

What is your stance on AI-generated content sent through your infrastructure?

Accepted Answer

We do not police content (that is your responsibility under our AUP), but we do enforce against patterns that AI-generated content tends to exhibit: high-volume, low-engagement sending without proper warming; templates with high spam-score patterns; lists generated through automated scraping rather than legitimate opt-in. Customers using AI-generated content responsibly (transactional notifications written by LLMs, marketing copy assisted by AI tools, customer support responses) have no issue. Customers using AI to generate volume that would not exist with human review get caught quickly because the engagement metrics give them away.

Question 14

Can we visit the Vienna office or the datacenters?

Accepted Answer

The Vienna office hosts customer visits by appointment, typically as part of Enterprise procurement processes that require physical site verification. Datacenter visits are coordinated case-by-case; the EU PoPs are colocation facilities operated by partners (Equinix, Interxion, our own racks) and access is governed by the partner facilities. The Panama datacenter we operate directly and customer visits can be arranged with notice. For most customers, the operational artifacts (signed DPAs, audit reports, SOC 2 documentation where applicable) are sufficient and physical visits are not necessary.

Question 15

How do we get started? What is the first call like?

Accepted Answer

The first call is a 30 to 45 minute discovery conversation covering your current sending profile, what you are trying to solve, what your timeline looks like, and what your constraints are. The output is either a clear product recommendation with pricing, or an honest "this is not a fit, here is who you should talk to instead" if your needs are not in our wheelhouse. About 25 percent of discovery calls conclude with us recommending a different vendor; the rest move to a contract within 1 to 4 weeks depending on engagement size and procurement complexity.

Question 16

Are you ISO 27001, SOC 2, or PCI-DSS certified?

Accepted Answer

ISO 27001: yes, certified since 2019, audited annually. SOC 2 Type II: yes, attestation reports available under NDA for procurement reviews. PCI-DSS: not directly (we do not process payment card data on the customer-facing infrastructure; our own card processing is handled by a payment service provider that is PCI-DSS compliant). For customers requiring specific certifications we do not currently hold, we can scope custom contracts that match the underlying control requirements without the formal certification, which works for most procurement processes that can accept compensating controls. Healthcare and defense industry customers often need this approach.

Question 17

What languages does customer support work in?

Accepted Answer

English, Spanish, and German for live support. Most documentation is in English (with the website translated to Spanish and Brazilian Portuguese for the customer-facing pages). Engineering work and technical reports happen in English regardless of customer location because the technical vocabulary translates poorly and the receiver-side documentation we coordinate with (Spamhaus, Microsoft, Google) is English-first. For customers in markets where English is not the working language for technical staff, we coordinate with their team in whatever language works for them and produce final reports in English plus a translated summary if needed.

Question 18

How do you handle situations where a customer wants something we cannot do?

Accepted Answer

Directly. If a customer asks for something outside our capabilities (specific certifications we do not hold, infrastructure regions we do not operate in, regulatory frameworks we are not familiar with, product categories we do not serve), we say so on the first call and recommend who they should talk to instead. About 25 percent of discovery calls conclude with that outcome. The discipline of being honest about limitations is part of the relationship; we have lost deals and gained referrals from prospects we sent to other vendors, and the long-term economics of that approach are better than trying to be everything to everyone.

	OS Domains Operated	AWS SES Cloud-managed	SendGrid Twilio	Mailgun Sinch
Dedicated IPs in EU	100K+ pool	Per-region	Limited	Limited
Schrems II compliance	✓ Native	Requires SCC	Requires SCC	Requires SCC
Named engineer per project	✓ Always	Support ticket	Pool/enterprise	Pool/enterprise
Placement SLA contractual	✓ Available	—	—	Enterprise tier
Managed DMARC + BIMI	✓ Included	DIY	Add-on	Add-on
DORA exit plan in DPA	✓ Yes	On request	—	—
Own ASN	AS56396	—	—	—
Years operating	18 yr	15 yr	16 yr	15 yr

#	Location	Country	Tier	Role	Peering exchange	Avg latency	Status
01	London	United Kingdom	Tier 4	Peering hub	LINX	17ms p99	Operational
02	Amsterdam	Netherlands	Tier 3+	Throughput	AMS-IX	19ms p99	Operational
03	Frankfurt	Germany	Tier 4	EU central	DE-CIX	18ms p99	Operational
04	Strasbourg	France	Tier 3+	Schrems-safe	France-IX	21ms p99	Operational
05	Vienna★	Austria	Tier 3+	HQ + PoP	VIX	16ms p99	Operational
06	Dallas	United States	Tier 3+	NA gateway	Equinix DA	112ms p99	Operational
07	Panama	Panama	Tier 3+	LATAM hardware	NAP del Caribe	148ms p99	Operational

Infrastructure

Outbound stack

Deliverability

Professional services

By use case

By industry

By regulation

The EU sovereign stack senders trust to land

Fourteen services across four categories.

Infrastructure

Outbound stack

Deliverability

Professional services

Why operators move from SES, SendGrid and Mailgun.

7 points of presence,
5 jurisdictions.

Built for senders
with measurable outcomes.

Transactional email

Marketing at scale

Cold outbound B2B

High-volume notifications

Banking & fintech

SaaS B2B

Latest from the journal.

PowerMTA vs KumoMTA en 2026: la comparación técnica profunda

DMARC enforcement post-Schrems II y bulk sender mandate

DMARC + BIMI: la guía completa 2026

Cold email B2B en 2026: lo que cambió

Ready to talk specifics?

The EU sovereign stack senders trust to land

Fourteen services across four categories.

Infrastructure

Outbound stack

Deliverability

Professional services

Why operators move from SES, SendGrid and Mailgun.

7 points of presence,5 jurisdictions.

Built for senderswith measurable outcomes.

Transactional email

Marketing at scale

Cold outbound B2B

High-volume notifications

Banking & fintech

SaaS B2B

Latest from the journal.

PowerMTA vs KumoMTA en 2026: la comparación técnica profunda

DMARC enforcement post-Schrems II y bulk sender mandate

DMARC + BIMI: la guía completa 2026

Cold email B2B en 2026: lo que cambió

Ready to talk specifics?

7 points of presence,
5 jurisdictions.

Built for senders
with measurable outcomes.