FREELANCER DELIVERY
Static hosting for freelancers who deliver client work
Static hosting for freelancers who need a finished client site, a proposal or a prototype behind a clean link without turning delivery into a deployment project. Upload the built files, send one address, and replace the build in place as the work moves.
Free plan, free SSL, no credit card.
- 96
- file types, so the deliverable and the invoice can share a home
- 15
- republishes a day, which outlasts most review rounds
- $15
- a month is where the client's own domain starts
- 1
- free site to try the workflow before you bill anyone
How it works
Three steps, start to live link
-
Upload the deliverable
Drop the built site, the HTML page, the PDF proposal or the design export. It is served exactly as you prepared it, with nothing reformatted.
-
Send one address
The client opens a link, not an archive. No download, no unzipping and no instructions about opening a local file in a browser.
-
Revise without resending
Publish the new build to the same site. The address in the email thread, the invoice and the printed QR code keeps pointing at the current work.
The plain answer
What freelancers actually need to hand over
Not a hosting account. The deliverable is usually a built static site, a PDF proposal or scope document, a set of design exports, or a prototype that has to be seen in a browser rather than described. What a freelancer needs is for each of those to become a link that a non-technical client can open on a phone, and that stays correct after the next revision.
The two common alternatives both leak time. Sending a ZIP moves the work of opening it onto the client, who then opens index.html from their downloads folder, sees a page with no styling because the browser blocked something, and replies that the site is broken. Standing up a real host for a project that has not been paid for yet means a server, a certificate and a DNS record you will have to remember to tear down.
A publishing step sits between those. Upload, share, replace. When the project is signed off and the client wants it on their own domain, the same site moves there from Pro, and the DNS guides are short enough to paste into an email. If the review needs to stay private, password protection from Starter is checked at the edge, before any file is served.
Who it is for
The people who reach for this
-
Design freelancers
Coded comps, style tiles and prototypes, live at an address instead of flattened into a slide.
-
Developer freelancers
A built site online for review before any decision has been made about where it will finally live.
-
Marketing consultants
A campaign page or a report that has to be shareable today, without the client's IT queue.
-
Small agencies
Several client previews running at once, each on its own address, each replaceable in place.
In detail
What you actually get
One address that survives the project
The link goes in a proposal, a contract, a chat thread and eventually an invoice. It has to still be right in three weeks, after four revisions.
- Publishing a new build swaps what the address serves; the address itself never moves.
- From Pro, returning to the version the client approved is one click.
- Pick the subdomain, so the link reads like the project rather than like a hash.
Private while it is unfinished
Work in progress should not be indexable, quotable or findable. Two separate controls cover that.
- Password protection from Starter, enforced at the edge before any file is served, so assets are covered as well as pages.
- Free sites are served noindex, so nothing half-finished turns up in a search result.
- Expiring links from Starter: set a preview to lapse after six hours, a day, a week, a month or a date you pick.
Hand it over cleanly at the end
The awkward part of freelance delivery is the moment the client takes ownership. Moving the same site to their domain is the least disruptive version of that.
- Connect a domain the client owns from Pro, $15 a month, with certificates handled.
- Registrar-specific DNS guides with the exact records to add.
- Visitor analytics from Pro, so "is anyone using it" has an answer.
The paperwork lives in the same place
A client project is rarely only a website. Proposals, specs, exports and slide decks all publish the same way and get the same kind of link.
- PDFs open in the browser rather than downloading, so a proposal is one tap on a phone.
- Images, video, audio, spreadsheets and Office documents are all handled, 96 extensions in total.
- Related: turning a PDF into a link.
No card required
What the free plan includes
Enough to run one client preview end to end before you decide whether this belongs in your workflow.
- 1 live site on a real free plan, not a trial of a paid one, and no card to start.
- Up to 25 MB per upload and 25 MB of storage across the account.
- 5,000 visits and 5 GB of traffic a month.
- HTTPS with a real certificate, issued and renewed for you.
- Up to 15 publishes a day, so you can iterate without asking permission.
- The deploy-time security check, which reads what you published and warns about a stray .env file, a .git folder, a private key or an API key left in your JavaScript.
- A small Droply badge in the corner of the page. Removing it starts on Starter.
- Free sites are served noindex, so search engines do not list them. Search visibility starts on Starter.
Droply vs Tiiny Host
How this compares for client delivery
Tiiny Host is used for the same job by a lot of freelancers and does it well. These rows are the ones that come up during an actual project rather than during signup.
| Droply | Tiiny Host | |
|---|---|---|
| Free plan | 1 site, 25 MB storage, 5,000 visits and 5 GB a month, no card. | 1 site, 5,000 visits and 5 GB bandwidth a month, 3 MB per project (0.5 MB for a PDF). |
| Custom domain | From Pro, $15 a month. | From Solo, $18 a month or $13 billed annually, up to 5 domains per account. |
| Password protection | From Starter, checked at the edge before any file is served. | From Solo, $18 a month or $13 billed annually. |
| Expiring links | From Starter: 6 hours, a day, a week, a month or a date you pick. | Not documented as a feature in the help center. |
| Rollback to an approved version | From Pro, in one click. | No self-serve rollback is documented. A deleted link can be restored by contacting support. |
| Security check on deploy | Every publish, on every plan, including free. | Not offered. |
| Entry paid price | $5 a month for Starter. | $9 a month for Tiny, or $5 billed annually. |
Tiiny Host figures come from its own help center, checked 8 September 2026: the pricing-plans article (updated 1 September 2026), the visitor, upload and bandwidth limits article (updated 2 September 2026), the free-plan link duration article (updated 21 August 2026), the password-protection article (updated 3 September 2026) and the custom-domains guide (updated 7 September 2026). Product plans can change.
When Droply is the wrong choice
Client work often needs more than a place to put files. Be honest with yourself about which of these the project is.
- The client needs a CMS so they can edit copy after you leave. Hand over a hosted WordPress or a headless setup instead; a static upload leaves them dependent on you for every word change.
- The deliverable is a web application with accounts and stored data. That is not a static site and nothing here will make it one.
- You need an audit trail of who approved which version, with comments attached. This keeps versions, not conversations.
- You need a database, a login system, or code that runs on the server. Droply serves files; it does not execute your application.
- You want a build to run on every push to a repository. Droply has no Git integration and no CI: you build locally and upload the result.
- You are running WordPress or another PHP application. A static export of it can be hosted here, but the application itself cannot.