One platform for both websites and web apps.
Frontend, API, database, storage and domains — the five things it takes to run a site or a web app. Simple pricing with zero-cost egress, so next month's invoice is one you can work out before you deploy.
- No data-transfer fees
- DNS & SSL, €1 a zone
- Analytics included
Why it exists
Most of the difficulty had nothing to do with the app.
Dripspace was built by people who spent a decade on the big clouds, and it is shaped by the parts of that decade that were not worth the time. Each row below is a thing we stopped doing.
What it usually takes
What it takes here
Usually Four services that solve one problem, and a week spent choosing between them.
Here Five services, one per job. If you can name what you are deploying, you know which one it is.
Usually Networking that becomes a project of its own before anything talks to anything.
Here Services in a project reach each other over a private network from the first deploy, with credentials already in the environment.
Usually Defaults that are open until you know enough to close them.
Here Databases private, buckets private, certificates issued. The switches that open things are the ones you throw yourself.
Usually Documentation that describes the API and never the intent.
Here Support answered by the engineers who built the thing, rather than by someone reading you the page you just read.
Usually An invoice you can only understand once it has arrived.
Here A flat rate, a size times a count, and a ceiling you picked. Three multiplications, all of them done before you deploy.
Three decisions, and everything else follows from them.
The platform
Smart services — frontend, API, database, storage and domain.
Private networking between services, credentials already in your environment, certificates already issued. No integration project, no glue to maintain.
Frontend
Static sites, single-page apps and server-rendered frontends. Push, get a URL, roll back in one click.
Attach a domain and the certificate is issued for you.
APIs & services
HTTP APIs & long-running background workers. Health-checked, rolled out without downtime, restarted when they fall over.
Reaches your database over a private network, never the public internet.
Database
Managed PostgreSQL with 15-day point-in-time restore included.
Attach it and the connection string appears in your service.
Blob storage
Buckets for uploads and assets, reachable from your services over the project network.
Nothing in a bucket is public until you publish it.
Domains, DNS & SSL
Register a domain or bring your own, then run the whole zone from here.
Certificates issue on attach and renew without you noticing.
Secure by default
Private on the way in, not after you have read the guide.
You should never have to wonder whether the thing you made an hour ago is open to the internet. A database you create answers your own services and nothing else; a bucket holds nothing the public can read until you publish it.
- Databases are reachable from your services over the private network. Public access is a switch you throw deliberately, restricted by IP.
- Buckets are private until you publish. Nothing becomes world-readable by accident.
- Connection strings and service URLs arrive as environment secrets, and keep themselves up to date. No credentials copied between dashboards.
- Certificates are issued when you attach a domain and renewed without being asked, covering the apex and every subdomain under it.
The first five minutes
From an empty project to your own domain, in order.
There is no architecture decision to make before you have written anything, and no step here that is a prerequisite project of its own.
- 01
Make a project, pick a region
EU regions are the default. Everything in the project stays in the one you choose — frontend, API, database and buckets alike.
- 02
Put something in it
Drag in a zip, connect the repo, run the CLI, call the API, or hand it to an agent. Six ways in, the same versioned release at the end of each.
The six ways - 03
It answers on a URL
Every deploy gets a dripspace.app address with a certificate already on it, at no cost, from the first push.
- 04
Attach your own domain
Register one here or point a record at us from wherever it lives. The wildcard certificate issues on attach and renews without you noticing.
More - 05
Attach a database or a bucket
The connection string appears in your service’s environment, over the private network. There is nothing to wire up and nothing to copy.
More
No free tier to convert out of, and nothing metered per request.
Managed PostgreSQL
The database you already know, with the operations already done.
One database, because a second one would only be a decision to make. Resizing is a setting rather than a migration: move up or down the ladder, turn the standby on, change the storage ceiling on its own — each takes effect immediately and is billed from the moment you make it.
- 15 days
- Point-in-time restore, includedWind a server back to any minute in the last 15 days — at every size and every ceiling, not an upgrade and not an add-on.
- A switch
- High availability when you want itTurn HA on and a standby runs at the same size, kept in sync, taking over on its own. It doubles that server and leaves its storage alone.
- Private
- Reachable from your services onlyOn the project network by default. Public access is opt-in and restricted by IP, and the connection string arrives in your service’s environment.
- Postgres 17
- Plain PostgreSQL, not a forkpgvector, PostGIS, pg_stat_statements and the rest of the common set. Your drivers, migration tools and clients connect unchanged.
$ psql "$DATABASE_URL"
psql (17) · SSL connection
acme-db=> \dx
pgvectorvector types and indexes
postgisgeometry and geography
pg_stat_statementsquery execution stats
uuid-osspuuid generation
4 extensions enabled
ready for connections
acme-db=>
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
Bring what you have
Nothing here asks you to rebuild it first.
- Your build output
- Whatever your bundler writes. Zip the folder and drop it in, or connect the repo and let a push do it.
- A built service
- A published .NET app, or a bundled Node or Bun service. You build it the way you already do; nothing of ours compiles your code.
- Your PostgreSQL
- Plain PostgreSQL, not a fork, so the drivers, migration tools and clients you have connect to it unchanged.
- Objects in another cloud
- A managed job copies them across from Azure, AWS or GCP, then keeps the two ends in step until you switch over.
Domains move too — transfer one in and we host the zone, or leave it where it is and point a record at us. Certificates are issued either way, and transfers out are never blocked or charged.
Metrics & analytics
Traffic and resource numbers, on every project, at no extra cost.
Anything that runs code — SSR frontends, APIs, workers, databases and buckets — is measured at the platform level from its first deploy, with nothing to install and some alerts already set. Static sites and SPAs are served as files rather than run, so their numbers come from the Metric SDK you add to the frontend.
- Automatic for every service that runs code, at no extra cost
- Static sites and SPAs report through the Metric SDK
- Retained for 90 days, exportable as CSV or over the API
- Alerts on error rate, latency and saturation already set, plus your own
Page views
128 402
- Top page
- /pricing
- Top referrer
- news.ycombinator
- Median TTFB
- 38 ms
- Egress billed
- €0.00
Data transfer
€0.00
on every invoice, at every size.
There is no egress line. Not on the frontend that serves your assets, not on the API answering them, and not on the bucket the downloads come out of — because transfer is never billed here, not because something caches it.
A fair transfer allowance applies to each service, and the larger the size you run, the larger the allowance. Nothing is throttled or charged automatically if you pass it: we get in touch and work it out with you.
- Inbound
- Outbound
- Blob downloads
- Between your services
Domains, DNS & SSL
Buy it, point it, secure it. In one place.
Register a new domain or transfer one in, then manage its DNS from the same dashboard as your deployments. A hosted zone is €1 a month, wildcard certificate in the price.
- 01
Buy it here or bring your own
Search and register a domain in the dashboard at a competitive price, or transfer one in. Transfers out are always allowed, never charged.
- 02
Manage the whole zone
A, AAAA, CNAME, MX, TXT, CAA, SRV and ALIAS at the apex — edited next to the deployment they point at. €1 a month per zone, however many records you put in it.
- 03
Certificates renew themselves
Wildcard SSL covering your apex and every subdomain. Issued on attach, renewed without you noticing, and never a line of its own — the zone price covers it.
Pricing
Simple enough to work out in your head.
Three rules cover the whole platform. Nothing is metered per request, data transfer is not billed, and no line on your invoice depends on how popular you were last month.
A static site is a flat rate
One price per site per month, whether it serves a hundred visitors or a million.
€5 / site / month
Anything that runs code is a size × instances
Pick a bundled vCPU and memory size — Compute, Standard or Memory — and pick how many run. That multiplication is the price.
from €24 / instance / month
Storage is a ceiling you choose
You buy the ceiling, not the bytes used, so an upload spike cannot move your invoice. Buckets and database storage alike come in fixed blocks, every block the same price.
€1 / 25 GB / month
What that actually costs
Three real setups, priced end to end. No traffic estimate needed.
A marketing site
A landing page, docs site or portfolio on your own domain.
- Static siteflat monthly rate
- €5
Early-stage SaaS
A frontend, an API, a database and somewhere to put uploads.
- Static frontendflat rate
- €5
- API2 vCPU · 4 GB × 1
- €48
- Database1 vCPU · 2 GB · 10 GB storage
- €43
- Blob storage25 GB quota
- €1
Production app
Server-rendered frontend, redundant API, HA database, media library.
- SSR frontend1 vCPU · 4 GB × 2
- €72
- API4 vCPU · 8 GB × 2
- €192
- 3 Background services2 vCPU · 4 GB × 1
- €48
- Database2 vCPU · 16 GB × 2 (HA) · 20 GB storage
- €412
- Blob storage1 TB quota
- €40
Included at €0
On every plan, at every size — not a tier you upgrade into.
- Data transfer
- In and out, including blob downloads. There is no data-transfer line on the invoice.
- Point-in-time restore
- Rewind a database server to any minute in the last 15 days, at every size and on no plan tier. Scheduled full backups are a paid add-on.
- Analytics & metrics
- Automatic on every service that runs code, and on static sites through the Metric SDK. Retained 90 days.
- A subdomain per service
- Every deploy gets a dripspace.app address with a certificate on it, from the first push.
Work it out now
The invoice, before you deploy anything.
Four rows, because that is the whole rate card. Nothing below is metered, so the figure you land on is the figure that arrives.
A flat €5 a month, whether it serves a hundred visitors or a million.
Every month
€164
- Frontend
- €5
- API or worker
- €24
- Database
- €135
- Transfer and analytics
- €0
Domains are extra and priced by the registry. A hosted DNS zone, wildcard certificate included, is charged per zone.
The full estimatorQuestions
The things people ask first.
A static frontend is files the browser executes: plain sites, single-page apps, and frameworks building to static output. Nothing of ours runs your code per request, so it is the flat monthly rate. A dynamic frontend is server-rendered — Next, Nuxt, SvelteKit or Astro in SSR mode — where a process runs your code to answer each request. That is real compute, so it is priced on the same bundled vCPU and memory sizes as an API. Data transfer comes with both, and domains work the same way on either. Metrics differ: a server-rendered frontend is measured for you, while a static one reports through the Metric SDK.
We are letting people on a few at a time.
The first accounts are worth looking after properly, and we would rather do that than open the doors and watch. Everything on this site is what we are building and what it will cost. Leave an email and we will write when there is an account waiting for you.
- Regions
- EU by default, one per project
- Your data
- Stays in the region you picked
- Operated by
- Deep Bay Labs AB, Northern Sweden
- Support
- Answered by the engineers
Have a longer look
The doors are not open yet.
Leave an email and say what you would put on it. We will write when there is an account waiting — we are letting people on a few at a time.