PaaS or CaaS? Gyro Containers (ECS) vs Serverless

When you want to run a Docker image without managing servers, you meet two abbreviations: PaaS (Platform as a Service) and CaaS (Container as a Service). Gyro offers both, in Istanbul with data staying in Turkey: Gyro Containers (ECS) is a managed container PaaS, and Gyro Serverless Containers is a CaaS.

Gyro Containers (ECS): a managed container PaaS

You buy an environment: a node pool dedicated to you. We run the Kubernetes-based platform, HTTPS certificates, zero-downtime deploys and autoscaling; you provide the image, the port and the resource size. All services in the environment (e.g. web and api-gateway) share the pool's resources. Billing is hourly and never exceeds the plan's monthly cap. It suits teams with a few always-on services looking for a managed Kubernetes or Heroku/Render-like experience.

Gyro Serverless Containers: CaaS

There are no nodes. You pick 0.25-4 vCPU and 0.5-30 GB of memory per container; you pay by that container's size and only while it runs. This AWS Fargate-like model suits occasional jobs, many small independent apps or services with spiky load. Each container runs in its own sandboxed runtime.

Which one to choose?

• A few always-on services with a predictable monthly cap: Gyro Containers (ECS), i.e. PaaS.
• Occasional jobs or many small, independent apps: Gyro Serverless Containers, i.e. CaaS.
• Need root access, persistent disk or your own database: neither; a Gyro Cloud Istanbul server fits better.

Both are managed with the same panel, REST API, gyro CLI and Terraform provider, and billed hourly from your prepaid balance. Detailed comparison and example costs: Serverless or node-based? · Plan limits: Gyro Containers concepts and packages.