HostCritiq
Search ⌘K
Menu

Application hosting

Hosting PairDrop

PairDrop moves files and text between devices through a web browser. It works for a quick phone-to-laptop handoff or sharing with another person without setting up a shared drive. Persistent device pairing and temporary rooms help devices find one another beyond a simple local-network session. It is a transfer tool, so keep long-term copies somewhere else.

Requirements last checked against the project's documentation.

Compare server plans Size a server

Understand the setup

Find the software and services needed to run the application.

See requirements

Budget your resources

Plan memory, storage and CPU for the way you will use it.

Open resource planner

Build your shortlist

Compare plans for the starting size, then review the provider and billing terms.

See plans

Must have

Installation requirements

  • A modern browser with the required WebRTC capabilities on participating devices.
  • A compatible Node.js service or container for a self-hosted instance.
  • HTTPS and WebSocket-aware proxying for a public deployment.

Recommended

Planning guidance

Use the resource planner to size a server for your workload.

Choosing a server for PairDrop

Direct peer transfers and relayed transfers have different server bandwidth needs. A TURN relay may carry the file traffic when peers cannot connect directly, so account for that path when setting transfer policies.

Deploy with

Supported paths

  • Docker container
  • Docker Compose
  • Node.js

The host must provide

Runtime

Connections
WebRTC for peer transfers; STUN/TURN configuration depends on the network environment.

Storage

Persistent data

PairDrop is not an archive of transferred files. Recipients need to save completed transfers on their own devices. Preserve server configuration separately if operating your own instance.

Step by step

Plan a PairDrop deployment

  1. Choose the hosting method

    Use the documented container or Node.js setup and keep the internal service behind the intended proxy.

    Official instructions
  2. Configure HTTPS and forwarding

    Follow the project’s reverse-proxy guidance, including client-address forwarding, so unrelated clients are not grouped incorrectly.

    Official instructions
  3. Check both connection paths

    Try local devices and a remote pair. Confirm the relay configuration if the network prevents a direct connection.

    Official instructions

Security

Before you go public

  • Configure the proxy to forward client addresses correctly. Otherwise, unrelated clients can appear to belong to the same discovery group.
  • Treat temporary room codes as access information and verify the recipient before accepting a transfer.

Cost

Beyond the server price

  • A web service and any TURN relay require hosting.
  • Relayed files can generate server traffic charges even when the application itself stores no permanent file library.

Want the full monthly bill? Use the hosting cost calculator. Add storage, backups and other costs to your estimate.