Cyso Cloud vs Leafcloud Object Storage

Instancias de compute escalables

Las instancias se lanzan en segundos con flavors adaptados a cargas de trabajo: estándar (equilibrado), optimizado para CPU (hasta 64 vCPUs) u optimizado para memoria (hasta 512 GB RAM). El almacenamiento efímero se vincula al ciclo de vida de la instancia; los volúmenes persistentes ofrecen triple replicación y escalado de IOPS (5-25 por GB). Las tarifas por hora empiezan en 0,026 € para especificaciones de entrada, permitiendo ajuste preciso de costes sin sobreaprovisionamiento.

Object storage compatible con S3

Diseñado para copias de seguridad y grandes conjuntos de datos, este servicio ofrece capacidad ilimitada con SLA de disponibilidad del 99,99 %. Las unidades NVMe garantizan baja latencia; los datos permanecen en regiones de la UE seleccionadas. Precios: 0,055 €/GB almacenamiento, entrada gratuita, 0,055 €/GB salida. Las operaciones cuestan 0,055 € por 10.000 solicitudes PUT/LIST, soportando acceso REST API para integración fluida.

Kubernetes gestionado

Enterprise Managed Kubernetes (EMK) incluye un plano de control a 29,99 € mensuales (HA a 59,99 €), con actualizaciones automatizadas e hibernación para ahorro de costes. El SLA del 99,9 % cubre clústeres de alta disponibilidad. Los usuarios despliegan vía panel; funciones como autoscaling gestionan cargas variables. La documentación guía la configuración en minutos.

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.