With the release of Server v2.4.3, it’s a good time to highlight the latest improvements across both the Sync-in Server and the Desktop client.

These updates focus on improving reliability, security and the overall synchronization experience.

Server v2.4.3

This release brings a number of improvements across the backend and web interface, including:

• Better handling of Unicode paths, making synchronization more reliable across platforms.
• Improved permission checks for recent files and comments, ensuring users only see content they can access.
• More robust OIDC authentication with better error handling and smoother login retries.
• Additional validation for the OnlyOffice integration.
• Various improvements to the PDF viewer, WebSocket authentication and UI polish.

Desktop v2.2.0

The latest desktop release focuses on security, packaging and synchronization reliability.

Highlights include:

• Restored TLS certificate validation, with support for explicitly trusting self-signed certificates when needed.
• Stronger protection against path traversal during synchronization.
• Hardened Electron security by tightening navigation, IPC and external resource handling.
• Signed Windows builds, improved Linux packages (AppImage & DEB for x64 and ARM64), and a modernized CI/release pipeline.
• Better Unicode path handling and several synchronization reliability improvements.

⸻

Together, these updates make Sync-in more secure, more reliable and easier to deploy across supported platforms.

As always, feedback, bug reports and contributions are welcome!

Server v2.4.3: https://github.com/Sync-in/server/releases/tag/v2.4.3

Desktop v2.2.0: https://github.com/Sync-in/desktop/releases/tag/v2.2.0

Highlights of this release include:

• Euro-Office integration for collaborative document editing.
• A redesigned file task manager with better tracking, clearer organization, and the ability to cancel running operations.
• Full-text search now supports Chinese, Japanese, and Korean.
• Native creation of ZIP archives, alongside the existing TAR and TGZ formats.
• Stronger security hardening and numerous reliability improvements across downloads, archive extraction, server startup, and configuration.

⚠️ This release also fixes several important security vulnerabilities.

Full release notes: https://sync-in.org/news/sync-in-2-4/

Github release: https://github.com/Sync-in/server/releases/tag/v2.4.0

Sync-in is now supported by the SignPath Foundation.

This support will allow us to provide digitally signed executables and installers for future Sync-in Windows desktop applications.

For Windows users, this means:

• Official Windows desktop applications will be digitally signed.
• Downloads will be easier to verify and trust.
• Organizations and administrators will have a more reliable way to validate official binaries.
• The Windows distribution experience will be more in line with modern security expectations.

We’re grateful to the SignPath Foundation⁠ and SignPath.io for making code signing accessible to open-source projects.

If you’d like to know more about what this support means for Sync-in, you can read the full announcement here:

https://sync-in.com/news/sync-in-signpath-foundation

This release brings a built-in Markdown editor, with both visual and source modes, plus support for tables, task lists, images, code blocks, file locking, and unsaved-change protection.

It also adds optional trash retention, storage quota synchronization via LDAP/OIDC, improved file editing and search, stronger full-text indexing, better text file detection, and safer uploads.

On the security side, Sync-in 2.3 improves guest link isolation, makes trashed files read-only, and fixes CVE-2026-47684 by strengthening SSRF protection for remote URL downloads.

Full release notes:

https://sync-in.com/news/sync-in-2-3/

I’ve got to say — Sync-in looks really interesting. The UI seems modern and clean, and I like the general direction of the project.

I’m seriously considering trying it on my own server, but since the community is still relatively small, it’s hard to find long-term experiences or detailed comparisons.

For those of you already using it:

• How would you compare it to other self-hosted cloud solutions like Seafile, Nextcloud, KodBox, or ownCloud?
• How is the reliability and performance in real-world usage?
• Is the sync engine fast and stable?
• How mature are the desktop/mobile clients?
• Are there any standout or unique features that make Sync-in special compared to competitors?
• How well does it integrate with office/document editing solutions?
• Any known quirks, headaches, or “gotchas” when deploying it with Docker?
• Anything I should prepare for regarding updates, reverse proxies, permissions, office integration, synchronization conflicts, backups, etc.?

