Kubeletto is a simple PaaS (Platform as a Service) that lets you deploy any containerized app in minutes. Push code, auto-deploy, and scale - all with zero infrastructure complexity. Free to use during our active beta.

What makes Kubeletto different?

Kubeletto offers unmatched flexibility to run any containerized application with developer-friendly workflows, autoscaling from zero, and simple observability without sacrificing performance or reliability.

Do I need infrastructure expertise to use Kubeletto?

Not at all! Kubeletto makes infrastructure invisible. Simply push your code, and we handle everything—building, deploying, and scaling. Focus on your app, not server management.

How quickly can I deploy an app?

You can deploy your first app in minutes. Just connect your Git repository, push your code, and Kubeletto handles the rest—building, deploying, and hosting your containerized application.

Platform Glossary

Serverless Containers

Category:

Definition

Serverless containers are OCI-compatible container workloads that run on managed infrastructure with automatic scaling (including scale to zero), without the operator needing to provision, configure, or maintain servers or Kubernetes clusters.

Detailed Explanation

Traditional containers require you to provision compute (EC2 instances, VMs, Kubernetes nodes), configure a container runtime, set up networking, manage security patches, and handle autoscaling yourself.

Serverless containers abstract all of that away. You provide a container image and the platform handles: - Scheduling containers onto compute nodes - Networking and TLS termination - Horizontal autoscaling based on traffic - Scale-to-zero when idle - Health checks and restarts on failure

The "serverless" label means no server management — not that servers don't exist. Compute still runs on physical machines somewhere; you just don't know or care which ones.

**How serverless containers differ from traditional serverless (AWS Lambda, Cloudflare Workers):**

| | Lambda / Functions | Serverless Containers | |---|---|---| | Unit of deployment | Function (handler code) | Full OCI container image | | Execution time limit | 15 minutes max | Configurable (minutes to hours) | | Language support | Limited runtimes | Any language that runs in a container | | Startup overhead | Cold start varies | Depends on image + app startup | | State | Stateless by default | Stateless by default (persistent volumes optional) |

Serverless containers give you the operational simplicity of Lambda without the runtime restrictions, making them ideal for deploying existing containerized applications without refactoring.

How Kubeletto provides Serverless Containers

Every application on Kubeletto runs as a serverless container. Kubeletto uses Knative Serving on a managed Kubernetes cluster, which provides automatic pod scheduling, ingress routing, TLS provisioning, and scale-to-zero without any configuration from the user. You supply the container image; Kubeletto handles everything else.

Try it free

Frequently Asked Questions

What's the difference between serverless containers and AWS ECS Fargate?

AWS Fargate runs containers without managing EC2 instances but still requires you to configure VPCs, task definitions, ALBs, and IAM roles. Serverless containers on Kubeletto abstract all of that — you just deploy an image.

Can serverless containers run long background jobs?

Yes. Unlike Lambda, which has a 15-minute execution limit, serverless containers can run processes for hours. On Kubeletto, long-running request timeouts are configurable up to 15 minutes per HTTP request.

Are serverless containers stateless?

Container filesystems are ephemeral on Kubeletto — data written locally is lost on redeploy. For persistent state, use an external database, S3-compatible object storage, or a managed cache (Redis).

See Serverless Containers in action

Deploy your first app on Kubeletto — free during our active beta.

Start Deploying Free Browse All Terms