Cloud storage decision

Tarkle

A competent technical user can build a useful self‑hosted file sharing + client portal using existing open‑source projects and cloud services, but replicating Tarkle's full polished, white‑label product (crew features, AI Assist, and integrated multi‑app UX) would be time‑consuming—pay if you need the complete product.

Visit website
You pay

$29/mo

$348/yr

Read off the official pricing page.

You’d pay instead

$100one-off120 h to build

$20/mo6 h/mo upkeep

On cash alone, building overtakes the subscription at 1 seat.

Open-source builds that already do this

Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All Tarkle alternatives, with the arithmetic →

What a replacement has to do

  • Allow users to upload large files, generate a branded shareable download link and a client portal where recipients can view/download and (optionally) purchase assets.

What it still won’t have

  • Turnkey white‑label polish and integrated UI across Send/Portal/Crew
  • Invite‑only contractor portal features (Crew) and contractor payroll/workflow
  • Built, tested branded download templates and built‑in backup/recovery policies
  • Integrated AI Assist features available on Tarkle Pro
  • SLAs, uptime, and ongoing product support

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

Keep paying

Paying is—cheaper in year one.

On cash alone, building overtakes the subscription at 1 seat.

Paid seatsseats

Money you would actually spend

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

Time you would spend

—

—

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a self-hosted minimal white‑label file sharing + client portal using Next.js for the frontend, a Node.js (Express) API, Postgres for metadata, and S3-compatible object storage (MinIO or AWS S3) for files. Core features in scope: resumable direct-to-S3 uploads, per-transfer metadata (title, description, expiry), branded download pages (logo, colors), expiring & one-time links, password protection, passwordless client email links, a simple client portal showing files shared with a client, Stripe integration for paid downloads, background job worker for cleanup and 90-day soft-deletes. Out of scope: contractor portal (Crew), multi-tenant billing dashboards, built-in AI Assist, advanced enterprise RBAC. Require TLS via Cloudflare for custom domains, proper error handling (upload failures, signed URL expiry), API and end-to-end tests, and deployment scripts for Docker Compose and a recommended cloud (AWS) setup.
How we checked5 sources · 3/3 runs agreed · evidence score 67

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 5 cited sources+3
  • Price verified on pricing page+3
  • 3/3 assessment runs agreed+4
  • Evidence score67

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.

How scoring works →

Cited sources · 5

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ Price read off the page✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded