Oct 9, 2026
On main, next release
Project settings read as rows and save as you change
The Project settings tab now lays each option out as one aligned row - description on the left, control on the right - inside a single card per section, instead of a card per option. The simple controls (project type, commit mode, history retention, data plane, guest access and the public-page options) save as you change them; Access control still asks before switching to protected mode. Project type, commit mode, access control and keep-full-history are all editable here now, and turning full history off is refused while a project has git access.
Project settings move to their own tab
A project's own settings now live on a dedicated Project settings tab instead of being tacked onto the bottom of the Storage tab, grouped into sections (Overview, General, Versions & history, Data & network, Collaboration & access, Public page). The editable controls are now all in one place - project type, commit mode, history retention (including keep-full-history), data plane, access control, external collaborators and the public-page requests. Storage keeps the metadata usage meter and maintenance.
Larger release assets from the command line
Attaching a release asset from the command line now handles files well past the old hundred-megabyte limit - up to five gigabytes, uploaded directly to the project's storage instead of through the service. The diagnostic check that verifies storage access is also renamed to say what it checks.
Turning on git access handles missing object ids
Enabling git access on a project with older files no longer stops to ask you to record missing object ids first: enable records them itself (hashing the file content it can reach, fetching what it needs) and then retries. The standalone backfill command still shows the whole job when you want to watch it, and a new option keeps the old refuse-first behavior for scripts.
Per-kind email overrides from the command line
The notifications command can now set one event kind's email override - on, off, or back to the global switches - and merges it into your existing overrides, so the rest and their webhook flags stay as they were. The dashboard remains the friendliest place to see them all at once.
0.3.8: big git pushes and protected roots
Two fixes for heavy git users. A large commit could dead-end the server's commit-id derivation once it touched more than about a hundred files at once, which could leave a big push without a confirmed id; the derivation now walks the change in bounded batches. And when the same person's two claims disagree about a commit's id, the first is kept and the challenger recorded as evidence rather than both being discarded, so a disputed commit stays visible while the disagreement is worked out. A push refused for moving a protected project's root now names the remedy - fetch and rebase, or have an owner clear the stranded head - instead of git's raw error.
Import an existing git repository
An existing GitHub, GitLab or local repository can now become a Swarmfile project in one command: swarmfile git import <url>. The source's default branch becomes the project's, commits keep their upstream ids, and the full history is there from the start. Annotated tags become lightweight by default (choose to skip or stop instead), a branch shape the git view cannot hold is skipped and listed, and running the command again with no options syncs new upstream commits into the same project. A partial import resumes from a local mirror that keeps no credentials.
Removing access now reaches every machine
Removing someone's access to a file or folder now reaches every affected computer as a targeted notice: the revoked content is dropped from that machine's local copies, further opens are refused, and a machine that was offline catches up when it reconnects. Organizations can also set how long a computer may keep serving already-downloaded content with no contact from the service; the default is seven days.
Anyone can file an RFI on a public project
A public project can now take requests for information from anyone: a registered visitor files one from the project page without joining the organization, tracks and replies to their requests in one place, and the team gets a notification carrying the requester's verified name and email. Filings land in the project's own RFIs folder. Non-member attachments are not accepted yet.
Ask for access to a public project
A public project can now take access requests: a signed-in visitor asks for comment access, contributor access (upload files), or membership, sees where the request stands, and can withdraw it. Owners and admins review the queue from the project's Project settings tab; a guest or contributor grant attaches to the project's Contributions folder, and a membership request becomes an ordinary invitation. Off by default, per project.
Publish a release from the dashboard
Releases can be published from the dashboard with a guided flow: choose a tag, review a side-effect-free preflight - whether publishing would be blocked, which paths the public page hides, whether the tag's policy differs from the default branch's - then confirm. The same preflight is available from the command line, with a distinct exit code when publishing would be blocked.
0.3.7: release assets from the command line
The desktop and command-line release that carries the long-operations and instant-rename entries above, plus release assets from the command line: attach a named binary to a release without it living in the project tree, list what is attached, or remove one later.
Hosted CI: jobs run on our machines now
Every push, tag, merge request, schedule or manual run can start a CI job in its own isolated container, with a token scoped to that job, secrets that can only be written, live logs, artifacts, a dependency cache, and one-click reruns. A small file on the branch describes the jobs; a GitHub Actions workflow can be imported one way. Compute bills per second of container time at our underlying provider's cost plus ten percent, with a sixty-second minimum, and jobs run on every plan - a payment method is required only where none is on file.
0.3.5: Windows drives refresh, rename and grow correctly
Remote changes now show up on a Windows drive without navigating: a teammate's create, rename, move, delete or in-place save refreshes an open Explorer window and a freshly opened file within a few seconds. Opening a file immediately after a teammate creates or renames it no longer fails with "Could not find file": the drive briefly holds the open only when there is real evidence that a matching change is still on its way, and a genuinely missing name still fails immediately even while other files are changing. Growing a file - the shape CAD and editing apps use to extend a save - now commits the larger size and its bytes. Accented names open by either Unicode spelling, and a file another process already has open keeps serving its old bytes until it is reopened, the same network-share behaviour as before.
0.3.4: sign-in, project defaults and drive-save fixes
Signing in on the desktop app now completes when your organization requires an authenticator code: a code step, with recovery codes, replaces the refusal. New projects are Open by default on every plan and in every app - web, Desktop and CLI - while Protected stays an explicit choice. Saves made through the drive are named "Saved N files" in history instead of showing no message. The Desktop App now notices when its engine and app versions don't match and offers the right repair: restart the engine, install the pending update, or reinstall when the install points outside the app bundle. Invitations and permission changes show up without a manual reload, and a member without access to a protected project sees that plainly instead of an empty file list. A drive also no longer fails to mount a plaintext project with a misleading "can't unlock" message after a burst of requests was briefly rate-limited.
Keep paths out of a public release
A project can now commit a .swarmfile/publicignore.yml naming the paths that must never reach its public page: internal notes, licensed assets, an unpublished cut. Hidden paths are left out of the release entirely - no browse entry, raw stream, download, archive entry or Explore result - and the policy is read from the tag being published, so a later listing can't expose what an earlier publish hid. An invalid file fails the publish with the reason instead of shipping unfiltered, and changing the file affects future publishes only. The file also records how CI logs attached to a release are exposed; no release carries attached logs yet.
Choose how your own bucket serves the public
Organizations that bring their own storage get two dashboard switches. Anonymous streaming of public media from your bucket is off by default - switch it on and visitors play without signing in; leave it off and public pages fall back to the sign-in-gated download. Gated release downloads are controlled separately: on automatically for an org that already had public releases, off by default for a new BYOS org until an owner turns it on. Swarmfile applies per-IP rate limits and byte budgets to public streaming, but your provider bills the requests and egress.
Root uploads on protected projects respect project grants
Creating a file or folder at the top level of a protected project - or moving one there - is now allowed for the project's creator and for anyone holding a project-wide write grant, not only org owners. Before this, an invited member with a project-wide write grant could read the project and edit inside granted folders, but a new file at the root was refused after its blocks had already uploaded, so the save silently never appeared. A deleted or absent project still fails closed, and the refusal now has its own recognizable outcome, which the desktop app holds in its create queue instead of dropping.
Long operations you can walk away from
Work that can take minutes - merges, checkouts, big deletes, restoring a folder - now runs as a durable operation in the engine instead of in your terminal. Ctrl-C detaches rather than cancelling: the command exits 3 and prints an id, and --no-wait returns at once. swarmfile op list / status / wait / cancel collect the outcome later, even after the engine restarts. A project delete or a folder delete, restore or purge above the hub's ~5,000-entry interactive cap runs as a background hub job the same way, so a large cleanup no longer has to be babysat.
Renames and deletes apply instantly
Renaming, moving or deleting a confirmed file - or an empty folder - no longer waits on the hub. The change applies on your machine immediately and is sent in the background, so a slow or briefly unreachable link can't stall a rename or a delete. Until the hub confirms it the app shows the change as a lightweight overlay, then re-verifies and refreshes in place, and the Desktop App marks peers serving it over the office LAN. Nothing is dropped: unconfirmed work is held and retried, and the web app's history, trash, merge-request and RFI views update live as it lands.
FedRAMP storage regions for Enterprise
Enterprise organizations can now have their metadata and block storage pinned to a FedRAMP or FedRAMP-High storage jurisdiction. The regions have been tested end to end, and we provision them through sales - there is no self-serve picker. This is not a FedRAMP authorization: Swarmfile itself is not FedRAMP-authorized, so raise the requirement with us before planning around it.
One settings surface for every project
Creating a project - in the web app, the Desktop App or the CLI - now draws on one options manifest, so every choice (encryption tier, commit mode, retention, visibility, ACL mode, data plane, project type, default-branch protection, the default branch's name, and the project's external-collaborator policy) appears with the same labels, choices and plan badges everywhere. Templates give a new project a starting shape: Blank, Media & post, Software (git repository), Revit worksharing, or Geospatial, with a starter ignore file and folder layout where they apply. After creation, the project's settings surface shows each effective value and where it came from, and swarmfile project show / swarmfile project set give scripts the same view and control.
Pin one project to its own region
An organization can already choose the EU or the US at signup. Now a single project can carry its own residency pin, set when the project is created (swarmfile project create --residency eu, or us) and independent of the organization's - useful when one client or contract needs its data to stay in a different jurisdiction. It needs the plan's residency eligibility and storage provisioned in that region, and it is fixed at creation.
0.3.1: reliability fixes for residency, purge and branch mirror
Released with the features above. Project data-residency checks now fail closed when a project's jurisdiction can't be verified (a refusal, not a silent pass), project creation rolls back cleanly if the residency pin can't be recorded, project purge clears the residency mirror, and branch-mirror scheduling is steadier.
Clone a project with git
Once an owner turns on git access for a project, git clone swarmfile://your-org/your-project gives you a real git repository of it: every non-empty branch and every tag as git history, large files as git-LFS pointers that Swarmfile serves, and git fetch to bring in new commits. You can push too: git push sends your commits back to the project (fast-forward only, merges land, force push is refused), so the drive and the clone can both be where work happens. The desktop installers include the small git helper it needs. Turning git access on is a one-way switch, because the rules that turn the project into git commits are frozen so commit ids never change under an existing clone. End-to-end-encrypted projects can't be cloned.
Require MFA or a verified email across your organization
Owners on Starter and above can now require every member to sign in with an authenticator app, to have a verified email, or both, starting right away or after a grace window of up to 30 days. Members are nudged to enroll in the web dashboard, the desktop app and the command line before enforcement starts, and owners can see who has and hasn't enrolled.
See where the bytes you read came from
The desktop app's new Data sources panel shows, for each file you've read and in total, how much came from this computer, from a colleague's computer, and from the cloud, with first-read times. Reset the counters to measure one session at a time; the same figures are available from the command line for scripts and reports.
Mac users: update to 0.2.41 now
Two serious bugs affected the Mac drive, and both are fixed in 0.2.41. First, releases up to 0.2.39 mounted the drive with a setting that let an app changing a file's extended attributes (Finder tags, comments and similar) trigger a crash in macOS's own network-filesystem client, restarting the Mac; the same setting made saves from TextEdit and some other apps fail. The drive no longer uses it: extended attributes now stay on the Mac that set them and aren't shared with teammates. Second, releases 0.2.36 to 0.2.39 could freeze the whole drive the moment a save was refused, for example a file locked by someone else or a project that had been archived, until the app was force-quit or the Mac restarted. A refused save now comes back as an ordinary error. There was no Mac build of 0.2.40, so update straight to 0.2.41 or later. Windows and Linux were not affected.
Set a ceiling on what overage can cost
Starter and Pro organizations now have a monthly spend cap on metered overage: storage above your allowance and extra external collaborators. It starts at your plan's seat charge, and an owner or admin can raise or lower it, permanently or for a set period. When overage reaches the cap, uploads that would add billable storage pause while reading, streaming and everything else keep working; the desktop app holds paused saves and sends them once the cap is raised or space is freed. A project API key can carry its own, lower budget as well.
Protected branches now refuse direct changes, not just merges
A protected branch used to block only direct merges - anyone could still edit files on it directly from a mount. Protection is now a write gate: saving, editing, renaming, moving, creating or deleting a file on a protected branch, staging and committing, rolling back, and resolving (or auto-resolving) a conflict all come back as "branch is protected - changes must land through an approved merge request". The way through is a branch and an approved merge request, as before; the merge itself is unchanged and still lands. Nobody gets a bypass, not even an org admin. Two practical notes: update every machine's mount/Desktop app before you protect a branch it works on - an older app reads the new refusal on a commit as a missing changeset and can drop its local commit session, while the updated app holds the work and tells you to move it to a branch - and reflecting LFS content (a git lfs push followed by reflect) onto a protected target is refused, so reflect onto a branch and merge it (the object upload itself still succeeds). Unprotected branches are untouched.
Handing back a whole project you reserved for offline work
When you reserve a whole folder or project for offline work (Pack & Go) and later choose Return from offline, other people could stay locked out of those files until the reservation expired - up to a month, in the worst case, with nothing in the app saying why. That's fixed: returning now releases the folder reservation itself, not just the per-file records, and it gives any saves still uploading a few seconds to land first, then tells you how many are still going. While you're online your reservations are renewed automatically (including across restarts, and for every mount you have open), so a trip away no longer silently outlives its lease; the Locks panel now lists folder/project reservations with who holds them and when they expire, including other machines'. Two machines can no longer each reserve the same folder and have one quietly lose its writes - the second one is refused up front with the holder's name. Canceling a reserve also stops the download it started, and switching a mount to another branch releases the reservation for the branch you left so teammates there aren't stuck. If you run an older desktop app, Return from offline there won't release a folder reservation; update the app to get the fix (the service also clears lapsed reservations on its own).
File conflicts are easier to see and safer to resolve
A pass over what happens when two people - or two machines - change the same file. A file with an unresolved conflict now wears a Conflict badge in the Files list, so you can spot it before opening it instead of only finding out once it is selected. Resolving a merge conflict by hand now writes the merged version back to the branch it came from as well, so the next merge doesn't immediately flag the same file again - and the hub checks you have write access on both branches before it does. The conflict text you hand-edit stays available for as long as the conflict is open (it could previously be cleaned up in the background), and a file added on a branch whose name someone created on the other side in the meantime is refused cleanly instead of applying part of a merge and stopping. Automatic merging is unchanged: it clears only what it can merge cleanly and leaves the rest to you.
A save made just after Swarmfile restarted could fail to reach your team
After Swarmfile restarted (an update, a reboot, a crash), the first save of a file you had also saved in the previous day could be recorded locally but never sent, so teammates kept seeing the earlier version until you saved that file again. Nothing was lost on your machine, but it didn't reach anyone else. That's fixed: every save now gets an identity that can't collide with one from before the restart, and if it ever did, the save is retried instead of dropped. If you edited files right after an update recently, saving them once more makes sure your team has the latest version.
Several projects on a Mac at the same time
On macOS the desktop app can now keep more than one project mounted at once, the way it already could on Windows and Linux: one mount per project or branch, each under its own path in /Volumes. Files stay live on every mount: reading or saving in one no longer freezes the others. Getting there meant fixing the filesystem library Swarmfile bundles for macOS, which until now could only serve a single mount per running app; the fix has been sent upstream and ships in this release.
Faster cold reads from the cloud
Opening part of a file this machine has never read got a lot quicker. On our staging service, with an 8 GB file and every byte coming from the cloud, the first read dropped from about 2.2 seconds to under a second, and a seek to a new spot from about 1.8 seconds to about 0.7. Most of the gain came from one fix: when a teammate's machine had just gone offline, every read used to wait a full second on it before asking the cloud. Now a peer that stops answering is skipped after a failure or two, the wait before asking the cloud adapts to how fast your peers normally answer, and the pieces a single read needs are fetched at the same time instead of one after another. Reading straight through a file (playing a video, copying it) now also fetches ahead of you in the background, without pulling more than it needs when you jump around.
Machines in the same office now find each other directly
Machines on the same network are supposed to discover each other automatically and share file data over the local network. That discovery wasn't actually announcing anything, so machines only found each other through the cloud service, and local transfers were treated like internet ones. It now works: in our tests, every byte a machine fetched from a teammate on the same network came over the local network. Discovery now only uses real local network adapters, not VPNs, virtual machines or container bridges. The Windows installer adds a firewall rule that lets Swarmfile reach other machines on the local network (on home and work networks only, not public ones), and a teammate's machine going offline no longer slows your reads while Swarmfile works out it has gone.
Conflicts on binary files: pick a side, no false promises
When a binary file (a texture, a model, a video) conflicts, the resolve dialog no longer offers an automatic merge or hand-editing, because neither can work on a binary format; it asks you which version to keep, or to keep both. Text files still get both options. Same change in the web dashboard and the desktop app.
Preview images are now encrypted at rest
On managed projects, the thumbnails, video poster frames and point-cloud previews the service generates are now stored encrypted with the project's own key, like the files themselves, instead of as plain images. Existing previews keep working and are replaced as files change. Video proxies and short-lived download copies are still stored unencrypted for now; the Security page lists exactly what is and isn't.
An API-key allowance on every plan, and packs when you need more
Each plan now includes a set number of project API keys for headless machines: 1 on Free, 2 per seat on Starter (at least 5), and 5 per seat on Pro (at least 10). Need more? Add them in packs of 10 for $20 a month from billing. Personal access tokens don't count against the allowance.
Two-step sign-in with an authenticator app
Protect your account with an authenticator app under Settings, Account, Security, with recovery codes in case you lose your phone. Once it's on, signing in also asks for a code from the app.
Open a file while it is still uploading
A file that is still uploading is now openable through the drive right away. It shows the size it is going to be, and reads stream the bytes as they arrive, served straight from the writer's machine over your office LAN before they ever reach the cloud. This only ever applies to a file that has no finished version yet, so a file you are already reading never changes under you. A read into a part that has not landed yet waits briefly and then reports a retryable 'try again' rather than an I/O error, so editing apps don't mistake a slow upload for a damaged file.
Check your project's history for yourself
Every confirmed commit is now hash-chained to the history before it, and the service regularly signs a checkpoint of each branch. A standalone verifier, installed with the desktop app, walks a branch from its newest commit back to the start, recomputes every hash and checks every signature, so an audit machine or a CI job can confirm the history hasn't been altered. Give it the signing key you trust and the check no longer depends on taking our word for it.
Public projects, releases, and Explore
Publish a tag of a public project as a release anyone can browse and stream, with a downloadable archive for signed-in users, a commit-pinned provenance badge, generated release notes and download counts, and the README as its landing page. Public projects with a release are listed, and searchable, on Explore; organizations get a public profile with followers, release emails and an RSS feed; and anyone can copy a release into a project of their own with Get this project. Publishing is from the desktop app or the command line.
A workspace for each coding agent, one shared dependency cache
Run several coding agents against one project on the same machine, each in its own labeled mount, and point them at one shared dependency cache so the same packages aren't downloaded and stored once per agent.
Large folders load fast in the Files view
Browsing a folder with tens or hundreds of thousands of files (a point-cloud tile set, a scan-output dump) no longer means waiting on one giant response or a sluggish, ever-growing list. The web dashboard's Files view and the desktop app's file picker now load a folder's contents in pages and only render what's actually on screen, so scrolling and sorting stay fast regardless of folder size.
A Free plan, no card needed
Start on Swarmfile without a card. The Free plan is for one person publishing public projects: storage that grows with the age of your account up to 1 GiB, free downloads, and one API key. Free projects are public and stored without encryption at rest; private and encrypted projects start on Starter, and you can upgrade the same organization whenever you're ready.
See exactly what changed in a merge request
Merge requests now show more than a list of changed files. Click one open to see the actual diff, with syntax highlighting and the specific words that changed on each line. A file that conflicts with the target branch shows a 3-way comparison instead: your changes and the target's changes, each against the version both branches started from, so you can see exactly what's colliding before you resolve it. Available on the web dashboard and the desktop app.
The right reviewers, requested automatically
A branch protection rule can now name a set of automatic reviewers, in the spirit of a CODEOWNERS file: every merge request opened against a matching branch asks for their review straight away, with nobody having to remember to add them.
A real grace period if a payment fails
If your subscription lapses, your projects don't disappear the moment a card is declined. You now get a 28-day grace period with reminder emails along the way to fix it, instead of a hard cutoff.
Swarmfile is now a git-LFS server
Point git-LFS at Swarmfile and your large binary assets get real storage, dedup, and quota instead of bloating your git host, while your source stays in the git host you already use. Stock git-LFS pushes objects up to ~100 MB through the hub at launch (a later direct-upload path raised the stock limit to ~5 GiB); a small transfer agent takes pushes up to 256 GiB per object, chunked and resumable; file locking works for files that live only in git; and you're never locked in: pulling everything back with stock git-LFS and no Swarmfile software lets you repoint at any other host and leave. Objects you push can also be projected onto the mounted drive as first-class files. One caveat on encryption: objects sent in blocks through the transfer agent are encrypted at rest like the rest of a private project, but objects uploaded directly by the stock git-LFS client, and uploads of 64 MiB or more through the desktop app's built-in agent, are stored without that encryption, and git-LFS isn't available on end-to-end-encrypted projects.
Keep your data in the EU or the US
Pin your organization's metadata and storage to a region (the EU or the US) when you sign up, and it stays there, enforced at the infrastructure level rather than by policy. It's included at no extra cost on every paid plan. FedRAMP and FedRAMP-High storage regions are available on Enterprise, provisioned through sales. Swarmfile itself is not FedRAMP-authorized, so talk to us before you plan around it.
Send events anywhere with webhooks
Swarmfile can now post to your own endpoint when files change, branches move, merges land, or people and permissions change, so Slack, Zapier, a SIEM, or your own service can react without polling. Every message is signed so you can verify it really came from us, outbound calls are guarded against pointing at internal addresses, and an endpoint that keeps failing is switched off automatically. You can also set up a personal channel just for the events you care about.
Protect a branch behind review
Mark a branch as protected (by name, or by a pattern like release/*) and changes into it need an approved merge request first. Set how many approvals a merge needs, and direct merges and writes are refused until the reviews are in.
Keep junk off the drive automatically
A .gitignore or .swarmfileignore file is now honored, so node_modules, caches, and build output are kept off the drive and out of your file listings instead of syncing to everyone. Nested rules and negation work the way you'd expect.
Bring your own storage
Enterprise organizations can point their primary block storage at their own S3-compatible bucket, so the underlying bytes live in infrastructure you own and control.
Mirror a branch to your own bucket
Mirror any branch to your own S3-compatible bucket (AWS, Wasabi, Backblaze B2, MinIO, or any other S3-compatible provider) as real files at real paths, not opaque blocks. Handy for a hand-off, a backup, or feeding a pipeline that expects plain files. Available on Pro and Enterprise.
Merge requests: review before it lands
Branching and merging back could already happen with nothing standing in the way. Now you can open a merge request instead (a named proposal with its own discussion thread), and it stays blocked until a teammate approves it. Anyone can request changes instead, and self-approval is refused, so review means an actual second person. Available from the dashboard, the desktop app, and the CLI, including a status check that scripts and CI can gate on.
Point an unattended machine at a branch and let it run
A render node or CI box can now watch a branch and run a job automatically the moment a matching commit or tag lands, with no person watching it happen. The rules live in a small file on the branch itself, so what runs travels with the code. Every run is recorded, with a history you can pull up per branch to see what ran and when.
Watch a file while it's still uploading
Asking for one part of a file in progress was already possible; watching one wasn't, because a viewer moves: it plays forward, and it seeks. Now it can. Point a follow job at a file someone is still uploading and it keeps a buffer ahead of wherever you are, re-targeting the moment you scrub somewhere else, and the uploading machine stops working on the stretch you scrubbed away from rather than finishing it first. How far ahead it buffers is measured from how fast you're actually watching, so a proxy and a full-resolution master each get the right amount. If the uploading machine is on the same network as you, it hands you the bytes straight off its own disk before they've even reached the cloud. Worth being straight about the limit: this decides which bytes reach you first, not how fast your connection is. A 4 TB master on a modest office uplink is still hours away whatever the order.
Ask for part of a file that's still uploading
A very large file on a slow connection can take hours to upload, and until now nobody else could open the new version until all of it had arrived. Now the file shows an "Uploading" badge while it's on its way (the version everyone can already read stays available and unchanged), and if you need part of the new one sooner, you can ask for it. The uploading machine sends that part first, so you get it in about the time it takes to send that part rather than waiting out the whole file. Handy when the reel, sheet or scan you need is at the end of something enormous.
Upload speed limits now apply at every value
An upload speed limit set below about 8 Mbps was previously ignored, so uploads ran at full speed. Limits now apply at every value, including low ones, and uploads slow to the rate you configured.
Sign in to the desktop app through your browser
Signing in to the desktop app now happens in the browser you already use: choose Sign in, finish there, and you're handed straight back to the app, with no codes to copy and no password typed into the app itself.
API keys for machines that don't have a person behind them
A render farm or CI runner no longer has to sign in as someone's actual account to talk to Swarmfile. Mint a key scoped to exactly one project, hand it to the machine, and revoke it independently whenever the job is done, without touching anyone's login.
Branch from an exact past commit, or a named tag
Forking a branch can now start from any past commit, not just the live tip, in one step instead of forking then rolling it back. Tag a commit with a memorable name to branch from later without hunting for a commit number, from the dashboard, the desktop app, or the CLI. Handy for pinning an unattended machine (a render node, a CI runner) to an exact historical state with no browser or Desktop App needed.
Windows: saving a file in place is reliable
Saving over an existing file on Windows and reopening it now returns exactly what you saved, every time. The overwrite path could previously leave the reopened file unreadable; that path is fixed.
Jul 2026
See exactly what you're paying for
A new usage panel shows what you're using against your plan, what each part costs, and an estimated total for the period, visible to anyone on the team, not just the account owner.
Jul 2026
Switch plans and manage billing without emailing anyone
Move between Starter and Pro right from the dashboard. Your existing subscription and trial carry over, no re-signing up. Cancel, update a card, or pull an invoice any time through a self-serve billing portal.
Jul 2026
Starting a trial is now one step
Sign up and you're straight into checkout, with no separate "create your organization" step in between. Your organization is set up automatically behind the scenes.
Jul 2026
A way to reach us, right on the site
A simple contact form for questions, demos, or anything else, so no more hunting for an email address.
Jul 2026
Fix it yourself
If something ever goes wrong with your install, a one-click repair option gets you back to a clean, working state, with no waiting on support.
Jul 2026
A simpler install on Mac
Installing on macOS no longer asks you to lower your Mac's security settings or reboot into recovery mode. Same drive, a much simpler first run.
Jun 2026
Review requests, right where the work lives
Architecture and engineering teams can now raise, track, and resolve requests for information and submittals directly on the drive, with no separate tool required.
Jun 2026
Branch a project, merge it back
Fork a project to try a variant without touching what everyone else is working on. Branching costs almost nothing and each branch works independently. When you're ready, merge the changed files back into main, with conflicts flagged so nothing gets silently overwritten.
Jun 2026
Commit a batch, revert it as one move
Group a set of changed files into one named, atomic commit. See the full history, and revert (or restore) an entire commit, folder, or project to a past point in time, not file by file.
Jun 2026
A new look, and dedicated pages for your team
Redesigned the whole site with a warmer, calmer look. New dedicated pages for media, geospatial, and AEC teams, a head-to-head comparison with LucidLink, and restructured pricing that's easier to compare at a glance.
Jun 2026
Tuned for Resolve, Premiere, and Avid
Performance tuned specifically for the editing and color tools studios actually use. Editors in the same office now share bandwidth automatically instead of each pulling from the cloud, and self-hosted seed nodes got a hardened setup guide.
Jun 2026
Your files survive losing a machine
When the engine judges it worthwhile (there are peers to hold the shards, and the file is at least 64 KiB), files are erasure-coded across shards, so up to four slow or offline peers never block a read. On a multi-machine office you can now deliberately spread those shards across your own workstations instead of leaving placement to chance (inspectable per file from the CLI), so losing any one machine in the office doesn't cost you data.
Jun 2026
Work offline, reconnect without losing anything
Files you've recently touched stay available even without a connection, and any edits you make offline sync automatically once you're back online. If someone else changed the same file while you were away, you get a clear choice (keep yours, keep theirs, or keep both) instead of a silent overwrite.
May 2026
Simpler, fairer pricing
Pro is now priced per seat, with metered overage only above your included storage. No surprise bills, no guessing what a plan actually costs as your team grows or shrinks.
May 2026
A mode for locked-down networks
For IT teams that block direct machine-to-machine traffic outright, Swarmfile can now run in a cloud-only mode, with everything routed through the same secure cloud path, no peer-to-peer connections at all.
May 2026
Point Swarmfile at your existing NAS
Run a self-hosted seed node against hardware you already own, and it joins the swarm like any other peer: a warm local tier backed by the cloud, not a wholesale migration off your NAS. Available on Pro and above.
May 2026
Review on the drive
Comment on any file and @-mention a teammate (or a guest reviewer) right where the work lives. They're notified by email or in the app; no round-trip to a separate review tool.
May 2026
Check a project out before you go somewhere offline
"Pack & Go" locks a file, or a set of files, to you for as long as you need. Travel to set, take a laptop somewhere without reliable internet, and know nobody else can land a conflicting change while you're away. Longer-lived than an ordinary edit lock, and released the moment you're back and done.
Apr 2026
See who's editing, and ask for it back
Real-time presence now shows exactly who has a file open, so you never overwrite someone mid-edit. And if a file you need is locked, you can request it in a click; the holder gets a prompt and the lock is released the moment they're done.
Apr 2026
Get notified the moment a specific file changes
Watch a single file or an entire folder and get notified the moment something inside it changes, on top of the project-wide change bell, for the handful of things you actually need to know about the second they move. Set it from the web, the desktop app, or the CLI.
Apr 2026
Notifications in your inbox, not just the app
Failed uploads, quarantined files, new comments, and mentions can now reach you by email too, with quiet hours and per-notification controls so you only hear about what matters.
Mar 2026
Bring your own identity provider
Connect your organization's own identity provider (OIDC, including Entra ID and Okta; SAML on Enterprise through an adapter) so sign-in and offboarding follow the rules your IT team already has. SCIM 2.0 keeps membership in sync automatically, and an on-prem LDAP sync agent covers Active Directory without exposing it to the internet.
Mar 2026
One feed for everything that happened
Team admins get a single activity feed (uploads, permission changes, comments, unlock requests, security events), searchable and exportable, instead of piecing it together from separate logs.
Mar 2026
Invite a client or consultant, no seat required
Give an external reviewer read or comment access to a single folder (fully audit-trailed and revocable in a click) without buying them a paid seat.
Feb 2026
Lock down who can see what, folder by folder
Grant read, write, or admin access on any folder or file, allow or deny, inherited down the tree, and enforced the same way no matter which machine or app touches the drive. On Windows, those permissions show up as real entries in Explorer's own Security tab, not just an app-level restriction.
Feb 2026
Know the moment something needs attention
Failed uploads, quarantined files, and changes from teammates now surface as native notifications in the Desktop App and a notification bell on the web, instead of failing silently.
Feb 2026
A built-in connectivity checker
Run a one-command diagnostic that walks through proxy, firewall, and DNS checks and tells you exactly what's wrong, instead of an IT team spending hours guessing.
2026
Revit worksharing over the drive, with no plugin
On Windows, native file locking is honored and enforced across every machine via the hub, so Revit central-and-local worksharing runs over the Swarmfile drive with no add-in, using the same OS-level approach the established players use. Mac and Linux machines use Swarmfile's own checkout locks, which work everywhere. A finer-grained byte-range lock API is available for custom element-level integrations.
2026
The drive comes to Windows
Windows joins macOS and Linux with a full native mount, both ARM64 and x64, Authenticode-signed. Right-click a file or folder on the drive for a Swarmfile menu straight in Explorer, and if a drive letter is already taken, Windows automatically relocates to a free one instead of failing to mount.
2025
See a file before you open it
Images, PDFs, and Photoshop files now get instant thumbnails and an in-browser preview: no download, no waiting for the full file to open.
2025
Browse and share from any browser
A full file browser in the dashboard, plus password-protected, expiring share links for sending a file or folder to anyone, with no account required on their end.
2025
Move your existing files in, verified
One command migrates a local drive or a NAS into Swarmfile, with resume support and a full report confirming every file arrived intact. (S3-bucket sources need a build with the optional S3 support enabled, which the shipped installers don't carry.)
2025
Find anything instantly
Search across every file, project, and person in your org from one search box, with a keyboard shortcut and deep links straight to the result.
2025
Nothing you delete is really gone
Deleting a file (from your file manager or the dashboard) sends it to a per-user trash instead of removing it outright, and every file keeps its own history so you can roll back to an earlier version without touching anything else in the project.
2025
Your files are encrypted before they ever leave your machine
Every file in a private project is encrypted at rest by default, on every paid plan. (Public projects, and projects on the no-card Free plan, are stored unencrypted so they can be served openly.) For teams handling pre-release or regulated content, an opt-in end-to-end tier keeps the encryption key off Swarmfile's servers entirely, so even we can't read your content.
2025
Ransomware can't take your project hostage
Swarmfile now watches for the pattern something overwriting your files leaves behind and quarantines the affected files inline, before more damage is done. Roll the project back to before it happened, and lock the attacker out.
2025
The Swarmfile drive, on your desktop
Signed installers for macOS, Linux, and Windows bring Swarmfile to your desktop as a normal mounted drive, with a menu-bar app for status and settings.
2025
Self-serve billing from day one
Start a trial, add a card, and manage your subscription entirely yourself. Usage-based billing tracks storage and extra external collaborators automatically in the background (downloads are free on every plan).