Paladin Cloud addresses that immediate, substantial challenge by identifying and eliminating blind spots in a company’s cloud environment and solving that with an open-source, security-as-code platform for developers and security teams.
The generic “we provide a security platform where one size fits all” approach no longer works. Each cloud, each system, and each cloud-hosted platform, codebase, and application comes with its own set of vulnerabilities. With many enterprises accelerating their move to the cloud, “a holistic approach” to cloud security is the only way to ensure real protection for business assets. And Paladin Cloud’s founders wanted to deliver just that with a powerful and impactful security solution, where it’s open-source genesis would be its most incredible strength.
After Paladin Cloud raised its Seed funding, our engagement focused on helping them with their product innovation:
The founding team had a clear vision to ensure that the time to value should be kept as minimal as possible. We worked with the founding team to create methodologies to ensure that users would be able to complete the installation and start securing their cloud in under 60 minutes.
We helped Paladin Cloud expand on its plugin-based architecture. The objective was to make its core adaptable and extensible to prepare not just for a variety of use cases, but to easily integrate with a company’s multi and hybrid cloud product strategy that would extend into an enterprise SaaS solution.
We helped develop proper documentation in and outside the repository as it plays a crucial role in driving adoption for an open-source project. Documentation minimizes the time spent on addressing fundamental questions from the community so that engineers could focus on larger issues raised. In partnership with the Head of Developer Success, WiKi and user guides became a critical feature of the product and an essential area of collaboration.
We also collaborated with the Paladin Cloud team to encourage community interactions and discussions. We used Gitter, Slack, and GitHub to encourage feedback and work on improvements.
We supported Paladin’s team to set up pull requests and issue templates with pre-populated information. These helped users capture the appropriate information about an issue quickly, and helped us resolve them faster.
As part of the deliverables, we also co-generated a CONTRIBUTING.md file with information for the community about any development/release standards that they should be following. This provided clarity to the users and helped align on best practices being followed in the repository.
We worked with the customer team to create branching strategies that defined how they plan to release particular versions of their solution. This helped users prepare for what’s to come and plan their usage. During every new release, the team ensured that they highlighted the changes made for the new release to mitigate surprises.
An intelligent Continuous Integration/Continuous Deployment (CI/CD) pipeline is non-negotiable for any product. We use it to ensure shorter feedback loops and to steadily make progress on product development milestones. It helped avoid long pull request times and having to manually test each community-raised pull request before we process it, streamlining development even more.
©2023 Zemoso Technologies. All rights reserved.