Predictable monthly pricing for a private managed environment.

Because the VPS is the easy part. What takes the time is everything after it: certificates, database setup, backups that actually run, log access, OS updates, and finding out why the application started failing after a deploy. CloudContainer does that work as a product rather than as a weekend project you maintain forever.

Your environment does run on real dedicated compute, and we are not going to pretend otherwise. The difference is that you never administer it. You connect a GitHub repository, and deployments, database, storage, certificates, backups, monitoring and OS maintenance are handled by the platform.

Two things. Before a deployment it reviews what changed and looks for security mistakes — committed secrets, vulnerable dependencies, authorization gaps, risky configuration. After a deployment it watches logs, errors, restarts and resource use, and when something changes it correlates it with recent deployments and tells you what it thinks happened. Both produce an instruction you can paste back into your coding agent.

No. It produces findings and instructions. Whether to act on them, and how, is entirely yours. CloudContainer does not modify your repository or your database schema.

The control plane manages your environment but is not in your application's normal request path, so a problem on our side should not take your running application or database down with it. That is a property of how the system is built, not an uptime guarantee — see the terms for what is and is not committed.

Your source code stays in your own GitHub organisation. PostgreSQL is standard PostgreSQL and the object store speaks the S3 API, and you can access those credentials and export your data. We would rather you stayed because the product is good.

CloudContainer compute runs on Norwegian infrastructure. AI Security Review and AI Operations send code and log excerpts to an external model provider for analysis, so those specific requests leave the environment. If data location is part of your procurement process, contact us and we will describe the current architecture precisely.

Anything that builds into a container and listens on a port: Next.js, Remix, Nuxt, SvelteKit, Django, Rails, Laravel, FastAPI, Express, Go, Rust and others. If your repository has a Dockerfile we use it; if it does not, we detect the stack and build one.

No. Prices and limits on this page are provisional while the product is being built, and are marked as such. Nothing here is a commitment yet. If you need certainty before committing, talk to us.