Infrastructure
Hosting & platform packages
Enterprise-style transparency for mid-market budgets: capacity you can explain in a board deck, adjust through a client portal, and align with engineering reality—not hidden quotas or mystery “plans.”
Pricing philosophy
Large integrators and cloud marketplaces often price infrastructure in ways that require a FinOps team to decode. We publish RAM, CPU, and storage in plain terms so you can map packages to expected concurrent users, API throughput, or batch windows—and subscribe or change tiers from your eRevolutions dashboard when your product roadmap demands it.
Reference formula: ₹3,000/month baseline = 1 GB RAM + 100 GB storage + 4 vCPU. Each additional ₹1,000/month adds +1 GB RAM and +50 GB storage. Listed packages below are ready to subscribe once you create a client account.
Typically included
- ✓Transparent capacity sizing in RAM, vCPU, and storage—so engineering and finance share one model
- ✓Upgrade and downgrade paths through the client portal as traffic or batch workloads shift
- ✓Suited to public sites, API backends, and modest product footprints—not opaque “unlimited” promises
- ✓Engineering access for architecture reviews when you approach tier limits or need custom sizing
Loading packages…
Beyond standard tiers
If you need dedicated capacity, multi-environment setups (dev / staging / production), or compliance-oriented segregation, we scope a custom package with the same transparent vocabulary— then document it in your portal subscription record.
Discuss custom infrastructure →Frequently asked
- How does this compare to hyperscaler raw VMs?
- Our tiers bundle capacity with an operational relationship: you get predictable sizing language, portal-based subscription management, and a direct line to the same team that builds your software—useful when you want integrator-style accountability rather than self-serve infrastructure-only contracts.
- What if we outgrow a standard tier?
- We step you through the next tier or a custom quote (RAM, storage, CPU, and SLA-style expectations). The goal is to avoid emergency migrations by planning headroom with you.
- Do you support production SLAs?
- Commercial SLAs are agreed per engagement. Packages describe capacity; contractual uptime and response targets are finalized when we understand your workload and risk profile.