Infomaniak Public Cloud in 2026: a review for teams leaving AWS

Infomaniak, a Geneva company founded in 1994, sells email, kDrive and web hosting as well as an OpenStack public cloud. This review covers only the Public Cloud and the developer products on it (instances, GPUs, storage, Kubernetes, databases, an LLM API); reports about the other products are not used as evidence.

It gave the lowest totals in this series: EUR 13.12 a month for our starter workload and EUR 132.10 for the production one, which has no database because Infomaniak does not sell managed PostgreSQL. Instance traffic is free, the contract keeps data in Infomaniak's own Swiss data centres, and a public-benefit foundation holds the voting majority. Against that, MySQL is the only managed database, 2026 brought a 25-day network incident and a power event that took one region down for hours, both regions are in Switzerland with zones that appear to share a data centre, and free support has no response target.

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 Infomaniak's documentation, legal terms, price catalogue and status pages, the Swiss commercial register, its listing press releases and user reports, each at its source. We did not open an account or run workloads.

At a glance

What you can build

Status is generally available unless noted, meaning sold with a public price and no beta label on 15 October 2026.

Infomaniak's pages disagree about databases. The overview calls the Database Service "MariaDB, MySQL, PostgreSQL, Redis and OpenSearch-compatible"; the Database Service page marks all but MySQL "Available soon", with no date, and the price catalogue holds only MySQL. The Kubernetes launch post of 3 April 2025 already said managed databases were "coming soon". A team leaving AWS would run PostgreSQL, Redis, queues and a registry on its own instances, or keep them elsewhere.

Object storage is Swift with an S3 layer: "Swift is only S3-compatible. Some features are not available." aws-cli 1.37.0 and later cannot upload, because of an encoding Swift does not support, and the S3 page does not mention lifecycle rules, object lock, bucket policies or event notifications.

The tooling is upstream OpenStack: the standard APIs, the openstack CLI and the community Terraform provider. Infomaniak's own provider covers only Kubernetes, MySQL and DNS, and its latest release, 1.4.1, dates from 16 April 2026. Default perf1 disks are rated at 500 IOPS; perf2 (1,000 IOPS) is "only available upon request".

The Kubernetes Service launched on 3 April 2025. The Shared control plane is free, with one API server replica, up to 10 nodes and no SLA; the Dedicated planes run two replicas and their own etcd with a 99.9% SLA. Infomaniak is absent from the CNCF conformance lists for Kubernetes 1.31 to 1.34, where Exoscale, OVHcloud, Scaleway, STACKIT and IONOS appear.

What it costs

Infomaniak list prices, VAT excluded, from the catalogue its price page loads, checked 15 and 16 October 2026, in dc3-a (Geneva) at 730 hours a month. Prices are the same in both regions, and both are in Switzerland, so the nearest region to Frankfurt is outside the EU.

Two currencies. The catalogue lists CHF and EUR, converted at a fixed 1 EUR = 1.11 CHF. At the ECB rate of 15 October 2026 (1 EUR = 0.9305 CHF), a customer billed in EUR therefore pays about 16% less than one billed in CHF. Infomaniak does not say who is billed in which currency. Lines below are in CHF, totals also in EUR at Infomaniak's rate.

Workload A, a starter setup: one VM with 2 vCPU and 4 GB, at least 40 GB of 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 in Frankfurt, so Infomaniak costs about 12% of AWS (14% at the ECB rate, EUR 15.66). On AWS the 1 TB of egress alone is USD 81.00 of a USD 125.95 bill.

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 2 vCPU, 8 GB and 100 GB as primary plus standby, 1 TB of object storage with 1 million PUT and 10 million GET requests, a Kubernetes control plane and 2 TB of egress.

The nearest substitute, a "Multi-AZ" MySQL Business cluster of two nodes with 2 vCPU and 8 GB, adds CHF 69.04, for CHF 215.67 or EUR 194.30. It is not like for like: Infomaniak does not document where the second node sits, whether replication is synchronous or how long failover takes.

