Our NCloud plan environment tiers (Starter, Pro, and Team) are engineered to deliver premium agility and performance to modern developers and corporate teams. Instead of measuring performance with legacy web hosting metrics, the IMOMA TECH cloud architecture monitors consumption using two key operational attributes: Concurrent Apps and Build Minutes.
Below we break down how each of these performance metrics operates so you can optimize your cloud ecosystem efficiently.
1. What are Concurrent Apps?
This operational threshold dictates the maximum volume of standalone projects or isolated containers you can maintain live and active simultaneously inside your account dashboard. Every single decoupled deployment module isolates as one distinct app. For instance:
- 1 Node.js / Next.js live production website = 1 App
- 1 Dedicated PostgreSQL database container = 1 App
- 1 Containerized WordPress instance = 1 App
If your assigned tier allows 3 Concurrent Apps (such as our NCloud Starter tier), you can retain up to 3 individual processes online together. If your team scales out a fourth deployment item, you must terminate a legacy container or upgrade your overall cloud tier.
2. What are Build Minutes?
Whenever you push fresh code adjustments to your repositories (via GitHub, GitLab, or raw upload structures) and our cloud pipelines download, compile, pack, and serve the updated layout, the task uses high-performance infrastructure engines. The total processing clock time spent compiling your code is tracked as Build Minutes.
- Your allocated Build Minutes tier ledger **resets completely every month** on your exact subscription anniversary date.
- Only active packaging workflows drain this balance. The time window your website spends online running and responding to visitors does not consume your Build Minutes quota.
If your monthly build balance reaches zero, your production apps that are currently online will remain active and fully functional with zero service downtime. However, you will be unable to run fresh deploys (code updates) until your next billing cycle clears, unless you purchase an unmetered build addon block or perform an automated upgrade to a higher tier (Pro or Team).
Best Practices to Optimize Your Build Minutes Allocation
- Restrict Continuous Deployment Branches: Map your dynamic Git webhooks to execute automated deployment routines strictly on production target branches (e.g.,
mainormaster) and review tests locally inside dev environments first. - Prune Heavy Package Files: Architecting lean dependency trees and caching configurations guarantees fast, agile code builds on our compilation instances.
