Deploy
Any source
Deploy from any Git repo, a Dockerfile or a prebuilt container image.
20+ templates
Language and framework templates to start from.
Automated builds and rollouts
Every deploy is built and rolled out without manual steps.
Work
Codelint product
Code2Cloud
Ship to Kubernetes without touching infrastructure.
A self-service Platform-as-a-Service built by Codelint. It gives teams a Heroku-style "push and it’s live" experience on their own Kubernetes infrastructure, with networking, databases and observability included by default.
The problem
Every service needs the same plumbing
Deploying to Kubernetes properly means wiring ingress, DNS, TLS, secrets, databases, CI/CD and monitoring for every app.
Done by hand, that work is slow, repetitive and easy to get wrong, and it has to be repeated for each new service.
| Chore | api | web | worker | Code2Cloud |
|---|---|---|---|---|
| Ingress | Manual | Manual | Manual | Included |
| DNS | Manual | Manual | Manual | Included |
| TLS | Manual | Manual | Manual | Included |
| Secrets | Manual | Manual | Manual | Included |
| Databases | Manual | Manual | Manual | Included |
| CI/CD | Manual | Manual | Manual | Included |
| Monitoring | Manual | Manual | Manual | Included |
| Total | 21 manual setups | Defaults | ||
How it works
From repository to URL in three steps
Step 1
Connect a source
Point Code2Cloud at a Git repository, a Dockerfile or a prebuilt container image.
Step 2
Configure
Pick one of 20+ language and framework templates, set environment variables and attach a managed database if the app needs one.
Step 3
Get a live URL
Code2Cloud builds and rolls out the app, then wires ingress routing, cluster DNS and TLS so it is reachable straight away.
What is included
The parts a team would otherwise assemble for each service ship as defaults.
Data
One-click databases
Managed PostgreSQL, MySQL, MongoDB and Redis, with connection strings injected into the app automatically.
Networking
Networking by default
Automatic ingress routing, cluster DNS, TLS and environment variables.
Scaling
Autoscaling
Apps scale out of the box.
Isolation
Multi-tenant isolation
Tenants are isolated, and credentials are resolved server-side so they never reach the browser.
Operations
Operations console
A browser-based console for day-to-day operations, with a secure debugging terminal.
Observability
Built-in observability
Live logs, P50/P95/P99 latency, metrics dashboards and distributed tracing.
Observability
Logs, latency and traces from the first deploy
- Live logs
- Stream logs from every running instance in the browser.
- Latency percentiles
- P50, P95 and P99 latency per app.
- Metrics dashboards
- Dashboards for each app out of the box.
- Distributed tracing
- Follow a request across services.
Tech stack
What Code2Cloud is built on and runs.
Application
- Next.js
- FastAPI
- Node.js
Platform
- Kubernetes
- Docker
- Jenkins
Observability
- Prometheus
- Grafana
- Loki
- OpenTelemetry
- Tempo
Running services on Kubernetes?
Tell us how you deploy today. We will walk through how Code2Cloud would fit your cluster and what moving your apps onto it involves.