Account holder confirmed 2026-08-15 that Host Europe offers no fully managed S3 and no API to provision storage. That is a blocking answer, which T02's acceptance criterion permits alongside evidence and unknown. - host-europe-cloud-storage: blocked-account-confirmation -> not-offered, with provenance recorded as account-holder knowledge rather than vendor-written confirmation. The 2020 published specification describes nothing currently orderable. - T02 done: no acceptance requirement is blank for any provider. - T01 done: the A/B/C comparison was never missing a leg. With no managed S3 to price, Host Europe's real form is self-managed Garage on their VMs, already priced from the public catalogue at EUR 335.77/month for 3 nodes — roughly 5x the chosen Scaleway option, and it fails closed at month 12 when base demand (458 GB) exceeds the 400 GB usable capacity. The missing evidence would not have changed the decision; it strengthens it. The 2026-08-10 due-diligence matrix and the approved optimization case are deliberately not rewritten. A decision record documents what was known when the decision was made; the new evidence document is the supersession. "No provisioning API" is filed as a procurement-facility fact: any Host Europe resource is manually provisioned, which is RESOURCE-WP-0005 and RAIL-HO-WP-0008 territory, not a pricing question. RESOURCE-WP-0002 is finished: all seven tasks done. 136 tests pass. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
4 KiB
Host Europe evidence gap — resolved 2026-08-15
The answer
Account-holder statement, 2026-08-15:
Host Europe does not support fully managed S3, and even less so an API to provision storage.
This closes the gap that RESOURCE-WP-0002-T01 and T02 had been holding open
since 2026-08-10. It is a blocking answer, which the T02 acceptance
criterion explicitly permits alongside evidence and unknown.
Provenance, stated honestly
This is the account holder's knowledge, not vendor-written confirmation. The
original request was for written terms from Host Europe account support; that
correspondence never happened and, given the answer, has no purpose. The
provider record carries the distinction in status_evidence rather than
implying a vendor document exists.
The 2020 Preis_und_Leistungsverzeichnis_CloudStorage_1-0-1.pdf is therefore a
historical specification, not a currently orderable product. Every row of the
2026-08-10 due-diligence matrix that reads unknown for Host Europe Cloud
Storage should now be read as not applicable — the product is not offered.
That matrix is a dated evidence record and has not been rewritten; this document
supersedes its Host Europe column.
What this changes
data/providers/object-storage.json — host-europe-cloud-storage moves
from blocked-account-confirmation to not-offered.
T02 is satisfiable. Every acceptance requirement now has evidence, an
unknown, or a blocking answer for each provider. Host Europe's blocking answer
is that the product does not exist.
T01 is satisfiable, and the A/B/C comparison was never actually missing a leg. Host Europe has no managed S3 to price, so its real form in this comparison is self-managed Garage on Host Europe VMs — which is already priced from their public virtual-server catalogue and always was:
| Option | Month 1–9 recurring | Month 12 | Note |
|---|---|---|---|
| Scaleway Standard Multi-AZ (chosen) | €60.60 → €67.35 | €67.35 | elastic, no capacity ceiling |
| Hetzner Object Storage | €96.49 | €96.49 | within the 1 TB quota |
| Host Europe, self-managed Garage 3-node | €335.77 | fails closed | 400 GB usable; base demand reaches 458 GB |
Host Europe is roughly five times the chosen option on recurring cost, and runs out of usable capacity inside the twelve-month horizon: at month 12 the model refuses to quote because a fixed-capacity VM set has no per-GB overage price — you would buy another node, not another gigabyte.
So the decision recorded in opt:platform-audit-storage:2026-08 is not weakened
by the missing evidence; it is strengthened. The excluded option was excluded
for want of terms, and the terms would not have changed the outcome.
The second half of the statement matters separately
"No API to provision storage" is a procurement-facility fact, not a pricing
fact. Any future Host Europe resource is manually provisioned: no
programmatic create, no scoped provisioning credential, no automated teardown.
That belongs to the procurement facility (RESOURCE-WP-0005) and to
RAIL-HO-WP-0008, which still owns the railiance01 server's commercial terms.
It also means the existing resource:hosteurope:railiance01 record will never
acquire a provider-native resource ID from an API; whatever identity it gets
comes from the control panel or an invoice.
What is deliberately not changed
opt:platform-audit-storage:2026-08 is a decision record and keeps the state it
had when the founder approved it on 2026-08-14, including Host Europe's recorded
unknowns and the exclusion reason written at that time. A decision record
documents what was known when the decision was made. This document is the
supersession, and the next quarterly review reads both.
Residual
None for Host Europe object storage. The comparison set for future quarterly re-evaluation is Scaleway (incumbent), Hetzner, and self-managed Garage — on Hetzner VMs rather than Host Europe, since Host Europe offers no advantage on price, capacity headroom, or failure-domain independence from railiance01.