Give client requirements and handover files a home.

Droplana is a client document portal for developers and small web studios. Each client gets one private portal where you collect requirements, copy and brand assets, and send back specifications and the handover guide. Clients need no account, password or app, and files are hosted in the EU.

The final page copy arrives as a Word file in one email, the logo in another, and a question about the contact form in chat. A client should not have to join your repository or issue tracker to send website copy or review a requirements document. Give those files one place per client and keep the code where it is.

A client portal for developers, from requirements to handover

1. Ask for named client inputs

Request the requirements document, approved page copy, brand assets and a list of hosting contacts in a document checklist. Explain the format and scope you need, such as “final copy for the Home, Services and Contact pages.”

Keep passwords, access tokens and private keys in your approved credential-sharing process. A hosting contact list should identify the service and responsible person, not contain login secrets.

2. Clarify the requirements on the file

Upload a named requirements PDF and ask a precise question in its comments: “In section 2, should the contact form send enquiries to one inbox or two?” Return a new export if the scope changes. Revision numbers are manual; Droplana does not diff requirements or convert comments into development issues.

Actual app, fictional documents. The requirements and handover guide are uploaded files; they are not synced from a repository or generated from a deployment.

3. Hand over the documents the client will use

Upload the handover guide, maintenance responsibilities and any agreed exports. Explain who handles hosting, how to request changes and where authorized access is managed. The client can return to the same portal for a later document exchange.

Try this request: “Please upload the approved copy for [pages], brand assets and the name of your hosting contact. Leave questions on [requirements file]. We will use this portal for documents and keep code, issues and deployment in [existing tools].”

Keep the development workflow in your existing tools

Droplana does not host a Git repository, run builds, deploy code, track issues or sync files. Uploads and comments are the client handoff. If you want to automate your side of it, an automation tool can connect through the MCP server, and signed webhooks report uploads, comments and signatures. If the client has several projects, they share one portal; there are no project-specific permissions.

Start with one requirements file and one handover guide. Use the client instructions to explain access, or compare the exchange with email attachments.

Use the client portal buying guide to compare access, storage and document workflows.

Access, storage and a starting plan

Each client sees their own portal. Authorized business team members share access to the business's clients, files and comments. Files, comments and metadata are stored in Germany; read the security details and DPA against your requirements.

Free covers 3 clients, 2 GB total storage and files up to 100 MB. Solo starts at €19/month plus applicable tax, with unlimited clients, 50 GB storage and a 1 GB file limit. Choose a larger plan for bigger files or more team seats.

Free files are kept for up to 180 days after upload; the client portal does not expire with them. Active paid plans have no automatic age-based file expiry, but chosen expiry dates, deletion and subscription rules still apply.

On Free, each file expires 180 days after upload. Your clients and their access stay active, so you can keep sharing new files. Active paid plans have no plan-imposed retention limit. Expiry settings, deletion and cancellation rules still apply; a persistent portal address does not guarantee permanent file availability. Team sizes include you. No setup fees or automatic overage charges. Prices exclude applicable tax.

Questions before the first handoff