Who builds mShield
mShield is developed by the CloudKitty product team. The website operator and data controller is KAPIDATA sp. z o.o., ul. Grójecka 43/1A, 02-031 Warszawa, Poland (KRS 0000709407, NIP 7010789895). See Privacy & cookies for privacy information and contact details.
The team builds and runs the product directly. A pilot conversation is with the people who build it and can help evaluate the fit for your environment.
Why we build mShield
A dependency can execute code during installation, before a later scan identifies a problem. Teams need a way to apply their security and license policies at the point of download.
mShield adds that decision to the package request path and records the outcome. It complements the tools teams use to inventory dependencies and investigate newly discovered vulnerabilities.
How we talk about the product
Three commitments that shape what is written on this site:
- We list what works today. The ecosystem table covers what enforces now; anything still in development is not sold as if it were finished.
- The limitations are published. What mShield does not do is a page section, not something you discover in week three of a pilot.
- Statistics are sourced. The threat figures on this site link to the public research they come from; none of them are our own measurements, and none are presented as such.
mShield is pre-general-availability. Pilots are joint evaluations, and we would rather say so than imply a production track record the product has not earned yet.
Contact
Everything goes to contact@cloudkitty.pl — pilot inquiries, technical questions, security reports, and press.
For a pilot, the four things worth including will get you a scoped answer instead of a discovery call. For a security issue in mShield itself, write to the same address with “security” in the subject and we will reply before doing anything else that day.