NewAuto-Scaling 2.0

Cloud hosting.Limitless scale.

Deploy a release. Raise traffic. Watch your infrastructure respond.

Explore dashboardSee How It Works

No signup · Runs in your browser

Ctrl KGo anywhere. Run any action.
app.nimbuscloud.my / overview

Sample data

Overview

All operational
CPU

60.0%

Average across 4 instances

MemoryAllocated

1.6GB

4 GB available

TrafficIncoming

240req/s

Updates once per second

Network activity

Latest 60 samples
Static
A live sample traffic chart. Current incoming traffic is 240 requests per second.

Hover to inspect. Keyboard: focus the chart, then use ← and →.

Sample traffic is 240 requests per second. Four instances are active.

Active servers

3 regions shown

Generated in your browser. Deploy actions do not create cloud resources.

Sample platform figures

Sample data
Uptime
99.99%
Data centres
12
Regional latency
<20ms

Illustrative figures for a fictional service. They are not production measurements.

Six tools. One control plane.

Inspect the details.

Open a row, change a setting and follow the result in the dashboard. Each micro-visual uses the same sample application state.

Fast DeployClone, build, test and release to three sample regions.

The deploy sequence streams its progress into the dashboard. Successful runs add a server row and increase sample traffic.

Auto-ScalingAdd capacity above 70% CPU. Scale down below 30%.

A four-second cooldown stops the instance count from changing too frequently. Traffic, cost and latency respond to the current capacity.

Adjust traffic load
Layered SecurityInspect TLS, firewall and access-policy settings.

These switches change a sample policy checklist. They do not inspect your device or configure a real network.

Sample policy

3 of 3 sample policies enabled.

Automatic BackupsCreate and inspect a local snapshot record.

Snapshot records stay in page memory. No files are read, copied or uploaded.

No snapshot records yet.

    Real-time MonitoringInspect a rolling window of 60 traffic samples.

    The chart supports pointer inspection and keyboard navigation. CPU warnings appear above 80% utilisation.

    Inspect the live chart
    24/7 SupportPreview a support request without sending a message.

    This fictional plan includes round-the-clock support. The form below validates a request locally; no support team is contacted.

    From commit to global

    Follow one change
    through the system.

    Scroll through the release path. The visual follows each stage, from a Git push to a traffic spike.

    Release traceSample data

    01 / Source

    git push origin main

    Commit received. Build queued.

    Stage 1 of 4: source received.

    1. Push a commit.

      The repository event identifies the application, commit and target environment. No manual server access is needed.

      git push origin main

    2. Build and verify.

      Resolve dependencies, compile the application and run checks. Failed checks stop the release before traffic changes.

      build → test → package

    3. Release to regions.

      The sample release moves to Singapore, Frankfurt and San Francisco. The previous version stays available until checks pass.

      SIN · FRA · SFO

    4. Respond to demand.

      A traffic spike increases CPU load. The scaling policy adds instances, waits for its cooldown and checks demand again.

      Try the scaling controls

    Capacity, under your control

    Give the system
    some work.

    Move the traffic slider or trigger a 10× spike. Watch the same instance count and CPU values update in the dashboard.

    240 req/s

    Arrow keys: one step. Shift + arrow: ten steps.

    Active instances
    4
    Average CPU
    60%
    Sample latency
    17ms
    Estimated hourly cost
    RM0.48

    Instance pool

    Within capacity

    Instance 01 is active. Sample capacity: 100 requests per second.

    Scaling events

    1. Sample workload initialised. Four instances are active.

    One release. Multiple regions.

    Put the response
    closer to the request.

    Inspect eight sample regions. Focus a node or choose its button to view latency and availability. All network values are sample data.

    Sample data
    Eight sample cloud regionsSan Francisco, New York, London, Frankfurt, Mumbai, Singapore, Tokyo and Sydney. Nodes support Enter, Space and arrow-key navigation.

    Public APIs. Real responses.

    Check the infrastructure.

    Current service health from the official Vercel, GitHub and Cloudflare status APIs. Each response keeps its source and check time.

    Status loads when this section is visible.

    • Vercel

      Not checked

      Waiting for the official status response.

      Source

    • GitHub

      Not checked

      Waiting for the official status response.

      Source

    • Cloudflare

      Not checked

      Waiting for the official status response.

      Source

    Refreshes every 60 seconds while visible. Provider statuses come from public APIs; dashboard metrics use sample data.

    Predictable resources. Visible costs.

    Start with a plan.
    Check the numbers.

    Compare the sample plans, then change the resource inputs below. Annual billing applies a 20% discount.

    Sample plans · no charges

    Starter

    A place to start.

    For a small project and a first deployment.

    RM0/month

    Free sample plan.

    • 1 instance
    • 1 GB storage
    • Community support

    Pro

    Recommended

    Room for the next release.

    More capacity, automatic scaling and priority support.

    RM79/month

    RM79 billed monthly.

    • Up to 10 instances
    • 100 GB storage
    • Auto-scaling and priority support

    Enterprise

    Define the requirements.

    A sample configuration for larger workloads.

    Contact us

    Custom capacity and service terms.

    • Custom resource limits
    • Dedicated account contact
    • 24/7 support with SLA

    Resource calculator

    Price the workload.

    Reference rates are defined in one JavaScript object. Nothing is purchased.

    3
    100 GB
    3 TB

    Estimated monthly cost

    RM103.45

    Monthly reference price.

    Compute
    RM36.00
    Storage
    RM34.65
    Bandwidth
    RM7.80
    Support
    RM25.00

    Sample rates only. Annual billing discounts each component by 20%.

    No paid demo plan selected.

    A readable release trace

    One command.
    Every stage visible.

    This sample session types a deployment trace. It repeats only while visible, and pauses when the tab is hidden.

    terminal / nimbus-cliSample data
    nimbus deploy my-app

    Portfolio sequence. No Git command is executed.

    Sample trace: clone repository, build application, run checks and release to three example regions. Use Pause session to stop the loop.

    Before the first deploy

    Know what happens
    when you click.

    The interface works in your browser. Cloud accounts, payments and support services are not connected.

    The portfolio sequence completes in a few seconds: clone, build, test and release. A real build would depend on source size, dependencies, tests and the selected regions.

    Your next action

    Run your
    first deploy.

    Try the signup interaction, then explore the dashboard. This is a portfolio demo; no account is created.

    Navigation

    Get Started

    Command palette

    Preparing available actions.

    ↑↓NavigateEnterRunEscClose

    Confirm action

    Reset the selected plan?

    This returns the local demo plan to Starter. No account or subscription is changed.

    Preview a support request.

    This form validates locally. No message is sent to a support team.

    Your text stays in this form until it is closed.