GitHub or GitLab
Select a repository and branch. Cloud Noce detects the language and build and start commands, then deploys a new version on each push.
Connect repository → Choose branch → Deploy
Cloud platform
Cloud Noce PaaS: from code to runtime, without server management
Send code from Git or the terminal, connect a database, then promote the approved build to production.
Key features
What engineering teams need for reliable deployments.
Managed deployment
Run web services, workers, scheduled jobs and Docker images. The platform manages hosting, certificates, routing, logs and service lifecycle.
Automatic builds or Dockerfile
Turn code from Git or your terminal into a runnable build. We use your Dockerfile if you have one, or detect the project language automatically.
Managed add-ons
Create relational databases, Redis, caches and queues in your project. Connection details are securely injected into the service environment.
Deploy from Git with previews
Push to your main branch to update staging or production. Pull requests can have their own preview URLs.
Promote without rebuilding
Promote the same build you tested in preview to production, applying only the destination environment's settings.
Custom domains and certificates
Connect custom domains to your services. Certificates are issued and renewed automatically.
Always on and reliable
Services stay online and respond without cold starts. Start on the free plan and upgrade when you need more resources.
Project and private network
Services, add-ons, production environments and previews share your project's secure private network.
How the Cloud Noce platform works
Cloud Noce follows clear principles to help you develop faster and keep services reliable.
Runtime
The platform manages web services, background workers and scheduled jobs.
Automatic builds
Use a configuration file or automatic language detection to create a runnable build.
Add-on
Create databases, caches and queues alongside your service, with connection details ready to use.
Send code
Push to Git to trigger a build and release automatically.
Safe promotion
Promote the exact build you tested to production for your users.
Get started as a developer
Deploy from Git, Docker or the CLI
Create a project and choose a deployment method. Check the port and environment variables; Cloud Noce handles the build, temporary domain, SSL, logs and release.
Docker Image or Dockerfile
Run a ready-made image from a registry or give Cloud Noce a Dockerfile to build and deploy.
Image / Dockerfile ← Port ← Deploy
Gerdoo CLI
To deploy a local folder, install the CLI and sign in. You do not need to create a Git repository.
gerdoo login → gerdoo deploy
1. Create a project and choose a source
2. Configure environment variables, port and resources
3. Test the temporary domain and connect your own
Ready-made apps for Cloud Noce PaaS
Alongside your Python, Node.js or other code, you can launch ready-made apps with persistent storage, a custom domain and SSL. These apps are part of the same Cloud Noce platform.
AI and vector data
Run agents, language model interfaces, AI workflows and semantic search on your infrastructure.
Database, cache and storage
Run your database and persistent storage beside the main service on your project’s private network.
Websites, content and business
Launch site builders, headless CMSs, office tools, and business software without manual installation.
Development, automation and search
Get ready-to-use development tools, code repositories, workflow automation and app search.
Monitoring, analytics and communication
Monitor service health, errors and data, and connect team and microservice tools securely.
Supported cloud platform technologies
Deploy code in popular languages and frameworks. Cloud Noce configures the platform for your project automatically.
Frequently asked questions
Focus on code, not infrastructure, with Cloud Noce PaaS
Launching and maintaining an app involves server setup, SSL, domains, new deployments, logs and resource management. These tasks can take time away from development.
Cloud Noce brings those tasks into one dashboard. Deploy a project, monitor it and adjust service resources as it grows.
This helps teams release new versions faster without adding more server administration work.
Why use Cloud Noce PaaS?
A PaaS should simplify deployment and app management while giving developers the control they need. Cloud Noce brings these tasks into one workflow:
- Deploy apps quickly: Connect your project and build and deploy it without preparing a server manually.
- Manage domains and SSL together: Connect a domain and manage secure access in the same dashboard.
- View logs and service status: Find the logs and status information you need to troubleshoot app issues.
- Adjust resources as you grow: Change service resources as your app’s needs change.
- Connect supporting services: Add databases, caches, queues and other components alongside your app.
- Built for solo developers and teams: Whether you work alone or with a team, Cloud Noce brings deployment and app management into one place.
What can I run on Cloud Noce PaaS?
Run web apps, content management systems, development tools, team collaboration apps and data processing services on Cloud Noce.
- Node.js cloud hosting: To run APIs, backends and Node.js apps, use Node.js cloud hosting on Cloud Noce to deploy and manage your project.
- Cloud WordPress hosting: For WordPress websites, cloud WordPress hosting runs WordPress on Cloud Noce and lets you manage site resources.
- Joomla hosting: For a Joomla website, Joomla hosting gives you an environment to run the CMS on Cloud Noce.
- Drupal hosting: For Drupal projects, Drupal hosting provides the runtime and resources your site needs.
- Mattermost hosting: Teams that use Mattermost for internal communication can run it with Mattermost hosting on Cloud Noce infrastructure.
- GitLab hosting: To manage repositories and CI/CD, use GitLab hosting to run GitLab in your own cloud environment.
- Jupyter cloud server: For analytics, machine learning and notebook projects, use a Jupyter cloud server to run Jupyter and manage its compute resources.
From code to running app in a few steps
Deploying an app on Cloud Noce is straightforward: choose a service, connect your project, configure it and start it in the cloud.
- Connect your project: Connect a repository or choose another deployment method to prepare the service.
- Choose the resources you need: Compute and memory scale with usage, and storage expands as it fills. You pay for actual usage.
- Build and deploy your app: Once configured, the app is built and deployed, and a running version becomes available.
- Manage domains and service settings: After deployment, manage the domain, environment variables and other service settings in the dashboard.
- Release new versions faster: Deploy new versions as you develop, without setting up the infrastructure again.
Manage your app in one place
Most apps need more than a runtime. Add a database, cache, queue, domain and supporting tools alongside the main service.
- Managed databases: Choose managed databases that fit your app without maintaining a database server yourself.
- Caches and queues: Add cache and queue services to improve responses and handle background jobs.
- Domains, DNS and SSL: Connect a domain and manage DNS and SSL settings together.
- Logs and deployments: Inspect logs and deployed versions to monitor the app, investigate errors and manage releases.
Run your app on Cloud Noce PaaS in European datacenters
Apps running in European datacenters may need access to external services and package repositories. Cloud Noce provides a European datacenter network route to those resources.
Run your application in European datacenters and connect to the APIs, repositories and other external resources it needs during builds, deployments and runtime.
This is useful for projects that run in European datacenters but depend on external services during development or operation.
Who is Cloud Noce PaaS for?
Cloud Noce PaaS suits projects that need quick deployment, simpler infrastructure management and room to grow, from early prototypes to growing apps.
- MVPs and early products: Spend less time preparing infrastructure and more time building and testing the first version of your product.
- Web apps and SaaS products: Deploy new versions of your app and manage services in one place.
- APIs and backend services: Choose resources to match the requests and processing your API needs.
- Software teams: Spend less time managing infrastructure and more time building features and fixing issues.
- Growing projects: Adjust service resources as your app grows.
Compare hosting, cloud servers and PaaS by control, technical setup, deployment speed and maintenance responsibility:
| Criteria | Hosting | PaaS service | Cloud servers |
|---|---|---|---|
| Infrastructure control | Limited | Medium | High |
| Manage the operating system | No | No | Yes |
| Configure the web server | Usually no | Usually no | Yes |
| Setup speed | High | High | Medium |
| Suitability for app deployment | Depends on the hosting type | Well suited | Suitable with manual configuration |
| Resource management | Limited by the plan | Adjustable for each service | Full control |
| DevOps experience needed | Low | Low to moderate | Moderate to high |
| Continuous deployment support | Limited | Supported | Supported with configuration |
| System configuration freedom | Low | Medium | Very high |
| Best for | Simple sites and projects | Software developers and teams | Projects requiring full infrastructure control |
Choose a cloud server when you need full control of the operating system and server settings. Choose conventional hosting for a ready-made website environment. Choose PaaS when you want to deploy apps quickly with less infrastructure management.
How is Cloud Noce PaaS billed?
Start on the free plan with one project and one service. A free subdomain and SSL let you test the app before connecting your main domain.
If your project needs more resources, upgrade to a paid plan. Paid usage is billed hourly based on the resources used.
Usage-based billing gives early-stage projects and workloads with changing demand more flexibility over infrastructure costs.
Cloud PaaS from Cloud Noce
Run your project on Cloud Noce infrastructure in Milan, Italy with deployments, resource controls, domains, logs and supporting services in one dashboard.
The European datacenter network can help projects that depend on APIs, repositories and services hosted elsewhere connect to those resources. This can reduce infrastructure work so you can focus on developing and releasing your product.
Choose the resources your project needs now. You can adjust them as the app grows.
Create your first cloud service
Create a project, connect a Git repository or Docker image and go live without managing servers.