Earn hosting income on NarwhalCloud: sizing and pricing 1-core, 128MB instances

Connect a spare server to NarwhalCloud, create small instance plans, and earn hosting revenue while maintaining the underlying machine. Our instances use 1 shared CPU core, 128MB RAM and a default 1GB disk. Each plan uses the host bandwidth with a shared uplink; monthly transfer is divided equally across the planned instance count. The memory overselling ratio is 1.5×. Start with one host and a limited inventory, then expand after validating demand and reliability.

Prices below were checked on September 10, 2026. These are provider-advertised offers, not completed purchases or tested NarwhalCloud deployments. Capacity figures are planning assumptions. Hosts set their prices based on costs and demand, and earnings depend on actual operation.

Upstream candidates

Host	CPU / RAM / SSD	Advertised price
RackNerd 2GB KVM	2 vCPU / 2GB / 35GB	$35.99/year, about $3/month
RackNerd 4GB KVM	3 vCPU / 4GB / 60GB	$59.99/year, about $5/month
netcup VPS Lite 1 G12s	2 vCore / 4GB / 80GB	€4.88/month including displayed 19% VAT
netcup VPS Lite 2 G12s	4 vCore / 8GB / 160GB	€7.92/month including displayed 19% VAT

See RackNerd Specials and netcup VPS Lite. RackNerd requires the annual payment upfront. netcup Lite uses availability-based European placement and reduced network specifications; verify the order’s term, billing cycle, IP options and applicable tax.

Hetzner’s June 15, 2026 adjustment lists CX23 at €5.49/month in Germany and Finland, excluding VAT and IPv4. Its cloud page showed the cost-optimized shared category as unavailable during this check, so confirm stock before budgeting around it.

For this use case, compare the two 4GB candidates first. Before purchasing, confirm upstream permission for container hosting and resale, sustained CPU restrictions, network limits, and actual compatibility with the Agent. Existing spare capacity is a useful way to test demand without another contract.

Additional candidates from LowEndTalk

We also reviewed recent or active LowEndTalk offers. Treat thread prices, current specifications and checkout availability separately.

Candidate	Host specifications	Advertised price, not verified at checkout	Example planned inventory
DeluxHost D-3, Germany	2 vCPU / 4GB / 60GB NVMe / shared 10Gbps	€14/year, about €1.17/month	40 if 40GB remains allocatable; RAM ceiling 48
DeluxHost D-4, Germany	2 vCPU / 8GB / 80GB NVMe / shared 10Gbps	€18/year, €1.50/month	64 if 64GB remains allocatable; RAM ceiling 96
Linveo Intel KVM 8GB, US	4 vCPU / 8GB / 50GB NVMe / shared 10Gbps	$4.07/month in its 2026 coupon offer	40 if 40GB remains allocatable; RAM ceiling 96

Inventory figures assume disk reserves and still require CPU and memory load testing. DeluxHost prices come from its August 28 provider thread. Its linked checkout did not expose readable price or stock details during this check. D-3 is the more balanced RAM-to-disk candidate; D-4’s extra RAM does not remove its CPU and disk limits.

DeluxHost’s current FUP counts inbound plus outbound traffic. Protected promotional offers have indicative review thresholds of 5–10TB, with the applicable figure determined by the plan. These are not guaranteed transfer packages. Confirm an operating transfer budget before dividing it across instances.

Linveo’s provider thread supplies code LET26INTELKVM2026. The current Ohio order page lists 4000GB for the standard 8GB plan, rather than the original thread’s 2000GB: divide by 40 to allocate 100GB per instance, with 10000Mbps shared bandwidth. Checkout discount pricing was not exposed. Do not automatically double the current allowance again. The provider confirmed on August 27 that Arizona is no longer offered; current entries are Ohio and Texas.

Other offers remain watchlist items:

• servaRICA FAT Slice 4 now shows $10/month, 4 dedicated cores, 8GB RAM, 120GB NVMe and zero stock in the store, compared with $8 in its launch thread.
• Fourplex advertises a 4GB/40GB NYC plan at $6/month, but disk limits density, sustained network use is subject to fair use, and the checked order link redirected to another product category.
• DartNode’s August 28 offer included a 24-hour $30/year 4GB/100GB flash deal. Its deals page did not expose a current price during this check, so exclude that promotion from a current purchasing budget.

Prioritize verifying DeluxHost D-3 stock and terms for a low annual cost, or Linveo 8GB checkout pricing for a monthly trial. Neither has been tested here for NarwhalCloud compatibility or confirmed resale permission.

Define the product clearly

Use Podman for this 128MB example; see the Agent installation guide. The current cloud-hypervisor plan minimum is 256MB.

Setting	Configuration
CPU	1 shared core, light workloads
RAM	128MB
Disk	1GB by default
Bandwidth	Same as the host; for example, 1000Mbps on a 1000Mbps host, with a shared uplink
Monthly transfer	Host monthly allowance divided by planned instance count, rounded down to whole GB
Memory overselling	1.5× the host reported total RAM
IPv4	Shared NAT with port forwarding
IPv6	Describe only what the host actually provides
Monthly price	Compare similar plans and allow for host costs, commission and maintenance

A shared core is not a dedicated physical core or permission to run continuously at full CPU usage. Twelve containers on a 3-vCPU host still share that host’s capacity.

