Sync-in

Self-hosted file storage, sharing, and collaboration, honestly reviewed. No marketing fluff, just what you get when you run it yourself.

TL;DR

• What it is: AGPL-3.0 self-hosted file storage and collaboration platform — file sync, sharing, WebDAV, real-time document editing, full-text search, all on your own server [README].
• Who it’s for: Privacy-conscious teams and solo founders who want Nextcloud-level features without Nextcloud’s configuration sprawl. Also small organizations with compliance requirements around data residency [homepage].
• Cost savings: Dropbox Business runs $15–$24/user/month. Google Workspace is $6–$18/user/month. Sync-in self-hosted on a $10 VPS is $10/month flat for your whole team, software cost zero [README].
• Key strength: Clean, modern UI with collaborative editing (Collabora Online + OnlyOffice), SSO, LDAP, and 2FA — enterprise authentication features that Nextcloud only added gracefully after years of rough patches [README][homepage].
• Key weakness: 903 GitHub stars at time of writing — this is a young project. Limited third-party reviews exist. Real-world production battle-testing data is thin. If you need something that thousands of companies have already hit hard, Nextcloud or Seafile are safer bets.
• License note: AGPL-3.0 — not MIT. You can self-host freely, but if you embed Sync-in in a product you distribute or offer as SaaS, AGPL requires you to open-source your changes. Relevant if you’re building a product on top of it.

---

What is Sync-in

Sync-in is a self-hosted file storage and collaboration platform. You run it on your own server, your files stay on your own infrastructure, and you get a web UI plus desktop clients for Windows, macOS, and Linux that sync files automatically. The GitHub description is direct: “Secure, open-source platform for file storage, sharing, collaboration, and syncing” [README].

The product covers three things simultaneously. First, file management and sync — drag-and-drop interface, cross-device sync via desktop clients, WebDAV for mounting as a network drive, offline task manager, and a gallery view for media [homepage]. Second, sharing and access control — spaces with fine-grained permissions, guest access for external collaborators, personal groups, secure share links with expiry dates and password protection [homepage]. Third, collaborative editing — Collabora Online and OnlyOffice integration for real-time co-editing of Office and OpenDocument files directly in the browser [homepage][README].

On the authentication side, Sync-in comes with OpenID Connect (OIDC) for SSO, LDAP for enterprise directory integration, multi-factor authentication with recovery codes, and application passwords for programmatic access [README]. These are features Nextcloud has but buries in plugins and configuration. Sync-in ships them as core.

The project has 903 GitHub stars and is funded via GitHub Sponsors and commercial support contracts [README]. It’s genuinely early-stage by open-source community standards — for comparison, Nextcloud is at 30,000+ stars and Seafile is at 12,000+. That’s not a disqualifier, but it’s context you should have before deciding to build your team’s workflow on it.

---

Why people choose it

Independent user reviews of Sync-in are scarce. The project’s community lives primarily on Discord and GitHub Discussions, and there are no substantial third-party review aggregators covering it at this stage. What follows is based on the product’s own documentation and positioning — not synthesized community feedback.

The pitch Sync-in makes — and that appears to resonate with the demographic this site targets — is simpler than Nextcloud but more capable than raw file servers. Nextcloud is powerful but frequently described (fairly) as configuration-heavy, plugin-dependent, and prone to update breakage when you have dozens of apps installed. Seafile solves the sync reliability problem well but has a less polished UI and weaker real-time collaboration. Sync-in positions itself between those two: a modern, well-integrated stack that ships with the features most teams actually need, without requiring you to assemble them from plugins [README][homepage].

The full-text search feature is worth calling out specifically. Most self-hosted storage tools search by filename only. Sync-in indexes document content — PDFs, Microsoft Office files, HTML, plain text — so you can find what’s inside your files, not just files by name [homepage]. For teams that store contracts, specs, or research, this is non-trivial.

The “Collaborative Spaces” model is the other meaningful differentiator. Rather than sharing files or folders ad hoc, you create purpose-built spaces for teams or projects with role-based access. Members can anchor files from other locations into a space without duplicating them. The design is closer to Notion’s “everything in one place” UX than Dropbox’s “shared folder” model [homepage].

What I can’t give you is a body of honest user feedback about bugs encountered, performance at scale, or upgrade reliability — because that data doesn’t exist publicly yet. This is the honest gap in this review.

---

Features

Based on the README and website:

File management:

• Drag-and-drop file operations, window manager, smart clipboard [homepage]
• Gallery view for media files [homepage]
• Sorting, filtering, enhanced viewer [homepage]
• Offline task manager — queue operations when disconnected [homepage]
• Storage quotas and file locking [README]
• Full document activity tracking [homepage]

Sync and access:

• Desktop clients for Windows, macOS, Linux [README]
• Multi-server support in the desktop client [README]
• Sync direction control, frequency settings, simulation mode, detailed logs [homepage]
• WebDAV for mounting as a network drive from any OS or third-party app [README][homepage]
• Spaces with fine-grained permissions per member or group [homepage]
• Secure share links with access limits, expiration dates, password protection [homepage]

