Matthew Gregory @Autonomy_CEO

@TechCrunch a good spot to share the news... @Ockam / @autonomy_comp is running an acquihire exit process through April 15th. If you are interested in working with @mrinal and I please reach out to me directly. We are both based in San Francisco.

@antonosika Hey @daniellot_theo and @antonosika @Autonomy_CEO and @mrinal are running an exit process though April 15th. We'd love to team up with @Lovable ! Our assets include @Ockam and autonomy.computer

If you want agent-powered products that can run safely in real production environments, this model is worth digging into 🔗 bit.ly/4qfB5Yw

We worked with @autonomy_comp to show a better pattern with 1Password: • just-in-time access • least privilege by default • no standing creds • no hardcoded secrets

@edsim @levie @Ockam You miss a critical feature for Agent-to-Agent communication: Real-time These communications will be created and shut down in real time. Basically, these are serverless systems/functions. We've solved that too. @Ockam's cold starts in ms. ockam.io/for/serverless…

@edsim @levie It's a solved problem. @Ockam does all of this. It's not even AI agent specific, it can connect anything, anywhere, to everything else. ex. ockam.io/blog/secure-ll…

Agent to Agent communication between software will be the biggest unlock of AI. Right now most AI products are limited to what they know, what they index from other systems in a clunky way, or what existing APIs they interact with. The future will be systems that can talk to each other via their Agents. A Salesforce Agent will pull data from a Box Agent, a ServiceNow Agent will orchestrate a workflow between Agents from different SaaS products. And so on. We know that any given AI system can only know so much about any given topic. The proprietary data most for most tasks or workflows is often housed in many multiple apps that one AI Agent needs access to. Today, the de facto model of software integrations in AI is one primary AI Agent interacting with the APIs of another system. This is a great model, and we will see 1,000X growth of API usage like this in the future. But it also means the agentic logic is assumed to all roll into the first system. This runs into challenges when the second system can deliver a far wider range of processing the request than the first Agent can anticipate. This is where Agent to Agent communication comes in. One Agent will do a handshake with another Agent and ask that Agent to complete whatever tasks it’s looking for. That second Agent goes off and does some busy work in its system and then returns with a response to the first system. That first agent then synthesizes the answers and data as appropriate for the task it was trying to accomplish. Unsurprisingly, this is how work already happens today in an analog format. Now, as an industry, we have plenty to work out of course. Firstly, we need better understanding of what any given Agent is capable of and what kind of tasks you can send to it. Latency will also be a huge challenge, as one request from the primary AI Agent will fan out to other Agents, and you will wait on those other systems to process their agentic workflows (over time this just gets solved with cheaper and faster AI). And we also have to figure out seamless auth between Agents and other ways of communicating on behalf of the user. Solving this is going to lead to an incredible amount of growth of AI Agents in the future. We’re working on this right now at Box with many partners, and excited to keep sharing how it all comes evolves.

Data-in-motion specialist @Ockam nabbed #Nix to simplify onboarding, standardize its monorepo, and enable reproducible builds. See why platform leads, SREs, DevOps engineers, and others trust Nix for their most challenging projects! hubs.li/Q02Mr7V70 #NixOS #Flox #DevOps

Snowflake <> Kafka, in minutes. ockam.io/blog/snowflake… It is unwise to publicly expose your Kafka brokers to the Internet. It paints a giant public target on your most sensitive business data. Teams that value the security of their customers keep their Kafka private. This however creates the challenge of how to move data between private Kafka and other systems like Snowflake. Ockam makes it trivial to create end-to-end encrypted, very high-throughput, secure portals to private Kafka brokers. Your Kafka could be anywhere – in a data-center, in a private VPC, in any cloud, in a private kubernetes cluster, in a BYOC deployment, etc. Here is an example: The @SnowflakeDB team shared with us how many of their customers are unable to securely and easily move insights from analyses in Snowflake to other operational systems. These enterprise customers have tried all sorts of janky ways to make it work – from punching insecure holes in their firewalls to elaborate multi-region private links that took them many months to setup. We worked with Snowflake to create a simple Snowflake Native App. This app uses Ockam to securely connect Snowflake with private Kafka. It then enables Change Data Capture (CDC) from any Snowflake table to any Kafka topic. A few simple clicks and you have insights streaming from Snowflake to private Kafka anywhere. Safely and securely.

