About us
A smaller cloud, built by people who spent a decade on the big ones.
Dripspace is developed, owned and operated by Deep Bay Labs AB, a Swedish software company. It exists because putting an app on the internet had quietly become the hardest part of building one.
The short version
- Company
- Deep Bay Labs AB
- Based
- Northern Sweden
- Infrastructure
- EU regions
- Services
- Five, and that is the list
- Support
- Answered by the engineers
Why it exists
Most of the difficulty had nothing to do with the app.
Our founder spent more than ten years on the hyperscalers. Not evaluating them — living with them, every working day, across a long line of projects. The pattern repeated on all of them. Work that should take an afternoon takes a fortnight, and none of the fortnight goes on the product.
You read documentation that covers every parameter and never the intent. You choose between four services that overlap, knowing the choice is hard to undo. You find out that the thing you just created is reachable from the internet, and that locking it down is your job and yours to get right. Networking turns into a side project of subnets, route tables and a diagram nobody ever finishes.
Then someone asks the only question that really gets asked — what will this cost next month — and the honest answer is that you do not know, because it depends on requests, gigabytes, tiers, zones and a page of footnotes.
After enough years of that, the wish gets specific: a platform where you get a website or a web app running quickly, without a decade of background in security, networking and orchestration first. That is the platform we are building.
What wore us down
- Four services that solve one problem, and a week spent choosing between them.
- Documentation that describes the API and never the intent.
- Defaults that are open until you know enough to close them.
- Networking that becomes a project of its own before anything talks to anything.
- An invoice you can only understand once it has arrived.
What we decided
Three decisions. Everything else follows from them.
They are constraints rather than features. Each one rules out things we could otherwise have built, which is the point of writing them down.
A limited set of services
Five services, one per job: frontends, APIs and background work, a database, blob storage, and domains with DNS and SSL. Nothing here solves a problem that something else here already solves, so there is no architecture decision to make before you have written anything.
- If you can name what you are deploying, you know which service it is.
- PostgreSQL is the database. There is no second one to weigh it against.
- The whole platform fits in one nav menu.
Secure by default
A database you create is reachable from your own services over a private network. Public access is a switch you throw deliberately, restricted by IP. Buckets are private until you publish them, and certificates are issued and renewed without being asked. You should never have to wonder whether the thing you made an hour ago is open to the internet.
- Private networking between your services from the first deploy, not as an add-on.
- Credentials arrive in your environment instead of in a setup guide.
- SSL on every domain, issued and renewed, in the price of the zone it covers.
Pricing you can predict
A static site is a flat €5 a month. Anything that runs code is a bundled vCPU and memory size multiplied by the number of instances. Storage is a ceiling you pick, not a meter. Multiply, add, and you have next month's invoice.
- Nothing on the platform is metered per request.
- Network egress and analytics are not billed. DNS and SSL are €1 a zone a month, together.
- No free tier quietly turning into a bill.
The platform
Five services, and that is the whole list.
Written out in full, because a platform you can read in one screen is the thing we were missing.
The trade
A short list of services is a trade, and we made it deliberately.
If you need a managed message broker, a data warehouse or a machine-learning service, we do not have one, and we would rather say so than sell you a way around it. We run .NET, Node.js and Bun. There is no free tier.
Dripspace is smaller than whatever you are leaving, on purpose, and for some workloads that makes it the wrong choice. A short conversation is usually enough to work out which — write to support@dripspace.cloud and you will get a straight answer.
The company
Deep Bay Labs AB
Deep Bay Labs AB is a Swedish software company based in Northern Sweden. It develops, owns and operates Dripspace — there is no parent company above it and nobody between you and the people who run the platform.
Support is answered by the engineers who built the thing, infrastructure runs in EU regions, and the roadmap is short by design. When something gets added, it is because one of the five services needed it, not because the catalogue looked thin.
It should just be simpler, so the time goes into building your app instead of your infrastructure.
See whether the smaller platform fits.
A static site at the flat monthly rate, a domain attached, and nothing else to configure. Find out how much of the old complexity you actually needed.