Evroc in 2026: an honest review of what it sells today

Evroc is a Stockholm company founded in 2022 "with a mission to build Europe's first hyperscaler". What it sells today is a small self-serve IaaS in one documented region, Stockholm, with three zones. Its contract is written for data control, with no sub-processor for the infrastructure services and no access from outside the EEA except to content you expressly make available, and its B200 GPUs cost EUR 8.00 an hour, about half the AWS list price in Stockholm. It cannot replace AWS or Azure for a typical application. There is no managed database, Kubernetes, registry, serverless, DNS, CDN, monitoring or backup; egress costs EUR 0.10 per GB with no allowance we could find; Evroc shows no certificate of any kind; and we found no independent account of anyone using it.

This article is one of a series comparing 24 European cloud providers with AWS and Azure; the overview puts them side by side. Everything below was checked on 15 and 16 October 2026 against Evroc's documentation, legal terms, price data, status page, press releases, register data and user reports, each at its source. We did not open an account or run workloads.

What you can use today, and what is announced

Evroc announces more than it documents. Only two things carry a "general availability" label: IAM in the documentation, and the AI agent roc since 6 June 2026. None is labelled preview, so the Service Terms' preview clause (no SLA, data may be deleted) applies to none, but the Compute and Networking API is versioned v1beta2.

Available on 16 October 2026, in Stockholm:

Announced, and not available or not confirmed:

The live service runs in what Evroc calls "strategic partner data centers in Paris, Stockholm, and Frankfurt", none of them named.

At a glance

What you can build

A team that needs a managed database, managed Kubernetes or anything event-driven runs it itself on VMs or keeps it elsewhere. Object storage covers the core S3 API but not bucket policies, ACLs, replication or lifecycle transitions, and has "Only one storage class".

The tooling is open and moves fast: the Terraform and OpenTofu provider reached 0.9.7 on 15 October 2026, five months after its first registry release, and the Go SDK, CLI and CSI driver are Apache-2.0 under evroc-oss on GitHub. The API moves too. On 26 June 2026 Compute and Networking went to v1beta2 with breaking changes: VMs without a security group "now have no network connectivity", and new IPv4-only VMs are no longer allowed.

What it costs

Evroc list prices in EUR, VAT excluded, from the price tables and price data on its VM and Object Storage pages, checked 15 and 16 October 2026, in Stockholm at 730 hours a month. AWS and Azure are priced in Frankfurt, about 1,200 km away.

Workload A, a starter setup: one VM with 2 vCPU and 4 GB, a 40 GB disk, one IPv4 address, 1 TB of egress and 100 GB of object storage.

AWS charges EUR 112.37 and Azure EUR 116.15 for the same, so Evroc costs 68% more than AWS; without the egress it is EUR 88.49. The VM page's calculator starts on A1a.s (2 vCPU, 8 GB, EUR 100.01 a month), which makes workload A EUR 213.31.

Workload B, a small production system: three VMs of 4 vCPU and 16 GB with an IPv4 address each, 300 GB of SSD block storage, a load balancer, PostgreSQL with a standby, 1 TB of object storage with 11 million requests, a Kubernetes control plane and 2 TB of egress.

This does not compare with AWS (EUR 985.89 to 1,082.61) or Azure, whose totals include a managed HA database and a Kubernetes control plane. Running PostgreSQL yourself on two A1a.s VMs with 100 GB disks each adds EUR 220.02, and replication, failover and backups become your work.

Egress and IPv4. Outbound traffic costs EUR 100 per TB, against EUR 80.30 on AWS and EUR 77.62 on Azure beyond their free 100 GB. Inbound is free. A public IPv4 address costs EUR 7.30 a month, against USD 3.65 (EUR 3.26) on AWS and Azure.

GPUs, per GPU-hour, billed by the hour: B200 EUR 8.00 and L40S EUR 1.50. AWS charges EUR 15.98 for a B200 in Stockholm on an 8-GPU instance, where Evroc sells a single-GPU VM, and EUR 2.08 for an L40S in Frankfurt. There is no H100, H200 or L4 VM and no spot tier, and the local NVMe on a GPU VM is lost if the host fails. Every GPU needs a quota request first. Think Models charge EUR 0.05 to 1.50 per million input tokens and up to EUR 6 per million output tokens.

