One account per person
Every operator has their own account. Organization access is invited, role-scoped, and removable without sharing a company password.
Codara owns the servers, the operating system and the certificates. You own the app. Every request is scoped to your organization, and every deploy leaves a record you can read.
your-org
Your organization
platform-api
postgres
volumes
another-customer
Not reachable
their-api
their-db
their-jobs
Every request and every lookup is scoped to your organization. Reserved machines add a second boundary underneath.
A hole in one layer should not hand over another customer's app, Codara's own systems, or every database password you have.
Every operator has their own account. Organization access is invited, role-scoped, and removable without sharing a company password.
Applications receive service-specific runtime credentials. Secrets are not sent to the browser or copied into unrelated environments.
Workloads, networking, databases, and storage are attached through explicit project and environment boundaries.
A deployment keeps the repository, commit, environment, actor, status, and release output together for investigation.
Activity and deployment history make operational changes understandable instead of burying them inside opaque automation.
You can reserve machines that run nothing but your own services, with capacity sized for your app rather than a sales tier.
Fixed prices only work if abusive traffic cannot buy infrastructure on your behalf. The platform treats attack load as a security event, not as demand.
Codara product endpoints run behind Cloudflare. Hosted apps are marked protected only after their hostname is enrolled, never inferred from a badge.
Autoscaling responds to resource pressure and stops at your plan's replica limit. Raw request count cannot create unlimited replicas.
Mitigated attack traffic belongs in security telemetry, not in ordinary customer usage or a surprise invoice.
Onboarding validates edge TLS and origin routing before an app is represented as shielded.
Edge traffic
Attack burst, filtered before your service
Your bill
The same before, during, and after
€5.00/month
Sharing machines is only safe when every request and every lookup is scoped to your organization first. Reserving machines of your own changes where the work runs as well.
Sign-in, your organization's membership, roles and plan decide which resources a request is even allowed to name.
Each environment runs in its own isolated space with its own network rules and capacity limits, so a running service cannot reach past it.
Databases, roles, credentials, attached disks and backups are separate resources you can see, not one shared secret behind the whole app.
Reserved machines for your organization, so no other customer's app is ever scheduled beside yours.
Codara Cloud publishes the controls it actually operates and does not claim a certification before it is earned. If your buyer sends a questionnaire, an engineer answers it with an architecture review and a written isolation plan.
Report security issues to cloud@codaracloud.com.
Activity is linked to actors and resources.
Membership and roles have an explicit owner.
Certificate state is visible and renewable.
Failed platform releases stop and roll back.
Infrastructure
Codara runs its own Kubernetes platform on Hetzner Cloud in the European Union, with Cloudflare at the edge.
Hetzner Cloud
Helsinki, Finland
Cloudflare
DNS, edge and R2 backups
Kubernetes
Operated by Codara
PostgreSQL
CloudNativePG operator
OCI images
Built with BuildKit
Every protection on this page, except dedicated machines (Enterprise), is on from your first deploy, on every plan. There is no security tier to buy and no checklist to work through.