Codara CloudDocumentation
Ship the whole application.Keep the whole picture.
Codara Cloud connects a GitHub repository to managed application infrastructure. Push a commit, get an HTTPS URL. Databases, domains, environments, logs and cost stay in the same console.
Access is invite-only
platform-users team. There is no open self-service signup. See Getting access.What Codara Cloud does
You connect a GitHub repository and choose a branch. On every push to that branch, Codara builds a container image, pushes it to a registry, and rolls it out. If the rollout fails, the previous release keeps serving traffic — a broken build never takes your app down.
Around that core loop sits everything an app normally needs: managed Postgres, MySQL, MariaDB, MongoDB and Redis; object storage and persistent volumes; scheduled jobs; custom domains with automatic certificates; and per-workspace cost tracking in EUR.
Start here
Take a GitHub repository to a live HTTPS URL, step by step.
Organizations, workspaces, projects, environments and services — and how they nest.
How sign-in works and what to do when it refuses you.
Install codaracloud and drive the platform from a terminal.
Guides
How a commit becomes a running container, and how to roll back.
Provision a database, connect it to an app, restore a backup.
Point a hostname at an app and get TLS issued automatically.
Tail runtime output and track CPU, memory and restarts.
See what each workspace costs and cap spend before it surprises you.
Configuration and secrets, per environment.
The 30-second version
Once you have access and the CLI is built, the whole loop is a handful of commands:
# Authenticate against the platform$ codaracloud login # See what is running$ codaracloud apps list # Build and release the current branch$ codaracloud deploy my-api --source # Watch it come up$ codaracloud logs my-api --followNote the flag. codaracloud deploy with no flags only restarts the current image — it does not build anything. Pass --source, --branch or --commit to produce a new build.