Home / About
About
MDCS designs and deploys cloud platforms, tests and defends them, operates them day to day — and builds the applications and integrations that run on them. That is a narrower claim than most firms our size make, and every part of it is something we do in production.
Two things we do deeply, rather than nine things we list.
MCloud and DDMS are our own, built by our own practice.
With OEM service backup, and not limited to them.
AWS and Oracle Cloud run internally as well as for clients.
References
Three environments in three operating contexts — public sector, overseas commercial and domestic enterprise. Working across three governance regimes is a different exercise from running one estate well.
| Context | What we are responsible for | Scope |
|---|---|---|
| State government \u00b7 India | IT management services for a state data centre environment. | Managed operations |
| Education \u00b7 United States | Design and management of the AWS infrastructure behind a live education platform. | Cloud platform |
| Enterprise EPC \u00b7 India | The full digital workload \u2014 infrastructure, applications, operations and security for a national contractor. | Every practice on this site |
Named references are available on request. The third is the one worth asking about: one organisation, every practice on this site, which is the practical answer to whether a company can cover all of this.
How we work
When public cloud is cheaper for your workload, when a review will find nothing, when the platform you have is fine. It is on the pages, not just in the meetings.
We prepare you for ISO 27001, SOC 2 and the rest, and close the gaps. An accredited body issues the certificate. No consultancy can do both.
Every security finding is retested and formally closed or reopened. A report is not the end of an engagement here.
The limits are on the website,not saved for the third meeting.
A deliberate omission
We sell the company’s capability, not an individual’s. People move between roles and between employers; the organisation, its documentation and its obligations do not. Every engagement is delivered by MDCS and accountable to MDCS, whoever is on the call.
If you want to meet the engineer who would run your estate before you commit, ask. That is a reasonable request and we will arrange it.
Our own posture
MDCS infrastructure is independently penetration tested. Ask for the summary and we will share a redacted copy under NDA. A security practice that has never had its own estate tested is asking you to accept something it has not accepted itself.
Describe what is happening in your own words. We will tell you which of this is relevant and which is not.
An engineer replies within two business days.
Partner, not tied
MDCS holds partnerships with Nutanix, HP and Dell, with OEM service backup. That is accredited capability rather than a restriction — and it cuts both ways.
We deploy proprietary hyperconverged platforms as an accredited partner. When we recommend Apache CloudStack it is a recommendation, not the only thing on the shelf.
We will specify a platform we hold no partnership with when that is the right answer, and we take no margin on hardware in any case.
We write what you need — sizing, model, licensing — and you buy it from whoever you like. That removes the suspicion that a design was written to sell boxes.
Accreditation tells you we can build it. It should not tell you what we will recommend.