Why it exists
Most companies under a few hundred people run their cloud with nobody whose job it is. The bill is read once a month, security settings are checked when a customer asks, and uptime is whatever the last outage taught. The tools that cover those jobs are sold to specialists, one domain each, and each assumes someone is there to read them. MarshalCloud treats cost, security exposure and customer uptime as one problem, explains what changed in plain words with the dollar impact first, and never changes anything on its own.
Who builds it
Chandra Mohan Thakur founded MarshalCloud in August 2026 and writes all of it. There is no team page because there is no team yet. Questions about the product, security or data handling go to [email protected] and are answered by the person who wrote the code.
How it is run
MarshalCloud runs on itself: its production is composed, planned, approved and applied through the same build pipeline it offers customers, in AWS Mumbai, at published list prices. The whole run is written up stage by stage on How a build works. What it can read in your account, what it never reads, and how to revoke it are on Security and access.
The facts, in one place
- Founded
- August 2026
- Team
- Chandra Mohan Thakur, founder and the only engineer
- Built deepest for
- AWS, with Google Cloud and Kubernetes on Growth and above
- Runs on
- Its own product, in AWS Mumbai (ap-south-1)
- Contact
- [email protected]
What MarshalCloud will not claim
- A savings figure that did not come from your own bill or a provider price. Otherwise it is $0, marked low confidence.
- A passing security or uptime result over missing or stale data. That reads as unknown.
- An undo it has not tested. Rollback is stated per action, before you approve.
- A certification it does not hold. Readiness evidence is not SOC 2.