--- title: "Lettermint turns 1 and we're just getting started" description: "2025 was our first year. A look back at what we achieved and a glimpse of what 2026 will bring." url: "https://lettermint.co/blog/lettermint-turns-1-and-we-are-just-getting-started" published: "2026-01-02" last_updated: "2026-01-02" --- # Lettermint turns 1 and we're just getting started > 2025 was our first year. A look back at what we achieved and a glimpse of what 2026 will bring. At the end of 2024, we *(Bjarn & Bjorn)* signed the founding documents of Lettermint with **January 1st 2025** as our official start date. Now, a year later, we want to look back at this wild ride. What did we achieve, what did we learn and what's on the roadmap for 2026? ## From idea to reality In our [first blog post](https://lettermint.co/blog/welcome-future-transactional-mailing-europe) we explained why we started Lettermint. In short: we wanted to build an alternative without relying on parties outside Europe. [Transactional email](https://lettermint.co/features/transactional-emails) for developers. Privacy-first, reliable and fully hosted in the EU. With the founding documents signed, we could start building our infrastructure. We registered our own **ASN**, got our own **IP ranges** assigned and started building a platform that runs entirely in Europe. It took weeks before we could send our first email through our own infrastructure with our own IPs. From server configuration to setting up the right DNS records, everything had to be built from scratch. At the end of February, the moment finally came and we saw that **first email** land successfully. After that, we could start warming up our IPs. ![First Lettermint email](https://lettermint.co/content/blog/first-email.webp) From that point on, we could split the work. Bjarn focused on the infrastructure and warming up the IPs, while Bjorn worked on branding and the website. The goal: be ready for our **beta launch at the end of May**. ## Our first customer And then that *magical* moment: our **first real customer**. Anyone who has ever built a [SaaS](https://lettermint.co/for/saas) (*Software as a Service*) knows that feeling. Not a test account, not a friend, but someone who discovers your product and decides to use it. Someone who believes in what you're building and consciously chooses a [European alternative for transactional emails](https://lettermint.co/features/transactional-emails). Because developer experience is at our core, we built our [integrations](https://lettermint.co/integrations) based on feedback from our users. How do they send emails? What software do they use? We started with **SMTP Relay** and added **PHP** and **Laravel** as our first SDKs. ## From sending to receiving ### Broadcast In August we launched [Broadcast emails](https://lettermint.co/features/broadcast-emails). Next to transactional emails you could now also send newsletters and marketing campaigns through Lettermint. We use separate IPs to keep transactional and marketing emails apart. Marketing emails are more often marked as spam or ignored, which affects your sending reputation. By separating them, password resets and order confirmations end up where they belong: the inbox. ### Time to Inbox Around the same time we launched our [Time to Inbox](https://lettermint.co/time-to-inbox-tti) page. Here you can see in real time how fast emails sent through Lettermint arrive in the inbox. Full transparency about our infrastructure. Live Time to Inbox measurements: [https://lettermint.co/time-to-inbox-tti](https://lettermint.co/time-to-inbox-tti) ### Inbound A few months later we launched [Inbound emails](https://lettermint.co/features/inbound-emails). Not just sending, but also receiving. We noticed that many users wanted to receive and process emails too. Incoming emails are automatically processed and sent to your application as a webhook. Great for support tickets, contact forms or automated workflows where you want to act on incoming messages. ## Behind the scenes Growth also means scaling. We had some bumps that our customers unfortunately noticed. Emails that were delayed, moments where it should have been better. Not our favourite chapter of the year, but definitely a learning experience. We decided to migrate to a multi-AZ infrastructure. This required careful preparation to keep downtime during the migration as short as possible. It turned into a few long nights. Shoutout to Red Bull. In the end we successfully made the switch. The result is a platform ready for the future and **through which we now send millions of emails per month**. > Setting up was a breeze, deliverability top notch and support simply > outstanding. Time to switch! ## The highlights Besides the major features, we made great progress in our first year. All documented on our [changelog](https://lettermint.co/changelog). Here's an overview of our highlights: - We sent our first email - We launched our website and dashboard - We developed SDKs for popular frameworks - We developed plugins to use Lettermint without technical knowledge, for example in WordPress - We developed no-code integrations for Zapier and Make - We sent our millionth email *(we celebrated that one)* - We launched Broadcast - We launched Webhooks - We launched Inbound - We launched a Team API - We launched Spam Insights - We started partnerships with organisations and charities - We wrote 20+ knowledge base articles about the world of email - We hit one million emails in a single month - We migrated to a multi-AZ infrastructure - We saw [governments, municipalities](https://lettermint.co/for/public-sector) and [healthcare institutions](https://lettermint.co/for/healthcare) become customers - Lettermint V.O.F became Lettermint B.V. ## Looking ahead to 2026 We started 2026 with an important step. The transition to **Lettermint B.V.** A structure that fits the growth we're seeing and the plans we have for this year. One of those plans is obtaining our ISO 27001 certification. We've taken security and privacy seriously from day one. A certification is the official proof. More about our current approach can be found on our [Trust Center](https://trust.lettermint.co/). We're also planning a renewed dashboard. We want it to better reflect everything you can do with Lettermint. This will make it possible to build marketing campaigns in Lettermint, without code. 2025 was the year of the foundation. We built the infrastructure, launched the platform and welcomed our first customers. 2026 will be the year we expand the platform and show Europe what we've got. Thanks to everyone who chose Lettermint this past year. Customers, partners and supporters. We're excited for what's next. Bjarn & Bjorn – Founders of Lettermint