Web services
Frontends, APIs, and long-running servers with health checks and zero-downtime rollout.
The platform
Every layer of production, in one coherent system.
Connect a repository once. Codara Cloud builds it, places it, exposes it, watches it, and keeps each environment understandable.
Designed around ownership
The hierarchy answers who, what, and where.
An organization owns access and billing. Workspaces separate companies or customers. Projects hold products. Environments isolate change. Services run the workload.
01
Organization
People & billing
02
Workspace
Company or customer
03
Project
One product stack
04
Environment
Prod, stage, preview
05
Service
App, DB, job, volume
A canvas, not a scavenger hunt
See the stack as a system.
The project canvas shows connections between code, applications, data, and domains. Click a service to configure it without losing the architecture around it.
cloud.codaracloud.com
Codara SolutionsInternalCodara CloudProduction
Project architecture
A complete stack, one deploy away.
GitHub
main · 9f43c1e
Connected
platform-api
Balanced · Autosize
Healthy
PostgreSQL
20 GiB · backed up
Ready
api.codaracloud.com
TLS managed
Live
More than web apps
The whole stack deploys together.
A service is any operational part of the product. Add only what the project needs, then configure each environment independently.
PostgreSQL
Attached relational databases with scoped credentials, persistent storage, and backups.
Workers & jobs
Long-running queues, scheduled jobs, and one-off tasks live next to the application.
Persistent volumes
Durable storage attached explicitly to the services and environments that use it.
Environments
Production stays boring while previews move fast.
Use permanent production, staging, and development environments. For pull requests, Codara can create an isolated preview and remove it when the branch closes.
Environment-specific configuration
Change replicas, variables, domains, or data attachments without altering the project definition.
Safe preview defaults
Preview services sleep at zero when idle; databases and custom domains are never cloned accidentally.
A visible path to production
Every deployment keeps the commit, actor, status, and environment together.
codara-cloud
3 environments · 8 services
Production
main
Staging
staging
PR #184
feat/usage
Resource profile
Automatic recommendations remain editable
Eco
0.25 vCPU · 256 MiB
Balanced
1 vCPU · 1 GiB
Performance
2 vCPU · 4 GiB
Resource control
Autosize normally. Override instantly.
Most services should run on automatic allocation so idle capacity does not eat the margin. When a workload needs certainty, select a profile or enter CPU and memory manually.
AutomaticEcoBalancedPerformanceManual
One flow from code to URL
Push code. Watch the platform do the rest.
Codara’s build plane does not depend on the customer paying for GitHub Actions. Repository workflows can keep doing their own work without becoming a requirement for deployment.
01
Connect
Choose a repository, branch, root path, and build settings.
02
Build
Codara builds an OCI image inside its controlled build plane.
03
Release
Health checks and rollout status decide when the new version is ready.
04
Route
Managed TLS and DNS verification put the service on its domain.
Private preview
Build once. Operate the complete product.
Start with one project and an automatic resource profile. Add environments, databases, and dedicated capacity when the application earns them.