Finished projects out of a full SharePoint or Google Drive, off an old server or straight off a drive. Every file checked, kept, and still a double-click away in the Finder. Half what your cloud charges.
shed /ʃɛd/ verb to let go of a load you no longer need to carry; noun the place you keep it.
Shed Sweep works out what is finished, moves it out of SharePoint or Google Drive into your shed, and leaves your team a note where it went. Your cloud stays lean, your bill stays down, and nobody has to remember.
One sign-in, one price per terabyte.
In the Finder and the browser. Permissions per folder, versions, every open recorded.
Shed for MacOut of SharePoint or Google Drive on a rule you set, every file checked first, still open to your team.
Shed SweepEvery version of a tenant or a server, kept outside it.
Backup as a servicePlug in a drive or camera card and it goes into the shed from the drive, every file checked, with a log emailed when it lands.
Ingest in Shed for MacComposite cases. The names are made up.
A creative agency whose SharePoint had grown to ten times what the licences included. Shed took the finished project folders a library at a time, checked every file, and left a note in each folder saying where it had gone.
An eleven-year-old file server in a cupboard that nobody would switch off, because nobody could say what was on it. It came across whole, folder structure intact, and became searchable for the first time.
A production company that wanted a copy of its working storage somewhere its cloud provider was not. A nightly checked copy of the edit volume and the delivery library, snapshotted and replicated to another country. Nothing was removed from the original.
Seven years of finance records, and card dumps too large for the cloud. The records went in by sweep and are opened twice a year; the rushes go in from the Mac app on shoot day.
First questions: what happens when SharePoint storage is full, what Microsoft's extra storage costs and how to free up Google Shared Drive space.
Shed works from the folders your team already uses, with the sign-in they already have.
Drag a folder into the Archive library, or set rules and let Shed Sweep find what counts as finished: untouched for a set number of years, over a size, or job codes marked closed.
Overnight, Sweep copies the folder to your shed and checks every file against the original. It shows what it would clear and waits for an owner to say yes. After a cooling-off period you set, the files leave your cloud and a note is left where the folder was.
Browse, search and preview in the browser, Office documents, PDFs, images and video included. Download a file or a folder, or put a folder back where it came from in one step. Every action is recorded.
Search reads names and the words inside documents.
| Result | Where | Size |
|---|---|---|
| Campaign_Book_FINAL.pdf | Archive / 2019 / Campaigns | 412.0 MB |
| Campaign_Book_v3.indd | Archive / 2019 / Campaigns / Working | 1.8 GB |
| Campaign brief, spring.docx | Archive / 2018 / Briefs | 84 KB |
| Book launch, run sheet.xlsx | Archive / 2021 / Events | 212 KB |
| Goes back to | The same place, with the same name. The breadcrumb note is removed. |
| Size | 41 folders · 6,208 files · 212.4 GB |
| Checked | Every file is compared with the shed copy by hash as it lands. |
| The shed copy | Stays. Nothing is removed from the shed. |
Project drives and shoot disks going back years. We read them, list every file, and keep what is on them.
Drives from one company overlap. Shed stores those bytes once, and the catalogue shows every drive a file came from.
Every drive is read and every file listed with its size and fingerprint: what is there, what is duplicated, what is unreadable. The folder structure is kept, drive by drive.
Anything that will not read cleanly is reported by name.
Drives are wiped and destroyed with a certificate each, or sent back to you.
A file counts as arrived when the shed has computed the same fingerprint. A transfer resumes after a sleep or a dropped connection, and a file already in the shed is not sent twice.
Files too big for the cloud go straight in. Three ways, every file checked.
| Item | Size | Status |
|---|---|---|
| A001 to A014 (card dumps) | 3.9 TB | Verified |
| B001_C007.mov | 48.2 GB | 62% · 11 min |
| Key_art_final.psb | 6.4 GB | Queued |
| Grade_v3.drp | 212 MB | Queued |
| Stills_selects (1,204 files) | 38.1 GB | Queued |
Every sign-in, search, open, download and change of access, with who and when. Export it as CSV.
Limit any folder to named people, a group or a domain. The rule covers browsing, search, downloads and ZIPs.
A card on every page shows what the shed would cost in extra cloud storage, what it costs here, and how much Sweep has cleared.
We set it up with you. Nothing changes for your team until the first sweep is approved.
A shed connects to the clouds your work lives in and to the system your jobs come from.
Approve Shed once and it finds every site, library and Shared Drive. You tick what it sweeps. A connection starts as copy only.
Connect it and job numbers become a way of finding files. File a folder against a job and everything under it comes too. Open a job and see what the shed holds for it.
GET /api/v1/jobs/FH2419 answers with the files, what they come to and links back into the shed. A token sees one shed and nothing else.
FH2419 is a job at Fieldhouse Studio, the imaginary company in the examples on this site.
Used on its own, a shed moves nothing and deletes nothing. It takes a copy of what you have, on a schedule, every file checked, on a node in a country you choose.
A file server, a NAS, an edit volume, a SharePoint library or a Shared Drive, copied as it stands.
A backup job only reads. It cannot write to your source or delete from it.
Nightly snapshots, kept for the period you choose, that nobody can quietly alter.
Where the work is big enough, a Shed node in your own building. Rushes land on it at local speed, your team works from it, and it replicates to your shed overnight.
Microsoft sells overflow storage by the gigabyte. Shed is priced per terabyte at half that rate, in your currency.
Over the quota Microsoft gives your tenant, every terabyte costs £180 a month to keep in Microsoft. In a shed it costs £90.
Microsoft's UK list price for Office 365 Extra File Storage, £0.18 per GB a month on a monthly term (£0.16 on an annual term), per terabyte per month, at last check.
Microsoft bills by the gigabyte; Shed by the terabyte kept, rounded to 100 GB. How the pooled quota works.
Billed monthly on what you keep. No minimum term, no setup fee, no charge to leave.
Cold tiers freeze files. Extra cloud storage keeps paying the cloud's price.
| Shed | SharePoint extra storage | Microsoft 365 Archive | A server in the office | |
|---|---|---|---|---|
| Browse, search and preview | Yes, in the browser | Yes | Frozen until reactivated | On the office network |
| Frees your tenant quota | Yes, the files leave | No, you buy more | Yes, at a lower rate | Yes |
| Snapshots you control | Nightly, immutable 14 days | Version history only | No | If you set them up |
| Replicated across nodes | Included | Microsoft's own | Microsoft's own | Extra kit and a service |
| Verified file by file | Before anything is removed | No | No | Only if you script it |
| Who fetched what | Full record, exportable | Audit log, with the right licence | Audit log | Rarely |
| Put a folder back | One step | It never left | Reactivate, then wait | Copy it by hand |
| Up-front cost | None | None | None | Thousands, plus a backup plan |
Per terabyte, yes, at about a quarter of Extra File Storage. The files are frozen while archived and stay in the same tenant. A shed costs more than a cold tier because the files stay open to your team, outside the cloud that ran out of room. More on Microsoft 365 Archive.
Google's add-on storage is roughly US$30 to US$40 per terabyte a month, less than a shed. The reasons to move finished work out are the same: it leaves the live environment and its sharing links, and it is checked and snapshotted on storage built for keeping. Sweep handles Shared Drives and exports native Docs, Sheets and Slides in Office formats.
None. The figure we halve is Microsoft's published rate for storage above your quota, US$0.20 per GB a month. Sterling uses the UK billing figure; other currencies are converted and rounded. Tell us the figure in yours and we price against that.
No. You are billed monthly on what you keep, rounded to 100 GB. If you leave, everything is handed back as plain files with the manifest, and our copies are deleted within 30 days.
You set what counts as old. Sweep finds it, shows what it would move, and waits for approval. It never removes anything from your cloud without a recorded yes.
Nothing changed for a number of years you choose.
The heaviest folders move first, so the quota comes back fastest.
A naming pattern or a column in the library that says the job is done.
Mark a folder off limits and no rule touches it. Anything dropped in the Archive folder goes on the next run. Google Docs, Sheets and Slides are exported in Office formats.
What moves, why it matched, what it frees. Approve it, or take folders out. The note on the right is left in the cloud.
| Folder | Last changed | Rule | Size | |
|---|---|---|---|---|
| Move | Campaigns / 2019 | 20 Dec 2019 | Untouched 3 years | 96.1 GB |
| Move | Campaigns / 2020 | 18 Dec 2020 | Untouched 3 years | 71.4 GB |
| Move | Campaigns / 2021 | 22 Dec 2021 | Untouched 3 years | 44.9 GB |
| Move | Jobs / FH-0412 Harbour launch | 03 Jun 2022 | Job code closed | 88.0 GB |
| Keep | Jobs / FH-0598 Rebrand | 11 Nov 2024 | Over 50 GB, changed recently | 58.7 GB |
Every pull, check, removal and index shows its progress as it runs.
Rules, schedule, mode, cooling-off and who to tell, per library or drive. Change a setting and the next run uses it.
Every file Sweep copies is compared with the original by hash before removal is offered. The report is kept with the data, and a scheduled check re-reads the shed against it.
New York, London, Singapore and Melbourne.
Shed is not a reseller. The servers are ours, bought outright and run by us.
We buy the servers and the disks. No margin on somebody else's storage.
Disks are recorded by serial number. A replaced disk is wiped, destroyed and certified.
Keys held by us.
Our nodes run on green energy plans wherever one is offered.
| Your node | The copy | |
|---|---|---|
| Your files | Encrypted at rest, open to your people by sign-in | Encrypted snapshots |
| The index and activity record | Here | None |
| Encryption key | Held here | Never |
| Who can reach it | Your people by sign-in, and the people who run Shed | The people who run Shed, with the key |
| Who runs the machine | Ours, bought outright | Ours |
Written to the headings tenders use. Quote any section. Where we do not hold something, such as a certification, we say so.
| Narrowed inside HR | Who |
|---|---|
| HR / Public | Everyone at fieldhouse.studio |
| HR / Payroll | finance@fieldhouse.studio |
This statement covers app.shed.work, the Shed Sweep worker, the node holding your files and its snapshot copy. It is written to the headings questionnaires use so it can be quoted section by section; where a tender needs its own format we complete and sign it from this page. Policies, the architecture diagram and restore results are available under a non-disclosure agreement.
One accountable owner for security, named in your agreement, approves every change to production and reviews access quarterly. Controls follow ISO 27001 Annex A and the Australian Cyber Security Centre's Essential Eight. We hold no certification and claim none; where a tender requires one we say so and describe the control instead.
Your files are on a node we own in the country your agreement names, with its snapshots replicated to our other nodes. No client file sits on shared public cloud compute. There is no test copy of client data; testing uses synthetic files.
Files and their names are encrypted at rest with AES-256, with keys we hold. Every connection uses TLS 1.2 or 1.3 with HSTS: your browser, Microsoft and Google when Sweep reads your cloud, and between our nodes. The snapshot copy cannot read what it holds. The credentials Sweep uses to read your cloud are encrypted with a key held outside the database and never logged. Storage uses block-level checksums, so silent corruption is caught on read and on the scrub.
There are no Shed passwords. Sign-in is by Microsoft Entra ID or Google Workspace, and the tenant or domain must match your company's record. MFA, conditional access and session policy are inherited from your tenant. Admins manage access; any folder can be narrowed to named people, a group or a domain, and the rule covers browsing, search, previews, downloads, ZIPs and Put back. The people who run Shed sign in the same way, and every administrative look at a shed is written to that client's own activity record.
The web application cannot write inside a shed: every change is a recorded job carried out by the worker, with version history and snapshots behind it. Nothing is deleted outright; removals go to a bin kept for 30 days. Each company's shed is its own storage path and its own rows, enforced in the database as well as the application. Signed host-only cookies, a CSRF token on every form, security headers, rate limits and a content security policy at the edge. Secrets live outside the code. Client-arranged penetration tests against a staging shed are welcome with notice.
Before anything is removed from your cloud, every file is compared with the original by hash and the report is kept with the data. A manifest of every path, size and hash is kept for each shed, and a scheduled check re-reads the shed against it. Removal from your cloud is a separate, approved step with a cooling-off period you set.
Snapshots nightly, kept 30 days and immutable for the first 14, replicated across our nodes. Recovery point 24 hours; a snapshot restore of any folder within 4 hours of request. Because the application cannot write to the shed and the copy uses separate credentials, a compromised workstation cannot encrypt or delete the archive.
Every sign-in, listing, search, preview, download, ZIP, Put back, access change and administrative action is recorded with who, when, what and from where. Owners see the record and can export it. It is kept for the life of the shed and 12 months after. Storage, replication, snapshots and the application are monitored with alerts to us; the status page is updated by hand.
We tell you within 2 working days of learning of a security incident affecting your shed: what is known, what has been done and what we need from you, with a written report when it is closed. Incidents notifiable under the Australian Privacy Act, the UK GDPR or the GDPR are handled within those timeframes. A named contact on each side is agreed at setup.
Operating systems, containers and dependencies are patched monthly; critical fixes within 72 hours of release. Every production change is made from the versioned stack and recorded with who and when. Changes that affect your data path are announced on the status page.
A small named team, each under a confidentiality agreement, with access granted for the work in hand and reviewed quarterly. Nobody at Shed opens or analyses your files beyond what listing, search, preview and verification need.
Microsoft and Google provide identity and are where your files come from, under their own terms. Sign-in and the index run on a server rented from one hosting provider, named in your agreement and in our privacy statement; it never holds a file. There are no other subprocessors, and we give 30 days' notice of any change.
Your files are plain files on plain storage. Take everything with you at any time, as a download or on a drive we ship, with the manifest. If you leave, we delete our copies, snapshots included, within 30 days and confirm it in writing. Nothing is deleted from a shed without a recorded request from your Admin.
Shed is a processor for the personal information inside your files and a controller only for the sign-in and activity record described in our privacy statement. The Australian Privacy Act applies; the UK GDPR and the GDPR apply to UK and EU clients and a data processing agreement is available. The law of Victoria, Australia governs the agreement.
Send the questionnaire and we complete and sign it from this page, usually within three working days. Under a non-disclosure agreement we also provide the items on the right.
Ask for the tender packYes, once the files leave the site recycle bin, which we can do as part of the removal. One exception: if a retention policy covers the site, SharePoint keeps deleted items in a hold library until the policy expires. We check this for every library before quoting a saving.
Everything is browsable and searchable in the browser, with previews for images, PDFs, video and Office documents. Folders download as a ZIP, and anything can be put back where it came from in one step.
Everyone at your company who can sign in, unless an Admin narrows a folder to named people, a group or a domain. People outside your Microsoft tenant or Google domain cannot sign in at all.
Your files are plain files on plain storage, with a manifest listing every path and hash. They can be handed over on a drive or copied to any destination you name.
For Microsoft 365, an app registration in your tenant with read access to the sites you choose, and write access only to leave the note and remove approved files. For Google Workspace, a service account with access to the Shared Drives you choose. You grant it, you can see it, you can revoke it.
Yes, at any point before the removal. That is what the cooling-off period is for. The copy stays in the shed and the originals are untouched.
Before a move: how to archive a SharePoint library without breaking links, and what to do when the tenant is about to go read-only.
Tell us which libraries or drives are full and roughly how large. We size a shed and set up the first sweep with you.