Ubirimi ubirimi
QTR File drop

A file drop. Not a document system in costume.

Quick Transfer is for the 48 MB deck and the dump that should not travel as a mail attachment. Upload. Notify the recipients. They download from a dedicated path. A dashboard of what you sent and what is waiting. When the file belongs on an issue or a page, put it there. This room is the drop.

Start a 15-day trial Why Quick Transfer
In
Upload
Tell
Notify recipients
Out
Download path
Not
An email attachment

Why Quick Transfer

Move large files deliberately without turning email into storage.

Oversized attachments are slow, easy to lose, and difficult to track. Quick Transfer gives occasional file delivery a clear path — upload, notify, download — without pretending a temporary handoff is a document library.

  1. 01
    Keep large payloads out of inboxes

    Upload files once and send recipients a dedicated way to retrieve them.

  2. 02
    See what is still waiting

    Use the transfer dashboard to find what you sent and what remains on the other side.

  3. 03
    Store lasting files in context

    Attach durable artefacts to a Yongo issue or Documentador page; use Quick Transfer for the handoff itself.

QTR-DASH

See what you have sent and what is waiting.

A dashboard, not a buried sent folder. The drop has to be findable or people will go back to mail.

  • Dashboard Transfers you started. What is waiting on the other side. Five routes in the product — small on purpose.

QTR-SEND

Upload. Notify. They fetch.

Put files in a transfer. An email tells the other side the files are ready. Recipients download from a dedicated path — not a 48 MB blob through the inbox.

  • Upload Files into a transfer instead of stuffing them through mail.
  • Notify API mail to the recipient. Silent drops are how files go missing.
  • Download Shared files from a dedicated download path. The recipient does not need a wiki seat to fetch a dump.

QTR-LIMIT

This is a drop. It is not Documentador.

No page tree. No revisions. No issue key. If you need those, you are in the wrong room — and the right rooms are in the same tenant.

  • Weight class Local filesystem upload. Honest about what this is: a drop, not an asset library with history.
  • Graduate Attach to PLATFORM-184 or DOC-12 when the file must live with the work.

Same house

If it needs a history, it is not a drop.

YNG

Yongo

Attachments on PLATFORM-184 when the file is part of the job.

DOC

Documentador

Files on the page when the artefact belongs with the runbook.

CHT

Chat

Tell them it is coming. The bytes do not belong in the channel.

UBI

The suite

Included. No file-drop vendor on the side.

Index

Everything in this drop

  • QTR-1
    Dashboard See what you have sent and what is waiting.
  • QTR-2
    Upload Put files in a transfer instead of stuffing them through mail.
  • QTR-3
    Notify recipients An email tells the other side the files are ready.
  • QTR-4
    Download Recipients fetch shared files from a dedicated download path.

The deal

Quick Transfer is not an add-on SKU.

The drop ships with the suite. Fifteen days, no card on the form.

Create an account See pricing

  • +Upload, notify, download — three steps
  • +A dashboard of sent and waiting
  • +Mail to the recipient when the files are ready
  • +Updates stay free