AWS charges EUR 1,082.61 for workload B on m7i.xlarge and Azure EUR 1,091.88 on D4s_v5, both with a highly available PostgreSQL. With the MySQL substitute Infomaniak costs 18% of either, or 21% of AWS at the ECB rate (EUR 231.78). Take the database out of the AWS total and it is still EUR 796.98, six times Infomaniak's EUR 132.10. The gap is in every line: three m7i.xlarge cost USD 528.89 a month against CHF 54.27, the 2 TB of egress USD 171.00 against nothing, the EKS control plane EUR 65.13 against EUR 26.31. Infomaniak does not say whether its vCPUs are dedicated, so the VM lines may not be like for like either.

The free Shared control plane would bring the total to CHF 117.43, with no SLA. The load balancer's address follows the docs' example, a floating IP, which needs a router gateway. Worker nodes are not included, as everywhere in this series.

Egress and IPv4. "Generally speaking, the incoming and outgoing traffic is free," says the price page. Object storage includes 10 TB of outgoing traffic per organisation per month, then CHF 0.009 per GiB (about CHF 8.38 per TB), and requests are not metered. Above 100 TB of bandwidth a month, the terms say "Infomaniak may suspend the Service". AWS and Azure charge EUR 80.30 and EUR 77.62 per TB beyond their free 100 GB. A public IPv4 address costs CHF 0.00457 an hour, against USD 0.005 on AWS and Azure.

Billing. The price page prorates the last hour, while the Public Cloud terms say billing "begins from the first second of use and is rounded up to the next started full hour". The terms are the contract. A stopped instance stops paying for CPU and RAM, but its disk, its GPU and a public IPv4 keep billing. "We don't offer quantity discounts", and the only cost control we found is the quota system, not a budget alert or spending cap. New customers in 37 listed countries get CHF 300 of credit for three months.

GPUs, per GPU-hour in EUR, every flavour "only available upon request": A2 0.15, T4 0.21, L4 0.25, L40S 0.63 and A100 80 GB 1.31, the A100 only with 128 vCPU and 240 GB of RAM. The H100 and B300 are "Contact our team", and there is no B200. In Frankfurt AWS charges EUR 2.08 for an L40S, EUR 0.90 for an L4 and EUR 3.82 per A100 80 GB. Infomaniak's GPU page shows other prices, VAT-inclusive for the L40S and A100 though it says VAT is excluded, and calls the A100 "40 GB of HBM2e"; we used the catalogue. The LLM API serves 15 models; its chat models start at CHF 0.20 per million input tokens.

Price changes. The general terms let Infomaniak "modify its prices at any time, without prior notice", for new orders or at renewal, which they do not define for hourly resources. We found no list-price change announced between October 2024 and October 2026; the price page's example of 4 CPUs, 8 GB and 50 GB at CHF 16.10 a month reads the same in an archived copy of 4 December 2024. A tracker, EUCloudCost, reported compute adjustments of plus or minus 5 to 10% in May 2026 without naming flavours; we could not confirm it.

Reliability

What a zone is. The documentation says: "Each of these zones have different network connectivity and power inputs." Zone names such as dc3-a-04, and status entries that call dc3-a and dc4-a a "datacenter", point to zones being parts of one data centre; that is our reading, as Infomaniak does not describe the sites. Zones exist for compute only ("There's only one for the volume service"), so block storage, with three Ceph replicas, and networks span the region. Both regions are in Switzerland: there is no failover to another country.

The database standby. MySQL Business runs two nodes and Advanced three, both "Multi-AZ". Standby placement, replication mode and failover time are documented nowhere we found, and since zones appear to share a data centre, "Multi-AZ" need not mean a second building. AWS and Azure keep a synchronous standby in another zone and fail over in 60 to 120 seconds. And Infomaniak "does not perform automatic backups of Customer data".

