We are pleased to announce the release of EPIM Mail and EPIM Pro 26.0.6.
This update fixes an issue that prevented translations from working correctly in Mail and resolves a problem that could require administrative privileges when installing or updating EPIM as a non-administrative Windows user. The release also includes additional technical improvements behind the scenes.
We recommend that all EPIM users update to this version to benefit from these fixes and improvements.
As usual, the update is available through EPIM's automatic update feature or can be downloaded from the Download Free page.
Reviews & Comments
However, as someone who follows the software industry closely, I would like to shared some friendly, high-level feedback regarding EPIM’s transition to a subscription model and its long-term future in the current AI and privacy-focused era.
Currently, the feedback on the forums and the ongoing issues with EPIM Cloud synchronization point to a deeper structural challenge. Forcing a traditional, closed-source client into a strict subscription model can be perceived as an "upgrade tax" rather than value creation, especially when competing against tech giants and modern agile platforms.
To survive the fierce AI disruption over the next 1–2 years, I highly recommend that EPIM considers transitioning into an Open-Core / Developer-Plugin Model (similar to successful pioneers like Obsidian or Joplin):
Modernize the Core Architecture: Consider migrating the underlying database from the legacy Firebird system to SQLite. This would dramatically reduce the technical debt, stop multi-device synchronization conflicts, and make the application lightweight and future-proof.
Empower the Community via an Open Plugin Marketplace: Don't bear the massive cost of developing AI or workflow automation features alone. By opening up your API and source code for the local engine, global developers can build AI assistants, Markdown integrators, and custom modules for free.
A Win-Win Subscription Model (B2C & B2B): Keep the local application and basic self-hosted syncing (WebDAV/Wi-Fi/File) free or buy-out. Instead, monetize through a robust, hassle-free Official Cloud/AI Sync subscription for non-technical users, and premium enterprise licenses for corporate clients.
This pivot would instantly transform EPIM from an aging client under fire into a privacy-first, community-driven "Personal AI Data Brain." It satisfies investors with a highly scalable SaaS model, while turning disgruntled legacy users into enthusiastic brand evangelists.
I love this product and truly want to see EPIM thrive for another 20 years. I hope you will take this strategic advice into consideration during your internal roadmap alignment.
Best regards,
A Proud EssentialPIM Lifetime User
Regarding EPIM Cloud, we'd actually be very interested in learning more about the synchronization issues you mentioned. We're not aware of any widespread problems at the moment, nor do we see corresponding reports on the forum.
As for SQLite, the idea is certainly not without merit. However, one of the major challenges is that SQLite does not support multi-user access scenarios, which makes such a transition significantly more complex than it may appear at first glance.
With respect to your broader strategic ideas like open-core, APIs, plugins, AI integrations and similar topics, we find them genuinely interesting. If you'd be willing to discuss them further, we'd be happy to continue the conversation in more detail. If you're interested, please feel free to contact our support team and reference this comment. We'd be glad to continue the discussion there and explore your ideas further. Who knows, there may even be opportunities to involve knowledgeable and passionate users such as yourself more directly in shaping the future of EPIM.
Thank you again for your continued support, thoughtful feedback and your commitment to EPIM. It is very much appreciated!
I would like to address your technical concern regarding SQLite and its perceived limitations in "multi-user access scenarios." With all due respect, I believe there might be a subtle but critical confusion between "Server-side Database Multi-User Concurrency" and "Client-side Multi-Device Synchronization."
Allow me to share how modern privacy-first efficiency tools (PIMs) like Joplin and Obsidian have successfully cracked this nut using SQLite and standard formats, achieving massive scalability while maintaining zero technical debt:
1. Redefining the Architecture: The Joplin Model
Joplin uses SQLite as its local, client-side relational database engine on Windows, macOS, Android, and iOS.
The Myth of Multi-User Limitation: SQLite is indeed a file-based database, meaning it doesn't handle multiple users writing to the exact same file simultaneously over a network file system.
The Modern Solution: Joplin does not expose the raw SQLite file to the network. Instead, every device has its own local SQLite database. When a user syncs, the client serializes changed items into lightweight, encrypted metadata files and pushes them to the cloud (WebDAV, Nextcloud, or Joplin Cloud). The server handles conflict resolution using atomic operations, and other clients pull these changes to update their own local SQLite instances.
Why this fits EPIM: Since over 95% of EPIM’s core users manage personal data across their own private devices (PC, phone, tablet), the Joplin architecture offers instantaneous local performance, complete privacy, and effortless multi-device sync without ever needing a heavy server-side RDBMS engine like Firebird.
2. The Plugin-Driven Extension: The Obsidian Model
Obsidian takes this a step further by using pure Markdown on the disk but leveraging an in-memory database index (internally structured similarly to highly optimized key-value stores) for instant searching and graphs.
When they introduced Obsidian Sync, they didn't implement a heavy, legacy network-locking database. They built a lightweight, end-to-end encrypted delta-sync engine.
By decoupling the Data Storage Layer (Local Markdown/SQLite) from the Sync/Collaboration Layer (The Cloud Engine), they allowed global open-source developers to build hundreds of AI plugins locally, while their official cloud subscription focuses purely on the synchronization service and server-side relay.
3. Resolving the Hidden Sync Friction in EPIM Cloud
You mentioned that you haven't seen widespread sync reports on the forums. The reality is that many advanced power users—especially on the Android client, which has experienced prolonged update gaps—suffer from "silent data friction."Because Firebird relies heavily on older transaction-locking paradigms, when an aging Android app attempts to sync complex, multi-layered data with a modern Windows client over EPIM Cloud, the system often defaults to heavy-handed conflict resolution, resulting in duplicated calendar entries or missing note categories. Many users simply stop using the cloud sync or quietly migrate to other tools instead of posting detailed logs on the forum.
Moving Forward: A Hybrid Path for EPIM
If EPIM still wants to serve the niche enterprise B market that requires true, real-time multi-user network sharing (e.g., multiple secretaries editing one boss's schedule simultaneously), you do not have to compromise your 95% personal user base.
You can adopt a Hybrid Dual-Engine Strategy:
EPIM Personal: Migrate to a clean, open-core SQLite + API Plugin architecture. Let local performance fly and make AI integration plug-and-play.
EPIM Business Server: Keep a network-capable server backend, but modernize it via PostgreSQL or a Dockerized microservice, rather than forcing personal users to carry the heavy architectural baggage of Firebird.
As a power user deeply embedded in the ecosystem, I want to bring a massive blind spot to your attention. The severe stagnation and update gaps of the EPIM Android client have triggered what industry product managers call a "Silent Sync Disaster." Advanced users are experiencing this daily, but they aren't reporting it on the forum anymore—they are simply migrating away.
Allow me to tear open this blind spot with three highly specific, real-world user scenarios that highlight how legacy architectural friction is killing EPIM Cloud:
Scenario 1: The "Version-Gap Overwrite" Nightmare (Data Loss)
The Setup: A user runs the latest, heavily updated 2026 version of EPIM Windows on their PC, utilizing advanced hierarchical note tags or complex recurrent calendar exceptions. Meanwhile, their Android phone runs the stagnated, un-updated version of EPIM.
The Disaster: The user edits a crucial note on their PC. Later, they make a quick text tweak to a completely different section of that note on their phone. When EPIM Cloud triggers a sync, the older Android database structural logic fails to interpret the advanced Windows metadata layout. Instead of a smart merge, the sync engine panics, flags a conflict, and either duplicates the entire note (cluttering the database) or silently overwrites the advanced PC changes with the simpler Android file structure.
The Result: The user opens their PC later to find hours of work distorted or wiped out.
Scenario 2: The Android OS "Deep Sleep" & Category Disappearance
The Setup: Modern operating systems like Android 14, 15, and 16 enforce strict battery optimization and background activity restrictions. Old apps that haven't been aggressively refactored to comply with modern Android background execution APIs are routinely "frozen" by the system.
The Disaster: Because the Android app hasn't been updated to leverage modern native push or modern background sync worker protocols, Wi-Fi or Cloud sync fails to trigger automatically in the background. When the user manually opens the app to force a sync, the massive backlog of accumulated delta changes forces a heavy transaction lock via the Firebird architecture. This causes the mobile app to freeze, crash mid-sync, or drop localized item categories/colors.
The Result: The user's phone calendar is rendered unreliable when they are out on business, causing missed appointments.
Scenario 3: Why This Is a "Silent Churn" Blind Spot for Your Team
You might wonder: "If this is happening, why is our forum quiet?"
The Psychology of Privacy-First Users: EPIM’s core user base consists of busy professionals—lawyers, doctors, engineers, and executives—who choose you because they want a reliable, quiet digital vault.
The Tragic Reality: When a user experiences data duplication or sync freezing for the third time due to the Android version gap, they don't have the time to extract database logs, register on a forum, and argue with developers. They assume the software is dying because the mobile app looks abandoned. They quietly export their data into universal formats (like .ics or .vcf) and switch to modern alternatives like Joplin, Obsidian, or Proton Calendar. Your database shows them as inactive, but your forum shows no complaints. This is silent hemorrhaging.
The Strategic Remedy
To expect users to pay a premium subscription fee for EPIM Cloud while the Android app remains an outdated bridge is a contradiction in value.
If EPIM adopts the Open-Core model I proposed earlier:
You could open up the local storage schema and basic syncing protocol.
The global community could build modern, native Android syncing wrappers or bridge tools for you, instantly relieving your small development team of the massive burden of chasing Google Play’s rapidly changing API requirements.
However, forcing your 95% C-end personal user base to carry the legacy architectural baggage of Firebird just to serve a small 5% B-end enterprise niche is a strategic bottleneck. It introduces high technical debt, causes the multi-device sync friction we see in EPIM Cloud, and completely locks out the global open-source AI developer ecosystem.
To bridge this gap, you don't have to choose one over the other. As a passionate user who wants to see EPIM thrive for another 20 years, I have sketched out a 3-Phase Progressive Roadmap that allows you to capture high-margin B2B revenue while turning EPIM Personal into a modern, community-driven AI powerhouse:
Phase 1: Decoupling the Core & The "Dual-Engine" Architecture (Short-term)
Instead of forcing one database onto all user segments, split EPIM's underlying storage layer from its user interface.
EPIM Personal (C-end): Refactor the local client to use a clean, blazingly fast SQLite or decoupled flat-file core. This completely optimizes individual multi-device syncing (PC to Android/iOS) via EPIM Cloud, eliminating delta-sync conflicts.
EPIM Business/Server (B-end): Keep your collaborative network layer, but modernize it by offering a PostgreSQL or Dockerized microservice backend for enterprise environments requiring true multi-user concurrency, replacing the aging Firebird server.
Phase 2: Opening the API & Launching the Plugin Marketplace (Mid-term)
Once the personal core is modernized, open up EPIM’s local API and launch an official EPIM Plugin Store.
Zero-Cost R&D: Do not attempt to build every feature yourself. Let global open-source developers build the bridges. Within months, the community will build custom Markdown importers, Kanban boards, and modern Android syncing wrappers for you, completely solving the current Android update stagnation.
The B2B & C2C Monetization Wave:
Keep the local application and basic self-hosted syncing (WebDAV) open/buy-out to maintain absolute trust with privacy purists.
Monetize by taking a 15%–30% revenue split from premium third-party plugins in your marketplace, mirroring the highly profitable models of Obsidian or WordPress.
Phase 3: The "Privacy-First" Personal AI Assistant Integration (Long-term)
In 2026, a PIM software is no longer just an organizer; it is the context provider for AI. By having a lightweight local architecture (Phase 1) and an open API (Phase 2), EPIM becomes perfectly positioned for the AI era.
Encourage the community to develop plugins that connect EPIM's local data (emails, calendar, notes) with local LLMs (via Ollama/Llama 3) or secure cloud APIs (OpenAI/Claude).
The Ultimate Subscription Value: Introduce EPIM AI Cloud, a premium subscription tier where your official servers handle advanced server-side RAG (Retrieval-Augmented Generation), secure cross-device AI scheduling, and smart email drafts. Users will happily pay a subscription for a living AI assistant, whereas they will resist paying a subscription just to sync basic calendar entries.
This roadmap satisfies your new investors by creating an incredibly lucrative, modern SaaS pipeline (Premium Cloud + AI + Marketplace Cut), while honoring and expanding the trust of your most loyal lifetime users.
Thank you again for your incredible responsiveness and commitment to listening to your power-user community.
Warmest regards,
A Proud EssentialPIM Lifetime User
That said, the discussion has now moved into a very specific technical and strategic territory and is becoming somewhat off-topic for the news post under which these comments are being made. For that reason, while we won't remove any of the existing comments, we believe the conversation would be better suited to a different communication channel.
If you'd like to continue the discussion, please feel free to contact our support team and reference this conversation. We'll be happy to provide comments where appropriate. We would also like to note, however, that without full visibility into our internal processes, historical decisions, technical constraints, business requirements and practical experience gained over many years of developing and supporting EPIM, some of the proposed approaches appear more straightforward or universally applicable than they are in practice. This doesn't diminish the value of the ideas themselves, but it does mean that the analysis inevitably lacks some context available only internally.
In any case, thank you again for the time, effort and thoughts you've put into this discussion. We appreciate your passion for the product and your desire to see EPIM continue to evolve and succeed in the years ahead :)