Billing. Usage is billed monthly and charged to a credit card on the second day after month end; invoicing is for "eligible, high-spend accounts". Reservations take 30% off CPU VMs for 12 months and 50% for 36. No free tier, no spending limit or alert documented. Load balancer, snapshot, File Store and KMS prices are not published.

Price changes. We found none in the last 24 months. The General Terms let Evroc change list prices "at any point in time", effective for services already in use "when published on evroc's Website", with no notice period.

Reliability

What a zone is. Evroc defines its zones as "physically separate data centres within a region", each with "independent power, cooling, and network connectivity"; which partner facilities they are is not published. VMs, disks, snapshots and File Store are zonal. VPCs, public IPs, load balancers and object storage are regional: the load balancer can reach backends in every zone with health checks, and object storage is replicated across zones. With no managed database, there is no standby to place: that design is yours.

The SLAs, from the Service Terms of 29 September 2026:

• Every target is a "design objective", "for informational purposes", and credits are the "sole and exclusive right to compensation", capped at 25% of that service's monthly fees.
• For zonal services the levels "are conditioned upon that the Customer's architecture is designed to deploy services across multiple zones".
• Between 99.5% and 99.9% a VM earns nothing; the VM page itself promises "VM availability of 99.5%".
• You claim with evidence within 60 days of month end.
• Liability is capped at 15% of the preceding 12 months' fees, loss of data excluded.

AWS commits to 99.99% for EC2 across two or more zones and 99.5% for a single instance, with credits up to 100%.

Status page and incidents. status.evroc.com has five components, no per-zone view, and keeps "a rolling two-week window"; older day pages return 404. In that window it showed one Compute maintenance on Monday 12 October 2026, 10:00 to 18:00, with "brief periods of network disruption", and no incident. We found no incident, postmortem or outage report for the last 24 months anywhere. With two weeks of history, that is an absence of evidence, not a clean record.

Support

The targets are "for informational purposes" and give "no rights, remedies, or claims". Starter costs more than 13 times workload A, so a small customer gets business-hours email with a 24-hour target for a production outage. Evroc says its engineers are in Europe; support may also use "third-party support providers". We found no forum or community channel.

Getting an account

Signup at signup.evroc.com starts with a name, email and password; we went no further. A credit card is required. The Acceptable Use Policy forbids use "without being a verified legal entity or individual by evroc", but how verification works is not documented, and the Getting started page still describes accounts set up by support for "your company".

Default quotas per region: 20 vCPUs, 160 GB of memory, 3 public IPs, 20 TB of block storage and 0 GPUs. Workload B fits the vCPU and memory limits but needs four public IPv4 addresses (three VMs and the load balancer), so it needs a quota request to support before it can be built as specified. Neither that nor a GPU request has a published turnaround.

Evroc may suspend "with immediate effect" for non-payment or where it "reasonably believes" there is a breach, and fees keep accruing during a suspension.

Compliance and data protection

The Data Processing Addendum of 29 September 2026 is the strong part. Evroc "has not engaged, and will not engage, any sub-processor" for Customer Content in the infrastructure services; the AI services use "one sub-processor", unnamed, bound to the EU or EEA. Evroc staff may not access Customer Content from outside the EEA "except where the Customer has expressly made Customer Content available for support, maintenance, troubleshooting, security or engineering purposes", which matters because Evroc has a London office. Breaches are notified within 24 hours; audits are remote by default, at the customer's cost.

Think Models do not log or store prompts or responses; roc stores them unless history is off. On encryption the documents disagree: the Service Terms make the customer "solely responsible for encrypting all data" in object and block storage, while the S3 page says all data is encrypted at rest with Evroc-managed keys. No sub-processor list is published.

Who controls it