The SLA, Article 10 of the Public Cloud terms (review of 5 March 2026):

• The credit "will replenish the Free Tier in the form of usage credits": future use, not a refund.
• You claim within two months with "the identifiers of the unavailable OpenStack Resources", and Infomaniak pays only if the unavailability "is attributable to Infomaniak".
• Planned or emergency maintenance "suspends the application of penalties"; planned maintenance is announced 48 business hours ahead.
• Force majeure includes "failure of transmission networks", "power outage" and "shortages of raw materials or supplier stock-outs".
• Liability is limited "to the amount of the payment paid for the Service affected ... for the current billing period".

On paper the target beats AWS, which commits to 99.99% only for instances in two or more zones and to 99.5% for a single one; Infomaniak sets no zone condition. AWS gives until the end of the second billing cycle to claim, Azure 60 days. The exclusions narrow the gap: the 15 July outage began during maintenance on electrical equipment, and power outages are force majeure.

Status pages and incidents. status.infomaniak.cloud shows only the current state. infomaniakstatus.com keeps a "Last 60 days' history" for every Infomaniak service; older entries open only by direct URL, and we found none before March 2026. Public Cloud entries rarely state a cause.

The spring entry covered both regions but describes separate faults in each. On 23 September the Public Cloud is not listed as affected, but its console was. Of the Public Cloud entries, only the July event has a post-mortem.

Support

Paid plans run for at least six months. Their terms say response times "may not be respected in the event of ... a general breakdown, total unavailability of the Services", which is when you would call. Support is answered in Geneva and Zurich, without outsourcing; which languages is not stated.

AWS Basic cannot open technical cases and Azure Basic has no technical response target, so a free phone line is more than either includes. A one-hour target costs the greater of USD 29 or 9% of spend on AWS Business Support+, USD 100 a month on Azure Standard, and at least CHF 1,000 a month here.

Getting an account

Signup asks for a name, email, physical address and "a valid mobile phone number", which Infomaniak may validate "before being able to use his Organization, as well as at any time". The Public Cloud needs a Visa, Mastercard or CB card; PayPal and bank transfer are refused. The CHF 300 trial is offered in 37 listed countries; whether customers elsewhere can buy at all is not stated.

Quota level 1 allows 20 vCPU, 64 GB of RAM, 10 instances and 1,000 GB of volumes. The docs do not say which level a new account gets. Workload B needs 12 vCPU, 48 GB and 300 GB, which fit level 1 on self-service perf1 flavours, but if Kubernetes worker nodes share the project quota (not stated), more than 8 vCPU of workers would need a raise from support. Our reading: workload B is possible on day one if a new account starts at level 1, which the documents do not settle. On AWS the default of 5 vCPUs is below workload B's 12; Azure's 20 cores fit on paper.

Three clauses matter later. "Access to Resources cannot be guaranteed and is subject to their availability at the time of ordering." After a failed card debit "The Service is blocked on D+7 and automatically terminated on D+14". And the acceptable use rules ban "any activity related to cryptocurrencies" and the "configuration of a public VPN", among others, with suspension "immediately" for abusive use "or use impacting the infrastructure".

Compliance and data protection

The Public Cloud terms state: "All data transmitted by the Customer to Infomaniak is stored and hosted exclusively in data centers located in Switzerland and owned by Infomaniak." The Data Processing Agreement applies the Swiss FADP and the GDPR, gives 30 days to object to a new sub-processor, and rules out transfers outside the EU or EEA "without the Company's prior written consent". We found no sub-processor list for data hosted on the Public Cloud. For card payments, which the Public Cloud requires, the privacy policy names Checkout.com, with processing in the EU, the UK "and United States (Amazon Web Services hosting)".