Authentication and security:

• OIDC/SSO — federated authentication [README]
• LDAP integration [README]
• Multi-factor authentication with recovery codes [README]
• Application passwords for API/CLI use [README]
• Unified auth across web, desktop, and CLI [README]

Collaboration:

• Collabora Online and OnlyOffice integration for real-time document editing [README][homepage]
• Microsoft Office and OpenDocument format support [homepage]
• Comments on files, notification system [homepage]
• Activity feed for recently modified or commented files [homepage]

Search:

• Full-text indexing of PDF, Office files, HTML, plain text [homepage]
• Include/exclude keyword and phrase filtering [homepage]
• OCR support for text extraction from images in PDFs [1]

Deployment:

• Docker Compose and NPM deployment [README][1]
• Reverse proxy configuration documented [1]
• Authentication provider guides (OIDC, LDAP) [1]
• Version migration guides [1]

---

Pricing: SaaS vs self-hosted math

Sync-in itself is free to self-host under AGPL-3.0. The company sells commercial support contracts rather than charging for the software [homepage].

Sync-in self-hosted:

• Software: $0
• VPS to run it: $6–20/month depending on team size and storage needs
• Optional enterprise support: pricing not published — contact required [homepage]

What the enterprise support appears to cover (from homepage):

• Architecture guidance, security hardening, compliance support for multi-site environments
• Deployment, information-system integrations, performance audits, scalability
• Ongoing governance

SaaS alternatives for comparison:

Product	Pricing	Notes
Dropbox Business Plus	$24/user/month	15+ users only
Google Workspace Business Starter	$6/user/month	30 GB/user
Box Business	$20/user/month	Unlimited storage
Nextcloud Enterprise	custom	Support contracts only

Concrete math for a 10-person team:

• Google Workspace: $60/month at the cheapest tier
• Dropbox Business: $240/month
• Sync-in self-hosted: ~$15/month on a reasonable VPS with local storage, software cost $0

Over a year, that’s $720–$2,880 in SaaS costs versus roughly $180 self-hosted. The caveat is your own time for setup and maintenance — and if you need Sync-in’s enterprise support, that’s an additional cost the company doesn’t publish on the website.

---

Deployment reality check

Sync-in ships two deployment paths: Docker Compose and NPM [README][1]. The Docker path is the standard choice for anyone self-hosting.

What the docs cover [1]:

• Docker Compose setup guide
• NPM install guide
• Server configuration via environment.yaml
• Reverse proxy integration (nginx, Caddy, Traefik)
• OIDC and LDAP authentication configuration
• OCR configuration for PDF text extraction
• Version migration guides

What you actually need:

• A Linux VPS with 2–4 GB RAM (document collaboration and full-text indexing aren’t trivial on memory)
• Docker and docker-compose
• A domain and HTTPS (reverse proxy — Caddy is easiest)
• An SMTP provider if you want email notifications and invites

What’s unknown without real-world reports:

• RAM usage under sustained team load with collaborative editing active
• Storage overhead from full-text indexing at scale
• Upgrade reliability — whether minor version bumps break things
• Performance with large file libraries

If you’re integrating Collabora Online or OnlyOffice for real-time editing, that’s a separate service you run alongside Sync-in, not something it bundles. The docs mention integration configuration but you’re running two Docker stacks, not one [homepage].

Realistic time estimate for a technical user following the docs: 1–2 hours to a working instance. For a non-technical founder: expect a full afternoon plus someone to help with the reverse proxy configuration.

---

Pros and cons

Pros

• SSO, LDAP, and MFA out of the box. These aren’t plugins or paid add-ons — they’re in the core product [README]. For small teams with compliance requirements, this matters.
• Collabora Online + OnlyOffice integration for real-time document editing, supporting Microsoft Office and OpenDocument formats natively [README][homepage].
• Full-text search across document contents — not just filenames. PDFs, Office files, HTML [homepage].
• Clean, modern UI. The homepage screenshots and feature descriptions suggest a design sensibility closer to modern SaaS than classic open-source “functional but ugly.” Unverifiable without hands-on time, but the architecture choices suggest intentionality.
• Desktop clients with advanced sync options — direction control, frequency, simulation mode, multi-server [homepage].
• Guest access and personal groups for external collaborator management without giving guests full accounts [homepage].
• Docker + NPM deployment with documented reverse proxy and auth provider setup [1].
• WebDAV for mounting as a network drive without installing the desktop client [README].

Cons

