Gokapi Hosting

How Gokapi works

Gokapi lets authenticated users upload a file and define when its link expires, either after a number of downloads or a number of days. Recipients can open the generated link without an uploader account, subject to any password applied to the download. File Requests can create controlled links through which external users submit files to the server.

The application also documents multi-user permissions, API keys, deduplication, local or supported object storage, and optional client-side end-to-end encryption. Password protection and encryption are different: the official usage guide notes that a download password alone does not encrypt the file on storage. Users must select and verify the protection mode appropriate to the data.

Key Gokapi features

Expiration removes files according to the configured day or download threshold, making Gokapi useful for temporary exchange. It is not a permanent archive, team drive, versioned document workspace, or legal retention system. Administrators should define sensible limits and keep an independent source copy until the recipient confirms successful receipt.

Uploads consume memory in chunks, and concurrent uploads or downloads can increase both processing and network use. Storage capacity remains the primary plan constraint. The hosted package does not include an S3 or Backblaze account, malware scanning, recipient identity verification, content classification, or a delivery compliance certificate.

Gokapi vs WeTransfer

Gokapi stores transfer data on the customer-controlled installation or on an external object store the customer configures, with local user and API-key administration. WeTransfer is a provider-operated service with account plans, transfer quotas, managed delivery pages, optional branding, expiration controls, password protection, and commercial access features.

WeTransfer may suit users who want a maintained public transfer service, high commercial allowances, recipient previews, and minimal server administration. Gokapi is more appropriate when an organisation wants the transfer application on its own domain and storage, accepts operational responsibility, and needs configurable expiry or download limits without a permanent drive.

Who uses Gokapi

Consultants deliver reports, support teams exchange diagnostic archives, creative groups send approved media, and businesses collect files through temporary request links. Multi-user controls can separate upload permissions among staff while keeping anonymous visitors limited to downloads or authorised requests.

Gokapi should not be used as the only copy of important files. Sensitive transfers require a considered encryption choice, verified recipient communication, lawful content, independent malware controls where necessary, and a clear retention policy beyond the application’s automatic deletion rules.

Self-hosting Gokapi: requirements and cost

Gokapi usage is driven by uploaded file size, retained transfers, concurrent uploads, download traffic, chunk processing, file requests, deduplication, encryption, API use, and user activity. Gokapi is mapped without PostgreSQL or MariaDB. Storage is the practical limit because transfer files stay on local or customer-configured object storage until their expiry conditions are met. Gokapi is marked storage-driven in the plan mapping, so 50 GB on Plan 3 is a realistic starting point and 100 GB on Plan 4 provides more room for a large working set.

On AvaHost, Gokapi uses Plan 1 at €2. The hosted Gokapi package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. The package includes local application storage, not an external S3 or Backblaze account, malware scanning, recipient identity checks, legal retention, or delivery certification. Configure expiry carefully, choose encryption deliberately, protect administrator accounts, and keep independent source copies until transfer completion is confirmed.