You contract with evroc Sweden AB, registered in August 2024 with "no employees", a subsidiary of evroc AB. The beneficial-owner entry for evroc Sweden AB, as shown by the aggregator tic.io (we could not read Bolagsverket directly), gives a masked name with more than 50% and up to 75% of control, through shares and through the right to appoint the board majority. Search snippets of two other aggregators name Mattias Åström as beneficial owner of evroc AB. Who holds the rest is not public.

Evroc names its investors as EQT Ventures and Norrsken VC (Swedish), Giant Ventures ("UK-based") and blisce/, which led a Series A of over EUR 50 million. blisce/ is Alexandre Mars's investment vehicle, based in Paris with an office in New York; TechCrunch calls it "U.S.-European". Mars joined the board. We found no non-European shareholder with control rights, but the cap table is not public. evroc AB reported no revenue and a net loss of about SEK 103 million for 2024 (aggregator data). The contract is under Swedish law with Stockholm arbitration under the SCC rules (General Terms 16.1 and 16.2).

The platform is Evroc's own, on undisclosed technology, in partner data centres. Customers it names include the Swedish Armed Forces.

Leaving

After termination you have 30 days to export through "evroc's standard export functionality ... only in the format in which it is stored"; help beyond that may cost extra. Either side may terminate for convenience on 30 days' notice. Exporting 10 TB at EUR 0.10 per GB costs EUR 1,000.

Lock-in is low because there is little proprietary to leave: object storage speaks the core S3 API, and self-managed Kubernetes built with upstream Cluster API and kubeadm moves as it is. IAM, the CLI and the Terraform resources are Evroc's own. No image import or export is documented, and moving a disk to another zone means copying its data.

What users report

We found no independent report of using Evroc: the 13 Hacker News comments that mention it, and the Reddit results, are passing mentions, news reposts and job ads.

Who it suits, and who should look elsewhere

Evroc suits organisations that need a Swedish contract with no US parent and no infrastructure sub-processor, for VM workloads, open-model inference or B200 GPUs from one per VM in Stockholm, and that run their own databases and Kubernetes. Swedish public-sector and defence-adjacent buyers following its work with the Swedish Armed Forces belong here too.

Look elsewhere if you need a managed database, managed Kubernetes or serverless; a certificate such as ISO 27001, SOC 2 or C5 for procurement now; a region other than Stockholm confirmed in writing; cheap egress; or round-the-clock help without paying EUR 2,500 a month.

Sources

Checked on 15 and 16 October 2026.

Pricing

• Virtual machines, price table and price data, Object Storage, GPU VMs, GPU clusters, Think Models, GPU campaign page
• Support plans
• AWS and Azure figures: AWS Price List bulk API and Azure Retail Prices API, converted at the ECB rate of 15 October 2026

Terms and SLA (all last updated 29 September 2026)

• General Terms and Conditions
• Service Terms
• Data Processing Addendum
• Acceptable Use Policy

Documentation (docs.evroc.com)

• Introduction, Getting started, Support, View your quota limits, Changelog
• Compute: Service definition, What's new in v1beta2, Regions and zones, VM resource profiles, GPU VMs, Disks, Public IPs
• Load balancer concepts; Object Storage and AWS S3 Feature Compatibility; File Store; IAM Service definition; Think; Billing
• Integrations: Terraform provider, CSI driver, CAPE
• A tour of the evroc cloud, 26 August 2026 and CAPE introduction, 15 September 2026
• Terraform registry, OpenTofu registry, evroc-oss on GitHub

Status and incidents

• Status page and Compute, 12 October 2026

Compliance

• Security and Sovereignty pages

Company and ownership

• About and Data centres
• Evroc releases: Series A, 20 March 2025, launch, 3 July 2025, Arlandastad land purchase, 3 February 2025, Mougins, 10 February 2025, SUSE, 8 December 2025, nuclear exploration, 6 October 2025, roc GA, 6 June 2026, Swedish Armed Forces, 18 June 2026
• Register data through aggregators: tic.io, evroc Sweden AB, merinfo.se, evroc AB
• TechCrunch: Evroc's Series A, 20 March 2025 and blisce/, 14 May 2024

User reports

• Hacker News comment search for "evroc" and Reddit search