Kubeletto
Product Deep Dive

What Kubeletto abstracts away

Modern application scaling provides immense resilience but introduces heavy complexity: ingress routing, certificate renewals, configuration maps, and container registries. Kubeletto abstracts this away into a single Git-driven developer control plane.

Container Image Deployment Path

Deploy OCI-compliant container images from any public or private registry. Kubeletto's API pulls registry tags, checks layers for security compliance, asserts image digests, and triggers the container revision engine. Your image starts running in seconds on isolated runtime nodes.

CLI Deploy Command:kubeletto deploy --app billing-service --image docker.io/library/redis:alpine --wait
{
  "serviceName": "billing-service",
  "source": {
    "type": "image",
    "reference": "docker.io/library/redis:alpine"
  },
  "runtime": {
    "port": 8080,
    "cpu": "0.25",
    "memory": "256Mi",
    "minScale": 0,
    "maxScale": 5
  }
}
{
  "event": "github.push",
  "repository": "benelabs/billing-api",
  "commit": "a1b2c3d4e5f6",
  "branch": "main",
  "build": {
    "builder": "nixpacks",
    "status": "queued"
  }
}

GitHub Git Push Pipeline

Link your repository using the Kubeletto GitHub Integration. Every push triggers our Git webhook receiver, spawning an isolated compiler workspace inside an ephemeral build worker to compile, scan, sign, and deploy your source branch automatically.

  • Automatic Dockerfile detection or framework compilation utilizing Nixpacks.
  • Blazing-fast build layer caching backed by secure object storage.
  • Opt-in image signing with Cosign and support for custom container registries.

Scale-to-Zero Auto-Scaling

Traditional hosting charges flat rates for idle servers. Kubeletto's autoscaling integration automatically scales replica counts down to 0 if a service goes without traffic. On new requests, our routing layer scales up the container in seconds, forwarding traffic without dropouts.

Min Scale0
Max Scale10
Wakeup delaySeconds
// Autoscaler Scale Loop Sequence
Inbound Traffic Rate: 0 req/secScale ➜ 0 replicas
Request Ingress TriggeredSpawning replica...
Inbound Traffic Rate: 28 req/secScale ➜ 2 replicas

Abstraction Matrix

Compare what Kubeletto manages automatically vs the manual configurations required by raw cloud infrastructure deployments.

Manual Infrastructure Tasks
  • Writing complex YAML manifests for Deployments, Services, and IngressRules.
  • Operating Docker registry credentials, image pull secrets, and vulnerability scanner daemons.
  • Provisioning cert-manager CA issuers, configuring DNS records, and renewing Let's Encrypt certificates manually.
  • Managing horizontal pod autoscalers (HPA), request-based concurrency parameters, and custom route triggers.
Automated Kubeletto Handling
  • Single-command CLI deploys or automatic webhook continuous integration triggers.
  • Isolated build sandboxes using runc, seccomp, and AppArmor profiles.
  • Automatic route provisioning, DNS configurations, and wildcard SSL subdomains allocation (https://{slug}.kubeletto.app/).
  • Instant scale-to-zero compute runtimes with automated TCP/HTTP readiness probes.