CloudNative, Inc Security Policy

Security at CloudNative, Inc is not only an ethical obligation, but your trust in our competence in this area is crucial to the sustainability of our business. We appreciate you taking the time to read this page along with Terms of Service and other pages on the website that constitute our Legal Terms. We will update these pages from time to time, so it is important that you check back regularly to ensure you still agree to these terms, before using the service.

We do not read your code!

CloudNative employees want your business to thrive, while using the CloudNative service, so privacy and security of your code is of the highest importance. Currently, only the Founders of CloudNative have the ability to read any of your code and would only ever do so in response to an explicit support request from your company. Contractors of CloudNative will never be given access to customer code.

Partners with access to your source code

CloudNative is built using Amazon Web Services, and we check out your code onto an EC2 instance in your AWS account. If AWS becomes vulnerable, your source code may also become vulnerable to accidental disclosure. The AWS Security Center discusses their security in great detail.

Canceling your account

If you need your account canceled and your data deleted, please contact us at To remove CloudNative's access to your GitHub account, you can remove it via your GitHub application settings page.

Our security model

Your code is only downloaded and executed on your servers. When building an AMI, CloudNative makes API calls to your AWS account to set up a build server. The build server, running in your AWS account, then downloads your code from your Git repository, as well as makes more API calls to your AWS account. This model makes certain that no customer ever has access to any other customer's code.

CloudNative, Inc. Responsible Disclosure Policy

We take the security of our systems seriously, and we value the security community. The responsible disclosure of security vulnerabilities helps us ensure the security and privacy of our users.

Guidelines to Responsible Disclosure

We require that all researchers:

  • Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction of data during security testing,
  • Perform research only within the scope set out below,
  • Use the identified communication channels to report vulnerability information to us, and
  • Keep information about any vulnerabilities discovered confidential between the researcher and CloudNative, Inc. until we’ve had 90 days to resolve the issues.

If you follow these guidelines when reporting an issue to us, we commit to:

  • Not pursue or support any legal action related to your research,
  • Work with you to understand and resolve the issue quickly (including an initial confirmation of your report within 72 hours of submission), and
  • Recognize your contribution on our Security Researcher Hall of Fame if you are the first to report the issue and we make a code or configuration change based on the issue.



Out of scope

Any services hosted by 3rd party providers and services are excluded from scope. These services include:

In the interest of the safety of our users, staff, the Internet at large, and you as a security researcher, the following test types are excluded from scope:

  • Findings from physical testing such as office access (e.g. open doors, tailgating),
  • Findings derived primarily from social engineering (e.g. phishing, vishing),
  • Findings from applications or systems not listed in the ‘Scope’ section
  • UI and UX bugs and spelling mistakes, and
  • Network level Denial of Service (DoS/DDoS) vulnerabilities

We do not want to receive:

  • Personally identifiable information (PII) or
  • Credit card holder data

How to report a security vulnerability?

If you believe you’ve found a security vulnerability in one of our products or platforms, please send it to us by emailing Please include the following details with your report:

  • Description of the location and potential impact of the vulnerability,
  • A detailed description of the steps required to reproduce the vulnerability (POC scripts, screenshots, and compressed screen captures are all helpful to us), and
  • Your name/handle and a link for recognition in our Hall of Fame.

If you’d like to encrypt the information, please use our security team's GPG key (ID: 0x2042926F, fingerprint: 55AA 9C76 54E8 1BFB 8144 4F8E DADF EA12 2042 926F).