Today, we’re incredibly excited to announce a major milestone in the Tines journey. We recently completed a second Series B extension, raising an additional $50M from existing investors. What does this news mean for Tines? Well, first and foremost, our mission doesn't change. We're more focused than ever on powering the world's most important workflows. This new funding will allow us to pursue the full breadth of our ambitions.

Alexandre Dumas's timeless novel "The Three Musketeers" immortalized the ideal of unyielding solidarity, the enduring motto "All for one and one for all." In the face of ever-evolving threats in the digital realm, the European Union echoes this spirit with its landmark Cyber Solidarity Act.

Tech leaders taking cybersecurity seriously is something of a double-edged sword. While it’s undoubtedly good that organizations are waking up to the genuine threat cyberattacks pose, it’s depressing that they must siphon off so many resources to protect themselves rather than using them for growth and innovation.

The fight against money laundering and terrorist financing requires a united front, with financial institutions and large corporations playing a critical role. One key weapon in this arsenal? Politically Exposed Persons (PEP) screening. PEP screening identifies individuals with prominent public positions or close ties to them, who may be exposed to a higher risk of bribery, corruption, and other financial crimes due to their influence.

While unit testing is crucial for improving code quality and reducing later testing time, it consumes at least 15% of developers' time. Developers can utilize automated fuzz tests to allocate more time for developing new features. They replace negative test cases, constituting around 30% of unit tests. In a recent analysis of a Java project using a fuzzing platform, a single fuzz test was equivalent to potentially 309 unit tests, achieving 74% code coverage within just 25 seconds.

The huge ecosystem of integrations has over time become a true differentiator for Open Policy Agent (OPA), and an embodiment of the project’s promise to provide policy across the “whole cloud native stack”. Integrating OPA into a new tech stack also tends to be a rewarding experience for developers, which might help explain why so many integrations have been provided by external contributors over the years.