Why incumbents structurally can't ship Sery's wedge

Reviewers keep telling us competition is heating up. The cloud-AI tools you already use are getting better at cross-document search. Office-suite AI is shipping new features every month. The OS vendors will eventually search everything on your machine. We've heard the version of this argument that ends in "why bother?" — and we want to give the honest answer to it.

Short version: they're parallel ecosystems, not the same market. The two things they all structurally cannot do are the entire reason Sery exists.

The single-vendor problem

Every cloud-AI tool worth comparing Sery to has the same shape: it indexes one company's data within one company's ecosystem. The shapes break down into three patterns:

Office-suite AI inside one productivity ecosystem. Indexes that vendor's mail, drive, calendar, docs. Not your laptop. Not your NAS. Not your Linux server. Not the files on a different vendor's cloud. The vendor can't read what isn't in their stack — and won't spend engineering effort indexing competitors' stacks because that erodes their lock-in.
OS-level AI tied to one device family. Works on the device-family that ships it. Won't index a Linux server in your basement, a Windows machine at the office, or an S3 bucket the user pays for personally.
Cloud notebook / chat tools that take uploads. You upload per-source; they summarize. Brilliant for the specific use case, structurally upload-bound for everything else.

Pick any two of these. None of them will index both for you. Your Mac at home and your Windows desktop at the office. Your iCloud Drive and your team's third-party cloud storage. Your laptop and your NAS. Your work productivity account and your personal one. Your S3 bucket from a side project and your SFTP archive on a hosted Linux box.

That gap isn't an oversight on their part — it's the business model. Single-vendor lock-in is what their companies actually sell. A device-vendor won't spend engineering effort indexing rival platforms because making their data more accessible without their device is anti-strategic. Same for office-suite vendors reading each other's files. They could ship the cross-vendor wedge tomorrow. They never will.

The upload problem

The other half of the cloud-AI category requires you to upload your data to use it. Every cloud notebook, every file-upload chat surface, every SaaS data analyst — the bytes have to leave your machine before any reasoning happens.

That's fine for a single document, occasionally. It is structurally not fine for an entire user category:

Lawyers under privilege.
Doctors under HIPAA.
Journalists with confidential sources.
Therapists, counselors, anyone with patient notes.
Security and compliance engineers who'd be fired for uploading the wrong file.
Anyone working under an NDA, with proprietary data, or auditing someone else's books.
Anyone with a sense of this isn't for the cloud about their own life.

For these users, the cloud product cannot get good enough to matter. The constraint is structural — it doesn't loosen as the model gets smarter. Every increase in capability is paired with the same blocker: but I can't upload.

That category is not small. Every tightening of privacy regulation grows it. Every news story about a cloud AI training on something it shouldn't have grows it. Every leak, breach, or subpoena story moves another margin user out of the "upload to the cloud" cohort and into the "files stay on my machines" cohort.

What Sery is for

Two things, both of which the incumbents structurally cannot ship:

Cross-vendor universal data gateway. Connect every cloud storage you have — local folders, S3, Drive, SFTP, WebDAV, B2, Azure, GCS, Dropbox, OneDrive — in one app. Browse, preview tables and Parquet without downloading, and search by filename or column name across every connected source. The atoms (your files) stay in the storage that owns them; only catalog metadata travels — and only when you opt in. No single-vendor stack can ship this without abandoning its lock-in.
AI without the upload. The Sery cloud workspace runs an agent that fans SQL out to your machine through a private tunnel. The query executes locally on the user's machine; only the result rows travel back. Raw files never leave the storage they live in. Or expose your folder via MCP and let your editor / desktop AI client read it directly without involving Sery cloud at all. Two independent paths, you pick.

What category we're actually in

The honest list of operators that overlap with Sery's actual category — coordination layers that don't own the atoms they coordinate, with a real privacy posture:

Network-shape operators. They're not building data tools, but they validate the architectural pattern: an operator that coordinates atoms it doesn't own. Same shape, different atoms (we coordinate files; they coordinate packets, web requests, payment rails).
Independent local-first tools. Different surface (notes, project management, knowledge graphs) but the same audience and the same privacy posture. We're not competing with them; we're complementary.
The next AGPL+P2P entrant in our exact shape. Somebody eventually builds Sery's exact shape. The kits we've published on crates.io (scankit, tabkit, mdkit, sery-mcp) make it easier for them to start. We did this on purpose. The moat isn't the code; the moat is the network — each new endpoint compounds the value of every other endpoint already on it.

The thing reviewers usually miss

The framing isn't local-first vs. cloud-everything, who wins?. The framing is who is willing to upload, and who isn't?

For the willing-to-upload majority, the existing cloud AI tools are great. We're not trying to convert them. They have a tool that works for them.

For the won't-upload minority, no incumbent can serve them ever. Single-vendor incumbents structurally won't go cross-vendor; cloud-AI tools structurally require upload. The gap doesn't close as either side improves. It just keeps opening as more people land in that minority.

That's the user we built Sery for. Not the masses. The people for whom no cloud product works, ever. That market doesn't need to be huge to support a category-defining network company — niche-but-deep is the shape that compounds when each new endpoint multiplies the network's value.

We'll keep watching the incumbents — there's always something to learn from how they ship. But we don't worry about them. Different ecosystem.

Sery Link is open-source under AGPL-3.0. The current release is v0.8.4 — nine source protocols, four S3-compatible presets, MCP server for AI client integration, and a fully offline free tier with no account required. Try it at /download, verify the privacy claims at /trust, see the public numbers at /numbers.