Exoscale vs Leafcloud Object Storage

Instancias de compute de alto rendimiento

Las instancias de compute de Exoscale usan almacenamiento local SSD con opciones estándar, optimizadas para CPU, memoria o almacenamiento. Los tamaños van de Micro (512 MB RAM, 1 núcleo) a Jumbo (225 GB RAM, 24 núcleos). Las instancias GPU con tarjetas NVIDIA (A30, V100, A40, A5000, RTX 6000 Pro) encajan para tareas de IA. La anti-afinidad garantiza que las instancias se distribuyan entre hosts para resiliencia. Snapshots y plantillas personalizadas ayudan en copias de seguridad y despliegues. La facturación prorratea al segundo, con instancias apagadas cobradas solo por almacenamiento.

Servicio Kubernetes escalable (SKS)

Kubernetes gestionado despliega clústeres en 120 segundos. Los clústeres Starter son gratuitos (sin SLA), Pro ofrece 99,95 % de disponibilidad. Los usuarios escalan nodos worker, gestionan planos de control vía portal, CLI, API o Terraform. Se integra con balanceadores de carga de red. Soporta apps cloud-native en todas las zonas.

DBaaS y almacenamiento gestionados

DBaaS cubre PostgreSQL, MySQL, Kafka, OpenSearch, Valkey y Grafana, con planes desde Hobbyist (2 GB RAM) hasta Premium (225 GB RAM, múltiples réplicas). Object Storage es compatible con S3 con multi-redundancia y replicación. NVMe Block Storage adjunta múltiples volúmenes por instancia para necesidades de baja latencia. Tráfico: entrada gratuita, intra-zona gratuita, 1 TB saliente gratuito por instancia mensual.

S3 API at leafcloud.store (europe-nl-ams1)

Path-style S3 endpoint https://leafcloud.store, region europe-nl-ams1. Works with AWS CLI, boto3, rclone, Cyberduck, MinIO mc, and other S3 SDKs. Documented features include public or private containers, bucket policies and ACLs, multipart uploads, and presigned URLs. Max object size is 5 TB via multipart. Authentication uses OpenStack EC2 credentials (openstack ec2 credentials create), not the dashboard password.

OpenStack Swift and Horizon dashboard

The same store is reachable as OpenStack object storage (Swift). Create and browse containers at create.leaf.cloud under Object Store. Native CLI uses project-scoped OpenStack auth (openstack container create / object create). Container names must be unique across all Leafcloud users. Docs say there is a limit on how many containers you can create (the exact quota is not published).

Ceph cluster with 3x replication in Amsterdam

The product page describes a Ceph backend (Apache 2.0 software) with triple replication across separate physical nodes in Amsterdam. Persistent objects sit at the Core facility. Compute Leaf sites are a different path and are not where object data is stored, according to the security pages. This is a single-region store, not a multi-region S3 deployment.

SSE-C plus TLS in transit

Official docs show S3 server-side encryption with customer-provided keys (SSE-C, AES256). Leafcloud uses the key on each request and does not store it. Lose the key and you cannot read the object. The product table also lists encryption at rest and TLS in transit as supported. DPA language is TLS 1.2+. LUKS-by-default messaging on the security pages refers to block volumes, not this object API.

Terraform state, Velero, and Nextcloud recipes

Leafcloud publishes working recipes for Terraform’s S3 backend (path-style, skip checksum/region checks, endpoint leafcloud.store), Velero Kubernetes backups (s3ForcePathStyle plus s3Url), and Nextcloud primary objectstore pointing at leafcloud.store:443. Useful if you already run those tools. Object versioning is not available, so state and backup designs must version keys themselves or copy out.