Leapcell

Leapcell differentiates on billing model: pay per invocation, not per running hour — meaning idle services cost nothing, and costs scale directly with usage. Strong fit for AI backend services, async task workers, and cron jobs that run intermittently. Zero cold-start billing means the per-invocation model works for event-driven workloads. Git-based deployments (GitHub/GitLab) with automatic builds. For agents managing deployment lifecycle: deploy a new service from a repo, trigger redeployments, and manage environment variables via API. Free tier available. Growing fast in the AI developer community. Confidence is docs-derived.

REST API and CLI (leapcell) for service management. Resources: services, deployments, environment variables, domains. Deploy via Git push (GitHub/GitLab integration) or CLI. API: POST /v1/services creates a service (repo URL, build command, start command). POST /v1/services/{id}/deploy triggers a new deployment. GET /v1/services/{id}/deployments lists deployment history with status. PUT /v1/services/{id}/env updates environment variables (replaces all vars). GET /v1/services lists all services. Service types: web service, background worker, cron job. Build: Leapcell detects runtime (Node.js, Python, Go, Rust, etc.) from repo.

API key auth: Authorization: Bearer {api_key} header. Keys from Leapcell Dashboard → Settings → API Keys. Account-scoped. HTTPS enforced. No OAuth2. Environment variables stored encrypted in Leapcell (set via Dashboard or API). Git integration: Leapcell uses GitHub App or GitLab OAuth for repo access; credentials scoped to allowed repositories.

Standard HTTP status codes with JSON error bodies. Deployment transitions: pending → building → deploying → running/failed. Build failures include build log accessible via Dashboard. Per-invocation billing: usage tracked in near-real-time; spending alerts configurable. Service health: Leapcell monitors running services and restarts on crash. Cron jobs: execution history logged. Leapcell uptime at status.leapcell.io. Cold-start on first invocation after idle: typically fast (sub-second for most runtimes).

leapcell.io/docs covers service creation, deployment workflow, environment variable management, cron job configuration, and API reference. Getting started: create Leapcell account, connect GitHub, deploy first service in under 5 minutes. CLI available for local development and deployment. Documentation quality is improving (platform is relatively new). Community via Leapcell Discord and GitHub. Free tier provides meaningful capacity for evaluation and small production workloads.