.NET, Node.js and Bun
First-class runtimes.
Build the service the way you already do and hand us the output — a published .NET app, or a bundled Node or Bun service.
APIs & background services
Build it, deploy it, ignore it.
HTTP APIs, workers and cron jobs on .NET, Node.js or Bun. Health-checked rollouts, automatic rollback, and metrics with pre-defined alerts — so there is not much left to watch.
Bundled sizes from €24 per instance per month · requests and data transfer not billed
Key features
What your service runs on.
The parts of a service platform you notice every day: what actually runs your code, what the instance underneath is made of, and whether changing the instance count costs you requests.
AMD EPYC Gen 5
and fast storage behind it
High performance.
High-performance hardware, at a great price. Your apps run on the latest generation of AMD EPYC, with a storage solution built to match it.
No downtime
to add, remove or resize
Scale without a maintenance window.
Change the instance count or move up a size and the rollout is gradual. A new instance takes traffic only once it passes its health check, and a rollout that fails reverses itself.
What you get
Everything around your service, already wired up.
Health-checked deploys, three ways to scale, per-instance metrics with alerts, and connection strings that stay current.
Deploys in seconds
Under 60 seconds from upload to application start-up. You upload a built artifact, so there is nothing of yours to compile and no build queue to wait behind.
Scaling
Change the instance count by hand, on a schedule, or automatically from metrics you pick — CPU, memory or request rate. All three use the same health-checked rollout.
Workers and cron
Background services and scheduled jobs use the same runtimes, the same deploy paths and the same bundled sizes.
Metrics without setup
CPU, memory, request rate, error rate and latency per instance, retained 90 days, with alerts already set and your own on top.
Service connections
Connection strings and service URLs arrive as environment secrets, and keep themselves up-to-date.
Sizes
Compute, Standard and Memory — per instance, per month.
Three ratios of memory to vCPU over one ladder. Pick the ratio your workload wants, then the rung, then how many instances run. HTTP APIs, background workers and cron jobs all price the same way.
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 |
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
dashboard · upload
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
Questions
Questions about running a service.
.NET, Node.js and Bun. You build the service yourself and upload the artifact — a published .NET app, or a bundled Node or Bun service — and we run it on the size you pick. Background workers and cron jobs use the same runtimes and the same bundled sizes.
Ship an API next to your frontend.
Same project, same dashboard, same deploy paths — and a private network between them.