Email, contacts and calendars
that keep working
The code is free and stays free. What we sell is what does not come with it: your service or integration tested on every change, your bugs first, a version line maintained for you.
- For email providersYou host mail, contacts or calendars for your users. Your servers in our test suite, your users set up with one address.
- For integratorsYou ship a product built on the Himalaya CLI or the Rust libraries. Your workflows in our test suite, a version line that does not move under you.
- For users plannedYou use the Pimalaya tools with Gmail or Microsoft 365. Sign in with one click, without registering your own app.
Why pay for free software
Writing a mail client got cheap. Keeping one working against real servers did not, and the bill comes back every year.
- Every server has quirks. Each one is a support ticket before it is a bug report.
- OAuth is a compliance project. Gmail needs a verified app and a yearly security audit; Microsoft 365 a verified publisher.
- The protocols keep moving. Basic auth is gone, Exchange Web Services is retiring: code breaks on someone else’s schedule.
- Already in effectBasic auth is gone from hosted IMAP and SMTP.
- 1 October 2026Exchange Web Services retirement begins, through April 2027.
- End of December 2026SMTP AUTH goes default-off on Microsoft 365.
The quirks are already found
Since 2022, 30+ libraries written from the RFCs up (IMAP, SMTP, JMAP, CardDAV, CalDAV, OAuth) and tested against the providers people use. A partnership puts yours first, for less than the weeks an engineer would spend on them each year.
Two ways to partner
For email providers
You host mail, contacts or calendars for your users.
When a client mishandles your server, the report lands in your support queue.
- Your servers in our CI, whatever you run: IMAP, SMTP, JMAP, CardDAV, CalDAV.
- Your quirks first, fixed and documented publicly.
- Setup with one address: a first-class preset in the Himalaya wizard and the discovery rules.
- A tested provider listing here and in the documentation.
From €3,000 per year. Large providers: on quote.
Get in touchFor integrators
You ship a product built on the Himalaya CLI or the Rust libraries.
Your risk is an upgrade that breaks you, or a provider bug your customers hit first.
- Your workflows in our CI: a release that breaks your commands, JSON output or library calls does not ship.
- A supported version line, with backported fixes until an agreed date.
- Your bugs first, ahead of the general queue.
- OAuth verification, done once: your own Google and Microsoft apps set up, verified and audit-ready.
- A partner badge in the community list.
From €5,000 per year.
Get in touch
What a partnership does not buy
- Ranking or exclusivity. Everyone is listed, tested and fixed, paying or not.
- Features. Nothing is locked: the code is MIT or Apache-2.0 for everyone.
- Endorsement. We vouch for the integration point, never for your product.
- 24/7 support. Pimalaya is a small team; response targets are agreed per contract, in days.
Be the first
None yet: the first partners shape the programme. Listing in the community catalogue stays free for anyone.
Tell us what you run and what breaks: pimalaya.org@posteo.net.