Switzerland and the EU. Switzerland is in neither the EU nor the EEA. The European Commission's Decision 2000/518/EC of 26 July 2000 states that "Switzerland is considered as providing an adequate level of protection for personal data transferred from the Community". In its first review of 11 such decisions, of 15 January 2024, the Commission found that data transferred to those countries, Switzerland included, "continues to benefit from adequate data protection safeguards", so the decisions "remain in place". Whether that meets a contract asking for data inside the EU is for the buyer to judge. Infomaniak says its data is "safe from extraterritorial laws such as the Cloud Act"; that is its claim, not our finding.

Who controls it

You contract with Infomaniak Network SA in Geneva. Above it sit the group holding, Infomaniak Group SA, and a listed parent, Infomaniak SA, the former Perrot Duval Holding SA. On 24 September 2026 Perrot Duval's general meeting approved a reverse takeover in which Infomaniak Group SA's shareholders exchanged their shares for new Perrot Duval shares; the company took the Infomaniak name and has traded on the SIX Swiss Exchange as INFO since 1 October 2026.

The Fondation Infomaniak, a Geneva public-benefit foundation under cantonal supervision, holds all the Class A shares, which are unlisted and not freely transferable. Infomaniak's press release of 2 September 2026 said they would carry 63.3% of the votes after the transaction, with the listed shares making up 85.3% of the capital; the investors page says only that the foundation holds the majority since May 2026, when "the founder and the shareholders unanimously agreed to reduce their own voting rights in favour of a public-benefit foundation". The founder, Boris Siegenthaler, sits on the board; his stake after the listing is in the prospectus, which we did not read. We found no non-European parent or shareholder, though anyone can now buy the listed shares.

Net sales were CHF 54.2 million in 2025, cloud not broken out, and Infomaniak had 337 employees on 30 June 2026, all in Switzerland. The Public Cloud runs on OpenStack in its own data centres: D3 in Geneva and D4 in Plan-les-Ouates, Geneva. That dc4-a sits in D4 is likely from the names but not stated.

Leaving

Data leaves cheaply. Instance traffic is free, and object storage includes 10 TB of egress per organisation per month, then about CHF 8.38 per TB; above 100 TB a month the fair-use clause applies.

Compute, storage and networking are plain OpenStack (Nova, Cinder, Swift, Neutron, Octavia, Heat), so the same code runs against other OpenStack clouds in Europe, such as OVHcloud, T Cloud Public, Cleura, Elastx and Cyso Cloud, with region, flavour and network names changed. The docs advise keeping your own copy of images because "no archive is maintained within the cloud", but describe no export path.

The lock-in is in the managed layer: the Kubernetes and Database services use Infomaniak's own API and Terraform provider, MySQL backups and point-in-time recovery are Infomaniak features, and a dump is the portable route.

On termination the project is placed "in a state of logical deletion", the data "becomes immediately inaccessible" and is permanently deleted after seven days; "Logical deletion does not constitute a backup". The Data Processing Agreement requires every copy of your personal data to be deleted "within ten working days" of the service ending; its deletion clause says nothing about returning it. Export before you cancel. A change to the special terms applies when you accept it, or at the latest 30 days after the update; if you disagree, you must stop using the service within those 30 days.

What users report

The record on the Public Cloud is thin. Of 162 Hacker News comments mentioning Infomaniak since October 2023, about ten touch a cloud product and none describes production use; we found no migration write-up from AWS or Azure, and could search only r/Infomaniak on Reddit. Four of the five themes below rest on one report plus an Infomaniak document.

PostgreSQL is promised and has not arrived. Users report that Infomaniak "announced that managed PostgreSQL databases would soon be available ... it's been almost a year ... the support guys can't tell me exactly when", from a customer leaving for OVH (r/Infomaniak, August 2026), and "We built our Postgres stack including backups/upgrades/monitoring on top of infomaniak" (p3vgo8s, August 2026). The Database page still says "Available soon".

A long outage in DC4. One user reports a "big down time few weeks ago with their DC4 on public cloud" (p3slj42, August 2026), which matches the 15 July power event.

