Cloud Noce
Managed cloud container

Cloud Noce container

Deploy from Git, the CLI or a Docker image. Cloud Noce manages networking, SSL, service health, replicas and persistent storage in one place.

Get startedChoose a container

Key features

What engineering teams need for reliable deployments.

Deploy from code or a Docker image

Connect a Git repository, upload a local folder or use a ready-made image. Cloud Noce handles the build, runtime, domain and SSL.

Replicas and automatic scaling

Run multiple service instances and increase capacity as load grows, without taking the service offline.

Persistent disk and backup

Keep service data on persistent storage and manage backups for fast recovery.

Integrated package access through European datacenters

Access packages, registries and APIs through European datacenters during builds and at runtime, without configuring a proxy.

Three ways to deploy, one workflow

Deploy in a way that fits your workflow

Every deployment path gives you a temporary domain, SSL, logs, health checks and version releases in one place.

From a Git repository

Connect GitHub or GitLab. Every push builds a new version and deploys it after health checks.

Git → Build → Deploy

From a Docker image

Run a public or private image from Docker Hub, GHCR, GitLab Registry, or a registry of your choice.

Image → Port → Run

With the Gerdoo CLI

Deploy your local project from the terminal, whether you work interactively, with scripts or in CI/CD.

gerdoo deploy
Ready-made stacks

Start with your language and framework

Start without writing a Dockerfile, or use your own Docker configuration for full control.

Platform features

Easy to start, ready to scale

The tools to deploy, monitor and recover a production service are available alongside your container.

Replicas and availability

Run multiple instances to distribute requests so a single instance failure does not take your app offline.

View plans

Auto scale

Increase capacity as traffic grows without moving servers or taking your app offline.

Explore pricing

CLI and development workflow

Create projects, deploy versions and check service status from the terminal alongside your CI/CD tools.

Getting started

Cloud AI agents

Run always-on AI agents with persistent storage, secure networking and connections to external models and tools.

Explore the agent service

Backup and recovery

Back up persistent data and recover services more quickly after errors or unwanted changes.

Backup docs

Access to global registries through European datacenters

Connect to global registries, package repositories and APIs through European datacenters, without a proxy inside your container or changes to your app code.

How it works

Use your own Docker image

Run any stack with a Dockerfile or ready-made image. Configure environment variables, ports, domains and start commands in the dashboard.

Docker documentation

Persistent storage

App files and data persist across deployments and are not deleted when the container is rebuilt.

Explore capacity
Ready-to-use applications

Databases, WordPress, Ghost and more

Add common tools alongside your service with ready-made settings, persistent storage and secure networking.

Explore all apps
Developer docs

From first deploy to production

Read the Cloud Noce guides for Docker, environment variables, domains, persistent storage, the CLI, backups and resource management.

View docsTalk to the Cloud Noce team
# deploy from your project
$ gerdoo login
$ gerdoo deploy

✓ image built
✓ health check passed
✓ service is live

Cloud container FAQs

What is the difference between a Cloud Noce container and a VPS?

With a VPS, you manage Docker, OS updates, networking, SSL and monitoring. For a cloud container, supply code or an image and choose resources; the platform handles the runtime.

Can I deploy an app without a Dockerfile?

Yes. Connect a code repository for stacks such as Node.js, Python, Go, Ruby and Laravel. Cloud Noce detects the language and build process. You can still provide a Dockerfile for full control.

Will my database and files survive a new deployment?

Yes. Use persistent storage or a database service for data. They remain separate from the running container version and are retained when you deploy new code.

You don't need to manage Kubernetes or Linux to get started.

Launch your first container

Choose your code or image, set resources and publish on a secure domain.

Start free