Introduction Here at Kloudless, we often find that companies benefit from our Unified APIs’ ability to provide integration for many different services at once. By coding once and integrating with multiple APIs, developers can skip the tedious process of combing through documentation, testing, and having to manually update their code so it plays well with other APIs in the future. This last reason can be especially important to a company when they’re looking to integrate their product with a single service that only Kloudless provides connectivity to. Perception Point is a recent customer who found great success by leveraging Kloudless for their service’s connectivity. The Company Perception Point offers threat detection for the digital-first enterprise. In practical terms, they protect email, messaging, cloud storage and any content-exchange channel from APTs (advanced threats), phishing, BEC (social-engineering) and malware. Chief Information Security Officers (CISOs) appreciate Perception Point’s next-generation offering because it enables them to protect against multiple threat vectors, across multiple channels within one holistic solution. This enables them to work more efficiently while being more secure, especially as they move to the cloud. The Challenge Perception Point needs access to the content itself in order to scan for threats. And that content lives across a myriad number of services, whether it consists of files in a cloud storage tool or customer records in a CRM system. For this reason, integration with popular cloud services is crucial to Perception Point’s ability to deliver on its promise. As VP of Product Benny Reich puts it, “we need to support multiple channels because that is how customers work today.” The more customers they have, the more services they need to integrate with, especially when a single new customer’s data is spread across multiple apps. In this situation, many security solution vendors attempt to build each integration from scratch. This approach sequesters engineers from their primary responsibilities to focus their time and energy on the quirks and maintenance of each individual cloud service API. Perception Point wanted to avoid that delay and headache from the get-go. In Benny’s words, “the whole idea was to save development time and get a faster time to market. We needed speed.” Their initial vendor search revealed vendors that failed to meet their criteria for simplicity and speed to market.