Test the offered image and application at 128MB before advertising compatibility. Small probes and low-memory utilities are potential uses; browser automation, large databases and builds need larger plans. Explain NAT, available forwarding rules and shared public ports in the listing. See the NAT VPS guide.

Budget capacity before listing inventory

Use 1024MB per GB of RAM for illustration and substitute the actual Agent-reported total. The current capacity check applies 1.5× directly to total reported RAM:

RAM-only count = floor(host total RAM in MB × 1.5 / 128)
Disk count = floor(allocatable instance data space in GB / 1)
Planned count N must fit RAM allocation, disk, ports and measured CPU capacity.

Per-instance bandwidth = host bandwidth (shared uplink)
Per-instance monthly transfer in GB = floor(host monthly allowance in GB / N)

Host RAM	Allocatable RAM at 1.5×	Theoretical 128MB count	Total default instance disk quota
2GB	3GB	24	24GB
4GB	6GB	48	48GB
8GB	12GB	96	96GB
16GB	24GB	192	192GB

These are allocation ceilings. Overselling does not increase physical RAM, and the OS, Agent and container overhead still consume real resources. Do not count swap or zram as additional sellable capacity beyond this calculation.

A 4GB host allows 4096 × 1.5 / 128 = 48 allocations by RAM. On a 60GB disk, allow space for the OS, images, logs and maintenance. If only 40GB remains allocatable to instances, budget 40 instances, each with the default 1GB disk. Use 48 only when disk capacity and measured load permit it. Check the actual Podman data-disk allocation too.

Observe peak-hour CPU usage, steal time, available memory, OOM events, disk I/O and tickets for one or two weeks. Open inventory gradually, but divide transfer by the final planned count from the outset so that expansion does not require reducing existing plan allowances.

For a 1000Mbps host with a 7000GB monthly allowance and 40 planned instances, each plan receives 1000Mbps shared bandwidth and 175GB monthly transfer. At 48 instances, round 7000 / 48 down to 145GB each, allocating 6960GB and leaving 40GB from rounding. This assumes the actual allowance is 7000GB; convert upstream units correctly rather than mixing TB and TiB.

Each instance shares the host uplink: identical bandwidth settings do not create independent dedicated connections. Transfer is divided by planned inventory, not the current sold count. If an upstream offer merely says transfer is included, confirm its allowance and fair-use rules before setting a budget. Monitor host traffic and metering differences as well.

Set prices and assess earnings

Plans are priced in USD, and NarwhalCloud charges a 20% commission. For external payout planning, start with roughly four-fifths of hosting revenue after refunds, then deduct host costs, receiving-channel fees and maintenance. Channel fees are separate from platform commission; do not deduct the commission twice.

Approximate operating surplus ≈ hosting revenue after refunds × 80%
                                - host costs - channel fees - operating expenses

Convert upstream costs at the exchange rate actually paid. Annual rent can be spread across months for comparison, but the annual payment is still due upfront.

With the same 1-core / 128MB / 1GB configuration, host bandwidth and equally divided transfer, pricing depends mainly on location, network quality, transfer allowance and procurement costs. Compare similar regional plans on the marketplace, leaving room for commission and ongoing maintenance. Verified network advantages or scarce locations may support higher prices.

Early orders may only offset part of the host bill. Stable occupancy and renewals can improve cost recovery and leave a surplus, but realized discounts, refunds and support work affect the outcome. Compare scenarios with low occupancy, roughly half the inventory rented, and most inventory rented; do not assume a full host or a fixed payback period.

Use actual orders to adjust prices and inventory. For promotions, limit usage and duration, and check whether discounted renewal pricing persists. Continuing discounts should remain affordable after the initial sale.

Connect and publish

1. Open the Hosting Center, add your host with accurate location and network details, and obtain its Agent Token.
2. Follow the installation guide, select Podman for this example, enter the token in the local Agent panel, and confirm online status and reported resources.
3. Create a plan with CPU 1, RAM 128 and disk 1. Set bandwidth to the host bandwidth and divide its monthly transfer by planned inventory. The 40-instance example uses 1000 Mbps and 175 GB; set the price based on costs and comparable plans.
4. Start with a maximum quantity such as 8. Zero means unlimited. Combine all plans and existing instances when calculating host capacity.
5. Verify creation, boot, SSH, DNS, forwarding, restart, deletion, resource limits and metering before promotion.
6. Track renewals, utilization and tickets before increasing inventory. When using promotions, check usage limits, expiry and whether the discounted renewal price persists.

Revenue and withdrawals

Estimated monthly revenue is not immediately withdrawable cash. Review escrow, locked and available amounts and use the withdrawal preview. The platform charges 20% commission, with receiving-channel fees borne separately by the recipient. Internal balance transfers are also available; check their fee preview, and use external payout terms when forecasting cash income.

Hosting rules require timely support, accurate descriptions and reasonable allocation. Hosts offline for 24 hours may be retired; inability to continue service can require clearing affected instances at twice their remaining value. Consult current console rules and retain a separate fault and retirement reserve based on the remaining value of hosted instances.

Before leaving, stop new sales and arrange the remaining instances’ exit and renewal boundaries. Add another host only after the first one demonstrates stable service, demand and enough revenue to cover its real costs.