martrexo as your email backbone

Fully documented API, dispatch via our own independent gateway infrastructure. Choose your own HTML or the martrexo block design.

Who is martrexo for?

Every product with an email component needs a solution to match. martrexo becomes part of the product, not just a connection alongside it.

  • SaaS providers & product teams: transactional emails and lifecycle communication from a single infrastructure

  • E-commerce & marketplace platforms: order and dispatch confirmations at high volumes

  • Agencies & system integrators: dispatch for multiple clients from a single shared connection

  • Fintech & regulated providers: high security and compliance requirements for deliverability and logging

  • App operators & webmasters: deliverability as a fixed part of your own system, without requiring your own mail infrastructure

Two routes, one infrastructure

How an email is created is entirely up to you. How it's delivered runs, in both cases, through the same proven gateway infrastructure.

Route A: Submit your own HTML

Finished emails are submitted via API and delivered through the martrexo gateways. Design, layout and content stay entirely in your hands; martrexo takes care of deliverability, logging and reputation protection.

 

  • Full creative control over the email template

  • Dispatch via our own independent gateways – no third party in the delivery path

  • Responsibility for cross-client rendering (table layouts, dark-mode display, style compatibility) stays with the submitting party

Route B: Use martrexo block designs

Instead of finished HTML, structured data is submitted. The block engine that also generates newsletters and campaigns automatically assembles it into a fully responsive email.

 

  • Submission as structured data, in common formats

  • Automatic, pixel-perfect and responsive rendering

  • The same block logic as in newsletters & campaigns, just API-driven instead of manually filled

  • No maintenance effort of your own for client-specific rendering pitfalls

One interface, two routes – usable in parallel too, depending on the use case, within the same system.

KI-Dino

Docking point
for AI agents

AI agents need tools to work with. martrexo provides these tools via its own MCP server. The platform itself becomes the interface.

  • The MCP server accepts requests from AI agents and AI tools directly, without a separate integration
  • Dispatch, status and reporting are available through it in structured form
  • Not an additional chat feature, but infrastructure that fits into existing AI workflows
  • New features become usable via the same server as soon as they're available on the platform

Operations & reliability

Dispatch runs via highly available, proprietary gateways with no third party in the delivery path. Bounce, feedback and complaint handling run automatically and feed directly into reputation management. Operations and hosting take place in Germany – EU-first as a consistent case for data sovereignty.

Consulting instead of templates

Where more than plain deliverability is needed, strategic design of email journeys is available. Triggers, lifecycle, automation. Not a catalog of templates, but design worked out together with people who understand the specific system landscape.

For developers

Integration happens via a fully documented API with clear references for each endpoint. Webhooks return status, bounce and event data directly back into your own systems. Getting started works without a major integration hurdle.

Deliverability as part of your own product, not as a side project.

Whether it's stakeholder enablement, a multi-branch system or worldwide dispatch – the best way forward is a conversation in which the specific setup becomes clear.