Product
Sotto has two halves. The desktop app works where your files are: it converts folders into assets, makes previews and publishes. The web portal is where everyone else finds, reviews and downloads them.
Desktop app · macOS
The desktop app reads your working folders, never changes them without asking, and publishes what is ready.
Before · the folder you have
Duplicates, a “final” that isn’t, a working file next to the deliverable, an image nobody can name.
After · one asset package
Turn one folder, twenty folders or a single file into asset packages. Deliverables go to OUT, working files to WRK, and tags are proposed from the folder path. Nothing converts without your review — and it works from the Finder right-click menu.
Every asset gets a short permanent ID in its folder name. Rename a tag, a file or the asset itself and ratings, comments and history stay attached. Nothing is ever keyed on a filename.
Thumbnails, video posters, previews, cloud delivery and the database sync run as independent phases in one pipeline. Content hashes skip files that haven’t changed.
Each client can have its own destinations: Dropbox, Google Drive, OneDrive or SharePoint, or a synced local folder. Pick the layout per destination — source tree, deliverables only, or flat.
Optionally mirror each asset as a Markdown note in an Obsidian vault, so your library and your thinking live side by side.
Web portal · library & search
Filenames are for computers. People look for a product, a moment, a format — so that is what Sotto indexes.
Summit pack — strap detail
Summit pack — on the ridge
Summit pack — explainer 60s
Summit pack — retail one-pager
Spring launch — sales deck
Spring launch — teaser 15s
Spring launch — key visual
Spring launch — trade fair kit
Type a tag or a name. Chips appear as you go; combine them with and, or and not in Advanced. Saved searches keep the ones you run every week.
Three dimensions — by default Entity, Angle and Format — shown side by side, never hidden in tabs. Rename them for each client: “Product”, “Campaign”, “Series”. Import and export as JSON.
Filters, the open asset, the focused variant and the lightbox all live in the address. Send a view to someone; it survives a reload and a sign-in round trip.
Named groups of assets, private or shared with the client. Set who may open them separately from who sees them in the list.
A shoot of forty images is one asset with forty children, not forty search results. Open it, step through, download one or all.
The master file stays the download. Sotto adds streaming playback, posters and hover previews on top, and protected videos only play through a signed link.
Light and dark mode. Works on phones, with touch selection and swipe through galleries.
Portals & sharing
Their logo, their colour, their people. On Small Team and above it runs on their own domain — sotto.theirbrand.com. Their IT adds two DNS records; certificates, sign-in and file delivery are set up automatically.
People sign in with an email link or with Microsoft, Google or GitHub. Allowed email domains join a client automatically, so a client’s whole team can get in without you sending forty invitations.
Trail jacket — hero still
Trail jacket — seam detail
Trail jacket — rain test 15s
Trail jacket — side profile
Basecamp tent — pitch timelapse
Basecamp tent — front render
An asset is only visible at its level once it is approved or published; until then it stays with your team. Collections and links never show more than the viewer’s own level allows.
Public
Anyone with the link, no account.
Guest
Anyone signed in.
Member
People of that client, and your team.
Editor
Your team only. Drafts and internal work.
Feedback & versions
Five stars, not likes — feedback you can sort by.
On the asset, pinned to a moment in a video if you want.
Draft, approved, published. Nothing unapproved leaves your team.
Every version kept; members can request a restore.
One email per client when something you follow is published, gets a new version or a collection changes — never one per file.
Your team sees what is used. Clients never see each other.
Storage & security
Working files never leave your folders. Deliverables go to the cloud drives you choose; previews and published originals go to Sotto’s delivery network on Cloudflare, so the library is fast everywhere. If you stop using Sotto, nothing is locked in.
Access enforced by the database
Every query is checked by row-level security on the server. What the browser shows is never the security boundary.
Gated delivery
Files that are not public are served through a gate that checks the viewer’s level on every request.
Credentials stay on your Mac
Cloud-drive sign-ins are kept in the operating system’s keychain on the machine that publishes, not on our servers.
Safe to run again
A pipeline run that stops halfway can simply be run again; it picks up what is missing and skips what is done.
An EU company
Sotto is made and sold by Disrupt Collective s.r.o. in Brno, Czech Republic, under EU law.
Coming next
0.4
Add or remove tags on one asset or a whole selection, without touching files or history.
In design
Point Sotto at years of folders and get a reviewable draft of your library within a minute: a proposed vocabulary from boilerplates for agencies, marketing teams, creators and artists, refined by AI, confirmed by you.
Candidate
Sends a thumbnail — never the original — to a vision model and suggests a clear filename and extra tags from your own vocabulary. You review every row.
0.6
An agency owner with a personal portfolio, or a freelancer working for three agencies, switches between them like workspaces.
0.7
Release builds signed and notarised, updates in the background, sign-in through app.sotto.zone.
Later
Turn a selection of your library into a public portfolio page.
Sotto is in private beta. Tell us what you work with and how much of it there is. We are opening it to a few teams at a time and answer every request within two working days.