🔥 INTRODUCING SOVEREIGN AI - Private, traceable, and secure #AI for the #enterprise The need to share sensitive data with third parties combined with obscure AI traceability deters enterprises from adopting AI. Enter Sovereign AI, which allows enterprises to leverage the latest AI models on their own hardware and without sending sensitive data outside their own network. 🚀 𝗦𝗵𝗶𝗽 𝘁𝗵𝗲 𝗺𝗼𝗱𝗲𝗹 𝘁𝗼 𝗱𝗮𝘁𝗮 for end-to-end transparency and ownership of your data while delivering low latency, real-time inferencing on your own hardware. 🔎 𝗧𝗿𝗮𝗰𝗲 𝗔𝗜 𝗹𝗶𝗻𝗲𝗮𝗴𝗲 to fully understand a comprehensive audit trail for state-of-the-art LLM all the way to the source. 🔒 𝗦𝗲𝗰𝘂𝗿𝗲 𝗯𝘆 𝗱𝗲𝘀𝗶𝗴𝗻 so you can launch and govern large-scale systems with the highest level of integrity, authentication, and authorization at your fingertips. Want to leverage cutting-edge AI without ever sharing your data? Sign up for a preview of Sovereign AI👇 ai.redpanda.com/?utm_source=li…

We've all heard that "less is more," but this time "more is less" 👀 With Redpanda Connect, #developers can quickly connect to and unlock #data silos, while @Ockam provides the mutual authentication and end-to-end #encryption that zero-trust streaming data apps require. "Secure #streamingdata is now simple to set up, trivial to maintain, and almost impossible to mess up." - Matthew Gregory, @Ockam_CEO Less complexity. Less stress 🌴 Read all about it👇 redpanda.com/blog/ockam-red…

@clintgibler @Mandiant Everyone keeps talking about MFA in this breach. It's a red herring. How about we don't make APIs to DBs public to the internet?! Here's the right way to solve this problem: github.com/build-trust/oc…

Redpanda Connect with @Ockam empowers a single developer to easily create end-to-end encrypted streaming pipelines that can connect 100's of applications across clouds and hybrid infrastructure. hackernoon.com/ockam-and-redp… #data #cybersecurity #datasecurity

@emaxerrno Jumps for show, corners for dough.

Really important point. Conversations about end-to-end encryption often focus on the confidentiality property. Ockam Secure Channels guarantee end-to-end data authenticity, integrity, & confidentiality. The managed service cannot: forge, tamper, or see any message.

Dino A. Dai Zovi @dinodaizovi

2 years ago

@mrinal @0xdade Another good point to make is that without e2ee topics, the pub/sub cluster is a single point of security failure that can observe and/or forge any message.

1 1 3 7K 0

Couldn’t agree more with @dinodaizovi & @0xdade in the quoted thread below. An example: Ockam + Redpanda to create end-to-end encrypted, kafka compatible, data streams in seconds. Left: A kafka consumer that has the keys. Right: A kafka consumer that doesn't have the keys.

Dino A. Dai Zovi @dinodaizovi

2 years ago

The security architecture that will make cybersecurity tractable is one where users control cryptographic keys and permit decryption of their data while they are interacting with a service provider. Authenticating to that service provider should be of limited utility w/o keys.

1 4 15 9K 3

It’s never been this trivial to create distributed ingestion pipelines that are extremely safe and highly scalable. The above configuration is the same whether you are creating 1 producer or 1000 distributed, parallel, producers. Here's how you run it:

Today, we announced the world's first Zero Trust, Streaming Platform - a partnership between @RedpandaData & @Ockam Redpanda Connect with Ockam: Create end-to-end encrypted, highly scalable, data streams between 230+ sources and sinks of business data, in seconds. Details👇

A developer’s experience is dead simple. For example: In the screenshots below is all the configuration you have to write to create end-to-end encrypted data streams from @MongoDB to @SnowflakeDB Ockam and Redpanda take care of all the hard parts. 🧵…

keyboard_arrow_left Previous keyboard_arrow_right Next