Raghu Hiremagalur

🧠 How JFrog ML Is Transforming the AI Software Supply Chain AI is becoming core to software delivery, but most ML pipelines remain fragmented, insecure and hard to govern. JFrog ML extends JFrog’s Software Supply Chain Platform to unify DevOps, DevSecOps and MLOps all in one secure enterprise-grade ecosystem. JFrog ML delivers:  ✅ End-to-end model lifecycle management ✅ Built-in versioning, metadata and promotion workflows ✅ Continuous security scanning of AI models and dependencies ✅ Seamless CI/CD integration for ML artifacts ✅ Multi-cloud and hybrid support with full traceability As AI scales, so do the risks. JFrog ML helps teams manage models with the same trust, traceability and automation as software, at an enterprise scale. 👉 Read the full blog here: https://lnkd.in/gkPGEfnP #MLOps #DevSecOps #SoftwareSupplyChain #AI #JFrog

26

2 Comments

💡 AI doesn’t just change how code is written – it changes expectations and outcomes. In the final section of Jellyfish’s AI Adoption Guide, we explore how expectations for engineering leaders are evolving as AI becomes embedded across the SDLC. Because the organizations pulling ahead are treating AI as a transformation, not a tooling upgrade. Inside, you’ll explore: - Why AI adoption is quickly becoming a leadership mandate, not an option - How to balance ambitious goals with realistic expectations - What cultural investments are required to sustain long-term gains - How data can be used to align executives and engineering teams The teams that win in the AI era won’t just have better tools – they’ll have leaders who know how to guide change. Download today: https://lnkd.in/dut_6WpQ

20

LiteLLM is an open-source proxy that connects your app to LLMs through one unified interface. Paired with Redis, it gives AI and ML teams a simple yet powerful way to unify access to LLMs, accelerate response times, and make AI apps real-time. Redis handles performance, memory, and data coordination that modern AI apps demand, while LiteLLM handles abstraction and routing. Our AI Product Marketing Manager Rini Vasan dives into: ▶️ What LiteLLM is ▶️ Why it works well with Redis ▶️ How LiteLLM and Redis work together Learn how to scale your LLM gateway with LiteLLM & Redis: https://lnkd.in/gqsTebF7

32

Who needs self-service? In this article, Conduktor’s VP of Engineering, Matt Searle, talks about his own experiences attempting to balance developer autonomy alongside platform stability. His key insight? Govern Kafka, or risk havoc. Read his latest blog—and learn more about how Conduktor can help you implement self-service with guardrails. https://lnkd.in/ejWTRctu

14

Two of AWS’ Sr. Principal Engineers, Nicholas Matsakis and Marc Bowes, take us inside the development of Aurora DSQL in a fascinating new blog. The post shows how the team scaled write operations without two-phase commit, overcame garbage collection hurdles, and ultimately embraced Rust for both data and control planes. What I find particularly interesting is how the team's journey with Rust evolved. They started cautiously, using it for a single component, and ended up rewriting almost everything in Rust. It's a reminder that sometimes the hard choices - like adopting a new language - can unlock tremendous value. The full post is well worth your time. It's not just about database internals, but also about team dynamics, a culture of learning (and questioning established approaches), and making difficult architectural decisions. Read it here: https://lnkd.in/eMhxBu9e Now, go build!

1,045

16 Comments

PagerDuty is now a Cursor customer. Over 30,000 customers rely on PagerDuty to respond to incidents faster, reduce outage risks, and build operational resilience. We’re excited that PagerDuty engineers will now use Cursor’s agents to build these mission-critical products.

555

6 Comments