Limited S3. Asked which S3 features were missing, one user answered "Conditional writes" (p4ga8sf, August 2026). The docs confirm gaps, though not that one.

A thin Terraform provider. A hands-on Kubernetes review calls Infomaniak's provider "pretty minimal", handling "cluster and node pool creation, but that's about it" (EUCloudCost, January 2026, updated February 2026); the registry's resource list agrees. The same reviewer found it "actually works" and the Shared control plane free. The site carries affiliate links in general and discloses no relationship with Infomaniak.

Slow default disks. The same review measured perf1 at "iops : min=242, max=806, avg=498.45", in line with the documented 500 IOPS.

Against these, one customer stays despite "bumpy" service because "we need a European provider for this" (p3tti81, August 2026). We found no report on Public Cloud signup or suspension, and none on support quality that met our bar.

Who it suits, and who should look elsewhere

Infomaniak suits teams that want Swiss-hosted, Swiss-controlled infrastructure at low cost with free bandwidth and run their own stack on VMs or simple Kubernetes; MySQL users; buyers of L4, L40S or A100 GPUs, or of an open-model LLM API, inside Switzerland; and Swiss regulated customers, for whom a FINMA outsourcing mapping is published.

Look elsewhere if you need managed PostgreSQL, Redis or Kafka, serverless, a registry or a CDN from the same provider; if your contract requires data inside the EU rather than Switzerland; if you need failover to another country or zones in separate buildings; if you need H100, H200 or B200 capacity on demand; if you want a guaranteed support response without paying for it; if you need CNCF-certified Kubernetes; or if you want a long, independent track record for this cloud, which the evidence does not yet provide.

Sources

Checked on 15 and 16 October 2026.

Pricing

• Public Cloud prices, with the catalogue files it loads: instances, storage and network, Database Service, Kubernetes Service
• Kubernetes Service, Database Service, GPU, AI Services and AI Services prices
• Billing, metering and rating
• Price page, archived 4 December 2024
• Premium Support and support
• EUCloudCost, EU cloud price update, 20 May 2026
• AWS and Azure figures: AWS Price List bulk API and Azure Retail Prices API, converted at the ECB reference rates of 15 October 2026

Terms and SLA

• Specific Terms: Public Cloud, review of 5 March 2026, with the SLA in Article 10
• Legal documents, including the General Terms and Conditions, review of 24 April 2026
• Special Terms: Support Premium
• Data Processing Agreement and confidentiality policy

Documentation

• Public Cloud overview
• Docs: availability zones, quotas, flavours, S3, Terraform, custom images
• Infomaniak Terraform provider on the registry and on GitHub; OpenStack Terraform provider
• CNCF Kubernetes conformance, v1.34
• Kubernetes Service launch, 3 April 2025

Status and incidents

• Public Cloud status and Infomaniak status, 60 days
• Entries: 23 March to 17 April 2026, 8 April 2026, S3, 8 April 2026, Database Service, 13 to 15 July 2026, 15 July 2026, post-mortem, 23 September 2026, report, 13 October 2026

Compliance

• ISO/IEC 27001:2022 certificate, certifications and trust centre
• Commission Decision 2000/518/EC, COM(2024) 7 final and Commission press release IP/24/161, 15 January 2024

Company and ownership

• Legal notice, governance and investors
• Press release, 2 September 2026 and press release, 24 September 2026
• Swiss commercial register (Zefix): Infomaniak Network SA, Infomaniak Group SA, Infomaniak SA, Fondation Infomaniak
• D4 data centre inauguration, 28 January 2025

User reports

• r/Infomaniak, "I'm leaving Infomaniak", 14 August 2026, with the replies p3vgo8s, p3slj42, p4ga8sf and p3tti81
• EUCloudCost, "Infomaniak Kubernetes Review", 25 January 2026, updated February 2026