Authors & Editorial Team
Meet the people and editorial roles behind getInfra.cloud's cloud pricing research, provider profiles, comparison pages and India-focused infrastructure guides.
Who Creates getInfra.cloud Content?
getInfra.cloud publishes cloud pricing comparisons, provider profiles, GPU cloud research, buyer guides, and India-focused infrastructure notes. This page explains who prepares that content, which editorial roles support the work, and how information is checked before publication.
Cloud infrastructure decisions require clear, reliable, and accountable information. The author and reviewer information below helps readers understand the experience behind the research, the source review process, and the limits of each published comparison.
getInfra.cloud lists named contributors where appropriate, but the page is designed as a platform-level trust page. Public profiles support author transparency; pricing and provider claims are still checked against official provider sources, methodology rules, and correction workflows.
Editorial Roles Behind the Platform
The author page should not read like a personal portfolio. It should show a clear editorial structure. These are the roles used across getInfra.cloud content.
Lead Author
Prepares the main explanation, page structure, provider summaries, comparison notes, and buyer-focused guidance.
Pricing Research
Checks official pricing pages, calculator outputs, plan specs, GPU rates, currency assumptions, and source dates.
Editorial Review
Reviews clarity, neutrality, source labels, disclaimers, provider influence risks, and correction requirements before updates go live.
Lead Author
Daya Shankar
Lead Author & MaintainerDaya Shankar contributes as the lead author and maintainer for getInfra.cloud. His background as a developer, AI and machine learning enthusiast, and cloud infrastructure researcher helps shape the platform's pricing comparisons, provider profiles, GPU cloud notes, and India-focused buyer guides.
His profile is included for transparency, but getInfra.cloud content is not based on personal preference. Provider and pricing claims are checked against official sources, review rules, and correction processes documented across the site.
Public author profiles
Portfolio Website
heydaya.github.io
Personal portfolio and project hub used as a public identity and developer background signal.
GitHub
github.com/heydaya
Public code profile supporting developer background and technical project visibility.
Medium
medium.com/@daya-shankar
Technical writing profile connected to cloud, GPU, Kubernetes, storage, scaling, and infrastructure topics.
Hugging Face
huggingface.co/daya-shankar
AI community profile used as a signal of interest in AI, LLM tools, and open-source model activity.
Quora
quora.com/profile/Daya-S-50
Public Q&A profile included for broader author identity and community presence.
X Profile
x.com/ImdayaOfficial
Public social profile for author discovery, professional presence, and occasional updates.
Relevant Expertise Areas
getInfra.cloud covers cloud providers, pricing, GPUs, storage, data centres, and managed services. These expertise areas combine developer experience, technical publishing, AI/ML interest, source review, and practical cloud research workflows.
Cloud Infrastructure Research
Comparing VPS plans, GPU instances, storage categories, bandwidth, regions, billing models, and provider-level differences.
GPU and AI Workloads
Researching H100, H200, A100, L40S, inference workloads, model training needs, and GPU cloud pricing trade-offs.
Web Development
Developer background helps with page structure, front-end implementation, data presentation, UX clarity, and technical explainers.
India-First Cloud Context
Focusing on INR pricing, India data centres, Indian provider availability, startup use cases, and local buyer concerns.
Editorial Responsibilities
| Content Area | Responsibility | Supporting Page |
|---|---|---|
| Pricing tables | Collect plan details, verify official sources, normalise specs, apply INR conversion notes, and flag uncertain pricing. | Methodology |
| Provider profiles | Summarise services, regions, GPU availability, data centre coverage, strengths, watch-outs, and source limitations. | Data sources |
| Buyer guides | Explain infrastructure buying decisions in plain language without pushing any provider unfairly. | Editorial policy |
| Corrections | Review reported issues, verify evidence, update affected pages, and log meaningful pricing changes. | Corrections |
Review Process Before Publishing
Source check
Research starts with official provider pages, pricing calculators, public product documentation, region pages, press releases, or provider support responses.
Comparison normalisation
Plan details are converted into a consistent comparison format, including vCPU, RAM, storage, bandwidth, currency, region, and billing model.
Technical and editorial review
The page is checked for unclear labels, outdated assumptions, exaggerated claims, missing disclaimers, and provider influence risks.
Publish and monitor
After publishing, pages are monitored through scheduled updates, reader feedback, provider correction requests, and periodic changelog reviews.
Bylines and Reviewer Labels
Every important pricing page, provider page, and buyer guide should show who created it, who reviewed the data, and when it was last updated.
Written by
Use this for the person who prepared the main content, explanation, and page structure.
Data reviewed by
Use this for the check against pricing pages, source links, regions, and provider specifications.
Last updated
Use this for the latest meaningful content, source, pricing, or methodology update.
Written by Daya Shankar ยท Data reviewed against official provider sources ยท Last updated June 2026 ยท Methodology: getInfra.cloud/methodology/Provider Influence Rules
Cloud providers can help correct factual errors, but they cannot control rankings, comparison labels, verdicts, or editorial conclusions.
Allowed
- Submitting updated official pricing links
- Reporting incorrect plan specifications
- Sharing public product documentation
- Clarifying region or data centre availability
- Requesting trademark or naming corrections
Not allowed
- Paying for higher placement
- Removing accurate competitor comparisons
- Editing final verdicts directly
- Replacing methodology with marketing claims
- Asking for hidden sponsorship or affiliate treatment
Contact the Editorial Team
Use the editorial contact for author questions, correction requests, provider source updates, missing attribution, or unclear methodology notes.
Report a data issue
Wrong price, stale plan, missing source, or unclear provider data.
[email protected]Author or contributor update
Send updated bios, contributor links, credentials, or publishing history.
[email protected]Editorial concern
Raise concerns about bias, attribution, ranking labels, or unclear methodology.
[email protected]Public profiles are included as author transparency signals, not as substitutes for source verification.
Review how getInfra.cloud handles sources, methodology, corrections, and editorial independence.
Methodology โEditorial Policy โ