Frontend hosting
From build output to live site in one step.
Upload the folder, run the CLI, or let your CI post it. You get a URL, a certificate when you attach a domain, and a numbered release you can roll back in one click. Static or server-rendered, the way in is the same.
Static from €5 per site per month · SSR on bundled sizes · data transfer not billed either way
Two kinds of frontend
Does your code run in the browser, or on a server?
That one question decides how a frontend is priced. If the build output is files the browser executes, it is static. If a process has to run your code to answer a request, it is dynamic.
Static
HTML, CSS and JavaScript that runs in the visitor’s browser
- Typically
- Plain HTML sites, React/Vue/Svelte SPAs, Astro and Next in static export mode, docs and marketing sites
- How it is served
- Served as files by the service — no process of ours runs your code
Flat €5 per site per month
Dynamic (SSR)
Your code executes on a server for each request
- Typically
- Next, Nuxt, SvelteKit, Remix and Astro in SSR mode — anything rendering per request or per user
- How it is served
- Runs as a sized instance, with health checks and rolling deploys
A bundled vCPU + memory size × instances
Custom domains, wildcard SSL and data transfer work the same way on both. The split changes how the compute is billed, and how metrics reach you — automatically for SSR, through the Metric SDK for static.
What you get
Everything a frontend needs, whichever kind it is.
There is no add-on list. Data transfer, a subdomain with its certificate and versioned releases come with static sites and server-rendered ones alike.
Served as files, not processes
Assets are fingerprinted on promote, so a release never serves a stale one. Cold starts do not exist for a static file.
Data transfer, not billed
In or out, including every asset the site serves. A fair transfer allowance applies, and we get in touch rather than charging.
Managed certificates
Issued when you attach a domain and renewed for you, covering the apex and every subdomain under it.
Immutable releases
Every deploy is a numbered release, and promote is atomic — a half-finished upload never reaches a visitor.
Twenty releases kept
The last 20 deploys stay online, so rolling back is picking one from the list rather than deploying again.
Ways to ship
Several ways to get your code online.
Pick whichever fits how you work. Every path ends in the same place: a live URL with SSL and instant rollback.
Drag in a build folder
Zip your dist/ and drop it on the dashboard. Dripspace unpacks it, fingerprints the assets and serves them. Every upload is a versioned release you can roll back to.
- Nothing to install, no build step on our side
- SPA fallback and redirects from a config file
- Keeps the last 20 releases
dropped dist.zip · 4.2 MB
unpacking 128 files · 4.2 MB
fingerprinting assets
uploading to eu-north-1
release r-1042 promoted
live https://acme-shop.dripspace.app
Sizes
Compute, Standard and Memory — per instance, per month.
Sizes apply to server-rendered frontends only — a static site is the flat €5 per site per month whatever the traffic. For SSR, pick the ratio of memory to vCPU your renderer wants, then the rung, then how many instances run.
Compute
1:2 & 1:3 vCPU:RAMThe least memory per core. For work that is bound by the processor.
| vCPU | Memory | Per instance / mo |
|---|---|---|
| 1 | 2 GB | €24 |
| 2 | 4 GB | €48 |
| 4 | 8 GB | €96 |
| 8 | 16 GB | €192 |
| 16 | 32 GB | €384 |
| 32 | 64 GB | €768 |
| 64 | 192 GB | €1,920 |
Standard
1:4 vCPU:RAMThe middle ratio, and the right starting point if you are unsure.
| vCPU | Memory | Per instance / mo |
|---|---|---|
| 1 | 4 GB | €36 |
| 2 | 8 GB | €72 |
| 4 | 16 GB | €144 |
| 8 | 32 GB | €288 |
| 16 | 64 GB | €576 |
| 32 | 128 GB | €1,152 |
| 64 | 256 GB | €2,304 |
Memory
1:8 vCPU:RAMThe most memory per core. For anything holding a large working set.
| vCPU | Memory | Per instance / mo |
|---|---|---|
| 1 | 8 GB | €60 |
| 2 | 16 GB | €120 |
| 4 | 32 GB | €240 |
| 8 | 64 GB | €480 |
| 16 | 128 GB | €960 |
| 32 | 256 GB | €1,920 |
| 64 | 512 GB | €3,840 |
Questions
Questions about hosting a frontend.
If the build output is files the browser executes — plain HTML, a single-page app, or a framework building to static output — it is static, and it is the flat monthly rate whatever the traffic. If a process has to run your code to answer a request, it is server-rendered, and it runs on a bundled size the way an API does. The deploy paths, domains and certificates are the same either way.
Put a site online when we open.
Drag in a zip or connect a repo. You can attach a domain straight after.