For a five-to-fifty-crore Indian business running custom software, the hosting choice is overdone. When a 1500-rupee VPS wins. When AWS wins. When Vercel wins.
By Mohammad Jamnagarwala · Simply Five Studio
A founder running a forty-crore distribution business in Coimbatore asked us last quarter whether his custom ERP should be on AWS. The question came from a conversation with a friend whose startup was on AWS, and who had said it as if AWS was the default for any serious business. The founder's current system runs on a single VPS that costs him around 1800 rupees a month, has been up for two and a half years without incident, and absorbs roughly 400 daily users without breaking a sweat.
We told him to stay where he was.
The hosting decision is one of the most overdone conversations in the custom-software space, mostly because the decision is framed as if the options were tiers of seriousness rather than choices that fit different operating profiles. A VPS is not a less-serious AWS. They serve different needs. Same for Vercel.
A Hetzner, Hostinger, or DigitalOcean VPS at one to three thousand rupees a month wins for the vast majority of mid-market Indian business applications. The reason is operational fit, not cost.
A business doing five to fifty crore in annual revenue, running a custom ERP, a customer portal, a vendor portal, and a couple of operational dashboards, typically generates somewhere between 200 and 2000 daily active users. The application is read-heavy with periodic write bursts during peak operational hours. Data volumes are manageable, in the low tens of gigabytes for the first few years. Compute requirements are well below what a modern VPS provides.
The AKSD distributor system runs exactly this profile. Three years of operational data, customer-facing storefront, internal ERP, WhatsApp notifications, PDF generation, mail server, all running on a single self-hosted VPS at modest cost. The system has absorbed every increase in volume the firm has thrown at it without requiring infrastructure upgrades.
The hidden advantage of the VPS path is operational simplicity. One machine. One database. One backup script. One deployment pipeline. The engineering team understands the entire stack. When something breaks, the path to diagnosis is short. The essay on PHP as a deliberate choice covers the related point that the right technology for the project depends on the project, not on what is fashionable.
The cost math is incidental. A 1800-rupee VPS versus a 35,000-rupee AWS bill for the same workload sounds like the headline. The real difference is the cognitive load on the team running the system. The VPS asks the team to understand one stack. AWS asks the team to understand a constellation of services, each with its own pricing model, each with its own failure modes.
For an Indian mid-market business where the engineering team is the firm's technology partner running a few systems across multiple clients, the VPS path keeps the operational burden inside what the team can carry confidently. This is the right answer for most engagements.
AWS wins when the application's operating profile genuinely needs what AWS provides, which is rarer than the marketing suggests.
The CFX multi-tenant ERP we built for three cutting-tool manufacturers in Mumbai runs on AWS. The decision was deliberate, and based on three specific operational facts.
The first was multi-tenant scale. Three brands, multiple regions of customer activity, a native Android client base used in the field, and an operational tempo that included peak load during quarter-end and year-end. The workload had genuine variability that a vertically scaled VPS would have struggled to absorb without over-provisioning.
The second was the breadth of operational tooling AWS provides. Managed Postgres with point-in-time recovery and automated backups. Managed file storage for the artifact-heavy quote PDFs. Managed certificate rotation. Managed DNS. Each of these would have been a separate operational responsibility on a VPS. On AWS, they are configuration.
The third was regulatory and audit comfort. A three-brand group at mid-market enterprise scale has external auditors, insurance underwriters, and customer compliance reviews that ask questions about hosting. AWS answers those questions in a standard form that the auditors recognise. A self-hosted VPS answers them too, but with more friction.
The AWS bill on CFX is materially higher than a VPS bill would have been. The bill is the right cost for the operational profile. The mistake is paying it when the profile does not require it.
The threshold for AWS, in practice, is when the application crosses into genuine multi-tenant complexity with variable load, when the operational tooling demand starts to consume meaningful team time on a VPS path, or when the audit and regulatory environment requires the managed-service stack AWS provides. Below that threshold, the VPS path is the better engineering decision.
Vercel wins for a narrow but real category: marketing sites, content sites, and customer-facing front-ends where the deployment workflow, the preview deploys per commit, and the edge CDN are the primary operational value.
A founder-led firm's marketing website, the customer-facing storefront for an ecommerce business with global edge requirements, a customer portal that benefits from per-region edge serving, all fit Vercel's sweet spot.
What Vercel does not fit is the operational backend of the business. The ERP, the workflows, the dashboards the team works in. Vercel's pricing model and architectural assumptions are wrong for that use case. The cost climbs sharply at modest usage. The serverless model adds latency that internal operational users experience daily.
The right architecture for an Indian mid-market business using Vercel is hybrid: Vercel for the customer-facing surface, a VPS or AWS for the operational backend, the two integrated through clean APIs. This shape appears in some of our newer engagements, including the essay on the SaaS-versus-custom-build math, where the comparable point about platform fit applies.
The hosting decision should follow from three operational questions.
What is the application's daily active user count and the load pattern? A 400 DAU system with predictable load is in VPS territory. A 4000 DAU system with variable load may need AWS.
What operational responsibilities does the team running the system have the bandwidth to carry? Managed services cost money. Self-hosted services cost time. The team's actual capacity decides which trade is right.
What is the audit, regulatory, and customer-trust environment the system operates in? Some environments expect the managed-service answer. Others do not care, as long as the system is reliable.
The internal systems engagement model defaults to VPS for most mid-market builds, with AWS for the engagements where the operational profile genuinely requires it, and Vercel where the customer-facing front-end has the specific characteristics that fit.
The choice is engineering, not fashion. For an Indian mid-market business, the right answer is usually less infrastructure than the internet would have you believe. Start a Conversation.
Every Indian B2B founder running customer messaging on WhatsApp eventually asks the same question. The honest answer is technical, not a sales pitch, and it depends on a few specific factors most BSP comparison pages skip.
Seventy percent of AI-in-ERP marketing is window dressing. The thirty percent that pays back lives in unstructured-input parsing, anomaly detection, and drafting outbound responses.
Imported booking SaaS does not understand UPI, member tiers, court-specific rules, no-show penalties, or family memberships. A fitted system for Indian sports clubs and academies.
The contact form takes about two minutes. The reply comes from the founder within two working days.