• 903 GitHub stars — young project. Production reliability under sustained load is unverified by the community. There are no substantial third-party reviews to synthesize. You are an early adopter.
• AGPL-3.0, not MIT. If you build a commercial product on top of Sync-in and distribute it, AGPL requires opening your source. Not an issue for self-hosting, but relevant if you plan to white-label or resell.
• Collaborative editing requires a second service. Collabora Online or OnlyOffice must be deployed separately — Sync-in integrates with them but doesn’t bundle them [homepage].
• No published enterprise support pricing. The commercial support offer is real but you can’t evaluate cost without contacting sales [homepage].
• Smaller ecosystem than Nextcloud. Nextcloud has 30 years of plugin development, a large app store, and integrations with everything from Jira to Mattermost. Sync-in doesn’t have that surface area yet.
• Limited community evidence of scale. No documented case studies, no public deployments of 100+ users referenced anywhere.
• OCR adds complexity. Full-text search on image-heavy PDFs requires OCR configuration as a separate step [1].

---

Who should use this / who shouldn’t

Use Sync-in if:

• You’re running a small team (2–20 people) and paying $50–$200/month for Dropbox or Google Workspace and the files are the only reason you’re there.
• You have compliance or data residency requirements and need files on your own infrastructure.
• You need SSO and LDAP and don’t want to configure Nextcloud plugins to get them.
• You have a technical person who can deploy Docker and set up a reverse proxy — or you’ll pay someone to do it once.
• You’re comfortable being an early adopter and can tolerate a younger project’s rough edges.

Skip it (try Nextcloud instead) if:

• You need a proven, battle-tested platform with thousands of documented production deployments.
• You rely on third-party integrations (Jira, Mattermost, calendar sync, Outlook integration) — Nextcloud’s app ecosystem is vastly larger.
• Your team is large enough that upgrade risk on a young project is unacceptable downtime.
• You need a publicly vetted security track record — Nextcloud has CVE history, security advisories, and a documented response process that Sync-in hasn’t accumulated yet.

Skip it (use Seafile instead) if:

• Your primary requirement is fast, reliable delta sync of large file libraries.
• You don’t need collaborative editing and want something proven and lightweight.

Skip it (stay on Google Workspace) if:

• Your team is already fully embedded in Google Docs and Calendar — the collaboration workflow doesn’t translate cleanly.
• You have fewer than 5 people and the cost is under $50/month.

---

Alternatives worth considering

• Nextcloud — the established leader in self-hosted file sync and collaboration. 30,000+ stars, massive plugin ecosystem, proven at scale. Heavier to configure correctly, more moving parts, but far more community knowledge available. If you need “definitely works in production,” Nextcloud is the answer.
• Seafile — 12,000+ stars, focused on reliable file sync. Less polished UI, no built-in document editing, but rock-solid delta sync performance. Good choice if files and sync are the core need.
• ownCloud — the predecessor to Nextcloud. Still maintained, commercially backed, but the community has largely moved to Nextcloud.
• Syncthing — purely P2P sync, no server, no web UI. Excellent for syncing between your own devices without a central server. Not a replacement for shared team storage.
• FileBrowser — minimal file manager and web interface for an existing storage directory. Zero collaboration features, but zero overhead too. Good for personal use.
• Dropbox Business / Google Workspace — the SaaS incumbents. Easiest onboarding, zero maintenance, full vendor lock-in, and pricing that scales against you as your team and storage grow.

For a non-technical founder evaluating escape from SaaS file storage, the realistic shortlist is Sync-in vs Nextcloud. Sync-in if you value a cleaner setup experience and modern auth out of the box, and you’re okay being an early adopter. Nextcloud if you need something the internet has already broken and fixed a hundred times.

---

Bottom line

Sync-in is doing something real: shipping a modern self-hosted file and collaboration platform with SSO, LDAP, full-text search, and real-time document editing — features that Nextcloud provides but requires meaningful effort to configure correctly. The UI and architecture appear thoughtful, and the deployment documentation is solid for a young project [1][README][homepage].

The honest constraint is the 903-star count. This isn’t a criticism of code quality — it’s a statement about community-verified production experience. If you build your team’s document storage on Sync-in today, you’re an early adopter. That means fewer Stack Overflow answers when something breaks, no community case studies at your scale, and less certainty about upgrade reliability. The upside is you get a cleaner, more modern stack than Nextcloud and potentially better support economics as the project grows.

For a non-technical founder currently paying $150/month for Dropbox Business for 10 people: the math absolutely works. The risk is not cost — it’s picking a project at 903 stars instead of 30,000. If that risk profile fits your tolerance, the setup investment is reasonable and the ongoing cost is minimal. If it doesn’t, Nextcloud is the safe choice, and the cost savings are still real.

If the deployment itself is the blocker, that’s the kind of one-time setup upready.dev handles for clients — you pay once, you own the infrastructure.

---

Sources

1. Sync-in Documentation — Installation & Setup (official docs). https://sync-in.com/docs/category/installation—setup

Primary sources:

• GitHub repository and README — https://github.com/sync-in/server (903 stars, AGPL-3.0 license)
• Official website — https://sync-in.com
• Desktop client repository — https://github.com/Sync-in/desktop