[verdict][curated prompt][source: iconik.io]
Can I vibecode Iconik?
// the value is the network, the data or the infrastructure
Iconik is not a search box, it is a storage gateway network. Its job is to make an on-prem NAS in one building, an LTO library in another, and three cloud buckets behave like one library, generate proxies for all of it, and then let a producer in another timezone browse the parts they are allowed to see without ever touching the original storage. Every hard part of that is infrastructure and permissions, and none of it gets easier because an agent writes the code. A solo editor can absolutely build a personal catalog of their own drives, and that is worth doing. It is not a MAM, and the moment a second person or a second site is involved you are staffing a product, not running a script.
confidence: high
what it is: Backlight's cloud MAM: indexes on-prem, LTO, and cloud storage into one searchable, permissioned media library
Buildability index · an editorial game
- Price 65 $/month · per seat weight: plus 3
- Time not realistically solo weight: minus 3
- Category audio and video no weight
- Moat infrastructure scale · integrations · collaboration weight: minus 4
- Confidence high weight: plus 1
- What you lose 6 items weight: minus 3
- Site iconik.io (si apre in una nuova scheda) no weight
It is not close. The prompt below rebuilds a piece, not the product.
Gioco editoriale: il verdetto dice se un agente può, l’indice se conviene.
What you build
For one person on their own drives: walk the volumes, make ffmpeg proxies, extract metadata, and search it locally. A catalog, not a MAM.
what you need
- ffmpeg
- a machine that can see every volume you want indexed
- SQLite plus FTS5
- storage for proxies
- a lot of patience for the first index
A useful no for post people: the searchable index is the easy half, the storage gateways are the product.
The prompt
The verdict is NOT REALLY, and the prompt stays anyway: it does not replace the app, it rebuilds the part that really is code. The rest is the moat.
Build me a single-user local media catalog for my own drives, the honest
personal floor of iconik. It is for exactly one person; facility-scale asset
management is what iconik is for. Requirements:
- A Node CLI plus a local web app: better-sqlite3 for the index, Express serving on
localhost, plain server-rendered pages.
- `scan <volume>` walks the drive, records path, size, mtime, and volume label, then
runs ffprobe for duration, codec, resolution, frame rate, and embedded timecode.
Re-running it is incremental, keyed on path plus mtime plus size.
- Every video gets a 480p H.264 proxy and a contact sheet of 9 frames written to
~/MediaCatalog/proxies/<hash>/, so I can identify a clip without mounting the drive
it lives on.
- Search across filename, path, codec, and my own notes with SQLite FTS5, plus filters
for duration, resolution, and volume. Results play the proxy inline.
- Offline drives stay in the index and are marked offline when the volume is not
mounted, with the volume label shown so I know which shelf to go to.
- Free-text notes and tags per clip, and a starred collection I can export as a JSON
or CSV shot list.
- Everything is local: no accounts, no cloud, no telemetry. The SQLite file plus the
proxies folder is the entire product and both are backupable.
- Out of scope: multi-user access, permissions, cloud storage gateways, and AI tagging.
Do not build a login system. If a second person needs this, buy iconik.
- README: installing ffmpeg, expected first-scan time for a 20TB volume, and a warning
to run the proxy pass overnight.Curated prompt: written and reviewed by hand for this app. In English on purpose — it is the language coding agents work best in.
What you lose
- storage gateways that index on-prem NAS, LTO, and cloud buckets as one library
- per-user and per-collection permissions with an audit trail
- proxy transcoding that keeps up with petabyte ingest
- Adobe and Resolve panels plus the desktop player
- shared collections and review for clients who never see your storage
- archive and restore lifecycle out to deep cloud storage
Why people still pay
They pay because the alternative is an intern and a spreadsheet, and because the asset you cannot find is functionally deleted. A facility's media outlives its staff, its NLE versions, and usually its storage vendor. Iconik's actual product is being the index that survives all three, with permissions solid enough to put a client in front of and an audit trail solid enough to put in a contract.
moat: Infrastructure scale Integrations Collaboration what a moat is
storage federation/permissions/scale
Who has already built it
Starting from here is still vibecoding: the prompt is for when you want it exactly your way.
- ResourceSpace (opens in a new tab) — Genuine open-source DAM with metadata, collections, and user permissions. Development lives on the project's own repo, the GitHub copy tracks it. (alive)
- Kitsu (opens in a new tab) — Open-source production platform with versioned media, review, and per-project access. Closer to a facility tool than a personal catalog. (alive)
What it costs in a year
65 $/mese 780 $/anno
Listino 65 $ al mese a persona su Iconik. L’anno è dodici mesi pieni, senza sconti annuali.
Do you agree?
The vote balance
Ancora nessun voto: il tuo è il primo.
Nessun voto ancora — il primo pesa.
