- Free allowance
- No free tier. Three resource profiles: DD1 Sulina 1 TB at EUR 4.99/month, DD5 Sf.
- Verdict
- ★ qualifiesusable as stated; the read path was probed
- Cost
- USD 3.36/TB-monthparsed from the record, in USD
- Identity
- cardcard required, no phone
- Binding limit
- request-rate50, 100 or 200 concurrent connections depending on the profile
- Evidence
- documented4 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-11-13checked 2026-10-22 (live); stale on 2026-11-13
| Free tier | No free tier. Three resource profiles: DD1 Sulina 1 TB at EUR 4.99/month, DD5 Sf. Gheorghe 5 TB at EUR 14.99, DD10 Chilia 10 TB at EUR 29.99 unit TiB; metered on stored-bytes |
|---|
| Price | EUR 4.99/TB/month at 1 TB falling to EUR 3.00/TB/month at 10 TB, read 2026-10-22 |
|---|
| Limits | - request-rate (binding) 50, 100 or 200 concurrent connections depending on the profile source
|
|---|
| Binding | request-rate The only published numbers that can bind are the concurrent-connection caps, because the traffic terms are unstated and the per-file cap is unstated. 50 connections on the 1 TB profile is ample for a copy job and thin for a serving path. |
|---|
| Identity | card a DanubeData account and a payment method. The docs do not describe the signup gate |
|---|
| Egress | No egress price and no traffic quota are published anywhere in the vendor documentation, so this field is false by the schema's own definition (false when traffic out has neither a price nor a quota) and not because the vendor granted anything. The instance is S3-backed and DanubeData sells object storage separately, so a traffic line may exist behind the Nextcloud facade and the docs do not say |
|---|
| Per-object cap | Not published as a per-file cap. The published per-profile numbers are subdomains and concurrent connections: 3 and 50, 7 and 100, 10 and 200 |
|---|
| Retention | Until deleted. The instance lifecycle is Pending, Provisioning, Running, Error, Destroying, with redeploy from Error. No retention clock is documented |
|---|
| Interface | webdav, rest, s3 |
|---|
| Tooling | a WebDAV endpoint on every profile, the Nextcloud clients, and one-scan QR setup for iOS and Android. S3-backed means the same bytes are in an object store, so an S3 tool may reach them without a second copy, but the docs do not publish the bucket |
|---|
| Composes with | S3-backed Nextcloud is the cleanest architecture of the four: the bytes live in an object store behind a Nextcloud facade, so either access path should reach the same copy. Ten subdomains per instance is an unusual sharding affordance and it is the only reseller here that offers it |
|---|
| Reliability | Falkenstein, Germany, the same data centre as Hetzner, so the failure domain is shared with the Hetzner option. Dedicated CPU and memory per instance, automatic TLS renewal. The product is young and the documentation is thin: the WebDAV page returned 404 when requested |
|---|
| Notes | The cheapest 10 TB managed Nextcloud of the five at EUR 3.00/TB/month, and the only one whose storage is documented as an object store behind the Nextcloud facade. Two things are unverified that a buyer needs: the traffic terms, and whether the S3 backend is reachable with credentials the customer holds. The docs describe the second as a property of the product and publish no endpoint. |
|---|
| Evidence note | documented Prices and profile numbers are from the vendor's own table read. documented at best: the traffic terms and the per-file cap are published nowhere, so the egress field carries a null metered rather than a guess. |
|---|
| Parsed numbers | - has-free-tier 0
- price-per-tb EUR 3 TB / month
|
|---|