[verdict][generated prompt][source: tresorit.com]
Can I vibecode Tresorit?
// the value is the network, the data or the infrastructure
A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Tresorit, sync a small encrypted folder set to user-owned storage with secure links. The hard boundary is audited encryption, cross-platform clients, sharing policy, recovery, and compliance, plus reliability, durability, and cross-device sync.
confidence: high
what it is: Sync a small encrypted folder set to user-owned storage with secure links
Buildability index · an editorial game
- Price 13.99 $/month weight: plus 2
- Time closest consolation build: one sitting weight: minus 1
- Category cloud storage no weight
- Moat infrastructure scale · brand and trust · compliance and regulation weight: minus 5
- Confidence high weight: plus 1
- What you lose 5 items weight: minus 2
- Site tresorit.com (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
Sync and back up a small folder set, encrypt files client-side, share secure links, track versions, and restore them from user-owned object storage.
what you need
- user-owned server or S3-compatible bucket
- PostgreSQL
- MinIO or object storage
- desktop filesystem permissions
- backup key stored offline
Editorial comparison targets the Personal plan and a single-user encrypted backup DIY substitute. Recheck price before merge.
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 a closest honest personal substitute for Tresorit in an empty repository.
Use Next.js 15, TypeScript, PostgreSQL, MinIO, and a Tauri 2 sync client; do not offer alternative stacks.
The core loop is: sync and back up a small folder set, encrypt files client-side, share secure links, track versions, and restore them from user-owned object storage.
Make the first run work locally with one documented command.
Store all user data locally by default and make export straightforward.
Put secrets in .env, ship .env.example, and never commit credentials.
Build a desktop client that watches explicitly selected folders and ignores configured patterns.
Chunk, hash, compress, and encrypt files locally before uploading to the configured object store.
Store version metadata, tombstones, device identifiers, and integrity checks in PostgreSQL.
Provide upload and restore queues with pause, retry, bandwidth limits, and resumable transfers.
Add file history, point-in-time restore, key export, storage usage, and scheduled restore tests.
Document the failure model and make clear that one server is not a complete backup strategy.
Include clear empty, loading, success, and recoverable error states.
Add input validation, safe filenames, and graceful handling of unavailable APIs.
Write focused tests for the core transformation and one end-to-end happy path.
Create a README with setup, architecture, permissions, data location, and backup steps.
Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
Do not claim to reproduce proprietary data, network liquidity, regulated access, or frontier infrastructure.
Deliberately leave out multi-provider consumer sync at global scale.
Deliberately leave out guaranteed durability or ransomware recovery.
Deliberately leave out shared-drive administration, mobile apps, and enterprise compliance.
Finish by running the tests and listing the exact commands used.Prompt generated from the data on this page, not reviewed by hand yet. In English on purpose — it is the language coding agents work best in.
What you lose
- audited encryption, cross-platform clients, sharing policy, recovery, and compliance
- global sync network
- battle-tested conflict resolution
- ransomware recovery guarantees
- mobile clients and support
Why people still pay
People still pay for Tresorit because storage subscriptions sell confidence that files will still exist after a lost device, bad sync, or provider incident. The recurring cost buys chunking, encryption, conflict detection, versions, garbage collection, bandwidth, restore drills, monitoring, billing, and disaster recovery, not just the visible interface.
moat: Infrastructure scale Brand and trust Compliance and regulation what a moat is
reliability, durability, and cross-device sync
Free alternatives
Not in the mood to build it? These already exist, they are free or open source, and we checked them one by one.
Rejected (2) — and why
- Nextcloud Files (si apre in una nuova scheda) — Secure links and versions, yes; Tresorit-style end-to-end encrypted sharing, no.
- Syncthing (si apre in una nuova scheda) — Encrypted folder replication is real; secure external links are simply not part of the product.
Who has already built it
Starting from here is still vibecoding: the prompt is for when you want it exactly your way.
- Nextcloud (opens in a new tab) — Mature open-source file sync and collaboration server.
Do you agree?
The vote balance
Ancora nessun voto: il tuo è il primo.
Nessun voto ancora — il primo pesa.