When most people hear "solid-state," they think storage. But in Santa Clara, xMEMS Labs just gave that term new resonance, literally. The company just raised $21M in Series D funding led by Boardman Bay Capital Management, with Cloudview Capital, CDIB-TEN Capital, Harbinger Ventures, Susquehanna Asia Venture Capital, and other strategic investors tuning in. This isn't another round of capital, it's an #amplifier for a company turning silicon into a new language of #sound and #cooling for the AI era. Founded in 2018 by Joseph Jiang and Jemm Liang, xMEMS spun out of piezoelectric R&D at TSMC and turned what was once wafer-level theory into commercial hardware. Joseph Jiang, a veteran of Knowles, Fortemedia, and InvenSense, leads with precision and swagger, while Jemm Liang, who built Ultrachip from the ground up, drives the engineering with surgical focus. Co-Founder & CLO Wei-Fu Hsu, the former MediaTek exec and IP expert, ensures xMEMS' innovation is as protected as it is disruptive. Their play? A monolithic MEMS platform that transforms voltage into vibration, silicon into sound. Unlike legacy coil speakers and fans, xMEMS tech doesn't move parts, it moves markets. Over 500K MEMS speakers shipped in 1H'24, backed by >250 global patents. The Cypress & Sycamore lines redefine what "small" can do: 1mm-thin, full-range, and capable of sub-bass response once thought impossible in earbuds. Their XMC-2400 µCooling chip, 1mm-thin, fan-on-a-chip, inaudible, moves 39cc/sec of air at just 30mW. That's not cooling, that's choreography at a molecular level. Dr. Chester Hwang, named CTO on Oct 15, 2025, joins to push that curve further. Alongside veterans Mike Housholder (VP Marketing & Biz Dev), Jim Wargnier (VP N.A. & EU Sales), James Lee (VP & Korea GM), Steven P. Bentley (VP Sales), and Martin Lim (VP MEMS Tech), xMEMS is scaling at semiconductor speed. They're already in BleeqUp's AI sports glasses and teamed with Dongguan Rayking Electronics for TWS modules. When OEMs talk "next-gen," they're talking xMEMS-level integration. For investors like Boardman Bay's Will Graves, this isn't just sound engineering, it's signal intelligence. With AI pushing devices thinner, faster, and hotter, xMEMS' piezoMEMS platform sits at the intersection of #acoustics and #thermals, where every millimeter matters. Backing them is a bet that the next wave of #sensorytech won't just compute, it'll feel alive. So what's next? Scaling production, expanding capacity, and embedding xMEMS' silicon pulse into everything from earbuds to AI #datacenters. In a world chasing speed, silence, and fidelity, xMEMS isn't following the beat, they're building the frequency the future will hum to. #Startups #StartupFunding #VentureCapital #SeriesD #AI #Sound #SoundEngineering #Semiconductors #Data #DataDriven #Technology #Innovation #TechEcosystem #StartupEcosystem #Hiring #TechHiring If software engineering peace of mind is what you crave, Vention is your zen.

16

1 Comment

Your CI/CD bill is not exploding because of “expensive runners,” it is bleeding out through flaky tests, over-parallelized jobs, and slow feedback loops that quietly tax every deploy This piece shows you how to redesign pipelines so you cut compute waste, shrink queues, and speed up developer flow without adding yet another approval gate or YAML religion Full breakdown in the comments. #DevOps #CICD #PlatformEngineering

8

1 Comment

For industry leaders like RS, API orchestration is the foundation for efficiency and scale. With Apollo’s graph-based orchestration platform, they unlocked 10x performance, and reduced latency by 24%, enabling their teams to build and innovate across previously siloed systems. See how RS modernized its tech stack to support future growth → https://lnkd.in/gYKdmGCG #GraphQL #APIorchestration #ApolloChampions

14

Big M&A news in Seattle startup land as Palo Alto Networks plans to acquire 3-year-old cybersecurity company Protect AI, ranked No. 10 on the GeekWire 200, our list of top tech startups across the Pacific Northwest. It's part of a growing cohort of cybersecurity startups that are based in the Seattle region or have a significant presence in the area. Read more: https://lnkd.in/gfx_pXkS

91