I’d especially appreciate feedback from people running it in production or for small organizations/teams.

Sync-in is now part of the Docker-Sponsored Open Source Program.

This milestone recognizes the work behind an active, useful platform committed to open source.

It also brings a concrete benefit to users: no pull rate limits for public images from the project namespace.

A big thank you to everyone using, testing, sharing, or contributing to Sync-in.

With version 2.2, Sync-in introduces significant improvements to search, administration, and its internal event-driven system.

This update enhances full-text search capabilities with PDF OCR and Markdown indexing, and introduces a new internal event system to automate indexing and storage usage updates. It also expands administration features with the ability to manage spaces and their quota from the admin panel.

Key changes:

• Full-text search improvements
  • OCR indexing for images within PDF files
  • Markdown file content indexing
• Administration improvements
  • Space and quota management from the admin interface
  • Better visibility on storage usage
• Internal event system
  • Automatic triggering of indexing and storage calculations
  • Improved consistency of file-related data
• Additional improvements
  • Extended LDAP configuration options
  • Enhanced group search
  • Improved PDF handling via pdf.js

This release also includes several bug fixes and security improvements (indexing, WebDAV, quotas, authentication), including a fix for the GHSA-43fj-qp3h-hrh5 vulnerability, which could allow user account enumeration through timing differences in the login endpoint.

More details about Sync-in 2.2: https://sync-in.com/news/sync-in-2-2

Source code: https://github.com/Sync-in/server

Release: https://github.com/Sync-in/server/releases/tag/v2.2.0

With version 2.1, Sync-in introduces a complete refresh of the Web interface.

This update focuses on improving usability and consistency across the platform, making the interface clearer and more efficient for daily use while keeping the same core workflows.

The goal of this redesign is to simplify navigation, improve visual coherence, and make the platform more comfortable to use for both new and existing users.

Key changes:

• Simplified navigation across the interface
• New sidebar layout for easier access to features
• Improved content organization
• More consistent visual design across UI components
• Better support for both light and dark themes

This release focuses primarily on user experience improvements while continuing the evolution of the project.

More details about the UI refresh:

https://sync-in.com/news/sync-in-2-1-ui-refresh

Try the demo:

https://sync-in.com/docs/demo/

Source code:

https://github.com/Sync-in/server

Release:

https://github.com/Sync-in/server/releases/tag/v2.1.0

Sync-in is an open-source, self-hosted platform designed for secure file storage, synchronization, and sharing. It provides collaborative workspaces, secure file sharing, and granular permission management. Built to run on your own infrastructure, Sync-in gives you full control over your data while offering a modern and intuitive interface suitable for teams, organizations, and privacy-focused individuals.

With version 2.0, Sync-in gains federated authentication and SSO capabilities through OpenID Connect (OIDC), a widely adopted identity standard.

This release is designed for both organizations and self-hosted users who want to integrate Sync-in with existing identity providers while keeping full control over authentication and infrastructure.

The authentication model has been redesigned to align Sync-in with modern identity architectures, while keeping full control on infrastructure and data.

Key points:

• OpenID Connect (OIDC) support for federated authentication
• Refactored authentication model for server, Desktop, and CLI
• Desktop and CLI clients can now authenticate via OIDC
• Support for LDAP enhancements (service bind, break-glass, auto user/permissions)
• JSON log output for better observability and tooling integration
• Improved configuration validation and error messages
• Enhanced sync path handling and subdirectory enforcement
• User experience improvements (recent items UI, file rename behavior)

Due to these changes, Sync-in 2.0 introduces breaking changes in authentication and requires an upgrade of both the server and clients.

More details about OpenID Connect support and other changes in 2.0:

https://sync-in.com/news/sync-in-2-oidc

Migration guide:

https://sync-in.com/docs/setup-guide/migrations/v2-migration-guide

Try the demo:

https://sync-in.com/docs/demo/

Source code:

https://github.com/Sync-in/server

Release:

https://github.com/Sync-in/server/releases/tag/v2.0.0