[{"data":1,"prerenderedAt":35},["ShallowReactive",2],{"post-merging-the-browser-and-the-sase-stack":3,"post-next-merging-the-browser-and-the-sase-stack":24,"post-nav-merging-the-browser-and-the-sase-stack":25},{"_path":4,"_dir":5,"_draft":6,"_partial":6,"_locale":7,"title":8,"description":7,"heading":8,"date":9,"minutes":10,"summary":11,"body":12,"_type":18,"_id":19,"_source":20,"_file":21,"_stem":22,"_extension":23},"\u002Fblog\u002Fmerging-the-browser-and-the-sase-stack","blog",false,"","Merging the browser and the SASE stack","2025-06-18",6,"Consolidation slideware says one agent, one policy. The enforcement plumbing underneath says otherwise. What merging actually requires.",{"type":13,"children":14,"toc":15},"root",[],{"title":7,"searchDepth":16,"depth":16,"links":17},2,[],"markdown","content:blog:merging-the-browser-and-the-sase-stack.md","content","blog\u002Fmerging-the-browser-and-the-sase-stack.md","blog\u002Fmerging-the-browser-and-the-sase-stack","md",null,{"newer":26,"older":31},{"_path":27,"title":28,"heading":29,"date":30},"\u002Fblog\u002Fgo-vs-rust-for-proxy-workloads","Go vs Rust for proxy workloads: the choice and why","Go vs Rust for proxy workloads","2025-09-24",{"_path":32,"title":33,"heading":33,"date":34},"\u002Fblog\u002Fprompt-injection-from-the-enforcement-side","Prompt injection, from the enforcement side","2025-03-05",1781170135587]