Cloud Noce platform

PaaS is Cloud Noce’s main product for running applications without managing machines or operating systems. Every workload is a service: a website, API, worker, cron job, database, broker or Docker image. Cloud Noce manages builds, runtime, networking, HTTPS, logs, metrics, volumes and the release lifecycle, so you can focus on application code and configuration.

Sources, Dockerfiles, framework detection and monorepos

Deployment

Secrets, build-time, runtime and references

Variables

Add-ons, bindings, volumes and backups

Data

Builds, releases, rollback, promote and cron

Operations

Build error explanations and suggested fixes

AI debugger

Manage services with MCP and a coding assistant

Working with AI assistants

The complete service lifecycle

Choose a project and environment

Create a project for your product and select production, staging or preview. Members, shared secrets and add-ons are managed at project level.

Connect the source

Choose GitHub/GitLab, a Docker image, a template or a local folder. For source code, Cloud Noce prioritizes the Dockerfile and detects the framework if none exists.

Configure runtime requirements

Web applications must listen on 0.0.0.0:$PORT. Set the command, root directory, process type, exposure, health checks and replicas to suit the application.

Connect configuration and data

Create variables at the right level, mask secrets, bind add-ons and mount persistent data paths on volumes.

Deploy and verify

Read the build logs, then runtime logs. Check the default URL, dependencies and health endpoint before connecting a custom domain.

Manage the release

Every deployment has a trackable build and release. Promote a verified version, and use rollback to return to a previous artifact if a failure occurs.

Regular services are always on and stop only through an explicit Stop action. Cron runs according to its schedule and has a separate run history.

Choosing a service type

Need	Suggested configuration
Website or API	Web process + HTTP exposure
Queue consumer	Worker + private
Scheduled task	Cron + cron expression
Public database or broker	TCP exposure, preferably with access controls
Internal service	Private and reference variables

Your responsibilities

Your team is responsible for correct commands and ports, database migrations, endpoint security, credential management, version compatibility and recoverable backups. Never rely solely on the container filesystem or a volume without backups for important data.