Choosing between Apps, Dedicated, and S3 plans

We ship three hosting surfaces. The decision tree for picking the right one is short, and picking wrong is expensive (over-provisioned = wasted budget, under-provisioned = downtime).

Use App Hosting (managed container hosting) when

• You’re running WordPress, ERPNext, Ghost, n8n, or any other Docker-image app.
• You don’t need custom kernel modules or raw hardware access.
• You want day-2 ops (backups, restores, TLS, monitoring) bundled. App Hosting ships all of that.
• Your traffic fits within a 0.5 vCPU / 0.5 GB to 4 vCPU / 16 GB envelope.

Use Bare Metal when

• You need full root access + your own kernel tuning.
• You’re running a stateful service that doesn’t fit a container model (custom VPN endpoint, bare database cluster, large in-memory cache).
• You need a hardware RAID for IOPS-sensitive workloads (database with > 50k qps, real-time analytics, video transcoding).
• You want full isolation from noisy neighbours.

Live SPEC tables live on the hosting pages; pricing on /pricing. The actual SKU matrix evolves as we add capacity, so the blog post sticks to the workload signals rather than snapshotting the per-SKU numbers.

Use S3 storage when

• You need object storage, not a server. (Files, images, backups, large datasets.)
• You pay per GB-month + per request. The S3 API is drop-in for any AWS SDK.
• You want the data in India, with a 99.9% SLA, and a free 5 GB starter tier.

Standard = hot tier (frequent reads/writes, ~₹0.25/GB-mo). Infrequent = cold tier (rare access, retrieval fee). Archive = archival tier (min 90-day commitment).

Mixed workloads

The most common production setup combines all three: Apps for the application tier, Bare Metal for the database, S3 for media + backups. That’s the architecture we deploy for our own internal staging environment.

Message us on WhatsApp with your workload profile and we’ll spec the right mix.