Mail, contacts and calendars that keep working
The ecosystem keeps moving, we keep you working. The code is free and stays free. What we sell is what does not come with it: your servers, apps and integrations tested on every change, your bugs first, maintained for you year after year.
- For mail providersYou host mail, contacts or calendars for your users. Your servers in our test suite, your users set up with one address, in apps under your name.
- For products that handle mailYour CRM, helpdesk, ERP or internal tool reads or sends your customers’ mail. Off Exchange Web Services and basic auth before Microsoft’s deadlines, then kept working.
- 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.
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.
- An app nobody maintains dies. Store rules, platform updates and protocol changes come back every year, long after the launch.
On someone else's schedule
What Microsoft already changed, and what comes next.
- Since October 2022Basic auth is gone from IMAP, POP and Exchange ActiveSync.
- 1 October 2026Exchange Web Services blocked by default; admins can still turn it back on.
- End of December 2026Basic auth for SMTP AUTH turned off by default on Microsoft 365.
- 1 April 2027Exchange Web Services shut down for good.
The quirks are already found
Since 2022, 30+ libraries written from the RFCs up (IMAP, SMTP, JMAP, CardDAV, CalDAV, OAuth, discovery) and tested against the providers people use, on accounts kept for testing alone. A partnership puts yours first, for less than the weeks an engineer would spend on them each year.
Pimalaya ships no AI. Its tools are made to be driven by other software, agents included: JSON output with its schemas, and documentation written for integrators.
30+libraries, since 2022
Three ways to partner
For mail providers
You host mail, contacts or calendars for your users.
Your users piece together a mail app, a contacts sync and a calendar to reach you, and each one breaks in its own way, 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 our setup wizards and the discovery rules.
- Apps under your name: mail, contacts and calendars in one, published on the stores for your users.
- Kept up to date, through store rules, platform updates and changes on your servers, every year.
- A tested provider listing here and in the documentation.
Get in touchFrom€6,000per year
Plus a setup from €10,000.
Android today, other platforms as they ship. Large providers: on quote.
For products that handle mail
Your CRM, helpdesk, ERP or internal tool reads or sends your customers’ mail.
Microsoft is switching off the way your product reaches your customers’ mailboxes, and every other provider changes its rules on its own schedule.
- Off EWS and basic auth: your mail connection moved to OAuth over IMAP and SMTP, on the Pimalaya libraries.
- Your customers’ providers in our CI, Microsoft 365 and Gmail first, tested on every change.
- On your servers: no per-account fee, no third party between you and your customers’ mail.
- Kept working, as Microsoft, Google and the others change their rules, every year.
- Your OAuth verification, prepared with you: what Google and Microsoft ask for, gathered together; the app and its audit stay yours.
Get in touchFrom€4,000per year
Plus a setup from €8,000.
Mail over IMAP and SMTP; Microsoft Graph is not covered yet.
For 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.
- Your bugs first, ahead of the general queue, from a bank of days agreed each year.
- A supported version line, as a higher tier: backported fixes until an agreed date.
- Audit-ready: a bill of materials and the security policy of every supported release, for your own OAuth audits and the Cyber Resilience Act.
- A partner badge in the community list.
Get in touchFrom€5,000per year
With a supported version line: from €12,000 per year.
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.
Our partners
Builds with us an AI-powered desktop client for mail, contacts and calendars, on the Pimalaya stack.
Tell us what you run and what breaks: pimalaya.org@posteo.net.