An agent has no consistent definition. You can think of an agent as an autonomous or semi-autonomous system that can take actions on behalf of the user in a given environment, state, and make decisions or take actions that can accomplish certain tasks along a given time-frame, either by calling tools, dynamically selecting the next action to take or use a deterministic "workflow" (systems where LLMs and tools are orchestrated through predefined code paths). Using an Agent framework that gives you the ability to built systems in both, a reliable and a dynamic way can accelerate your agent development journey using agent abstractions. This means building Agentic systems that can reliably call tools, store memory (episodic/semantic/procedural), have comprehensive logging and observability, human in the loop workflows and the ability to build various multi-agent patterns flexibly based on your use case. A successful Agentic system in production is usually a combination of both, dynamic and predictable/reliable multi-agent systems. Strands Agents SDK gives you exactly these capabilities by treating each “agent” as a combination of a foundation model plus a suite of tools. You define a prompt and register your tools (decorated functions) in code, then Strands handles reasoning→planning→tool-execution cycles, local testing, and cloud deployment (ECS, Fargate, Lambda, EC2), along with support for all other agent abstractions provided above. Excited to share a hedge-fund analyst multi agent system: This uses the newest Anthropic's Claude 4 Sonnet/Opus that powers the Lead Analyst Agent, routing incoming queries to specialized sub-agents for fundamental, technical, and market analyses. Each specialist is wrapped as a callable tool (using the “agents-as-tools” multi-agent pattern), so the orchestrator never has to implement domain logic itself and can handoff the task to an agent as a tool. For sensitive operations (insider lookups), we utilize a HITL approval step that halts execution until a human grants consent. We also use meta-tooling that enables the Lead Analyst to generate, load, and invoke new custom tools at runtime—whether it’s a portfolio beta calculator or a pricer—without redeployment. Strands also embeds observability (Langfuse) and OpenTelemetry tracing so you can trace reasoning events, tool invocations, errors, and end-to-end workflows in real time. View more information on the code implementation here: https://lnkd.in/gJmwVyGi Code implementation: https://lnkd.in/gzTtJvJq Thanks to 🏄‍♂️ Cagatay Cali for being a reviewer/collaborator on this! Feel free to try it out and reach out with any questions/ideas. #aws #agenticAI #strands #agents #generativeAI

60

6 Comments

NEXTGEN INFRA STARTUPS MUST PLAY OFFENSE Historically, software infrastructure / middleware startups have played DEFENSE well. They have built deep, defensible technology moats over a period of time. The founders have been deeply technical, have sold to other developers, and have been content to not have a strong public-facing brand. However, this playbook (and archetype) must change. Infra founders and startups must play OFFENSE and become more dynamic and front footed. Why? First, foundation models are adding more and more infastructural components and nibbling away at what was traditionally considered infrastructure. No company can now comfortably sit and own a part of the stack. It will inevitably erode. Second, end customers are deciding or opining on what infrastructure to use. Guess what? Customers of infra products are no longer just career engineers but ordinary people (including VCs!) Infrastructure now has a PLG motion. Having a customer-facing brand is no longer optional. Finally, it’s possible (or even probable) that your company might need to fundamentally change its business model, and not be an infrastructure company any more. And in this crucible moment, you need to have the muscle and the ability to seize the opportunity and go for it. Consider OpenAI launching ChatGPT or Vercel launching v0. They could never have managed it with a legacy infrastructure mindset. Check out Groq’s homepage - it looks more like a vibecoding startup than a chip company. To summarize, infrastructure startups need to evolve. They must start thinking about the end customers, become much more public-facing with their brand, and develop the muscle to build customer-facing (not just developer facing) products. The archetype of infrastructure founders is changing. They cannot just be technical. That’s tablestakes. They must build a deep understanding of their customers’ customers, be superb at product development, marketing, storytelling and brand building, and be ready to move up the stack at any time. In other words, they must be able to play OFFENSE. That’s what greatness means in infra companies today.

146

8 Comments