AI enablement, security, and control in one platform. The default for AI-native teams like Gusto, Lemonade, & Baseten.

NYC & SF
Pinned Tweet
Companies shouldn’t have to choose between reckless AI power use and AI as a glorified text editor. Runlayer is the golden path: secure AI enablement, agents where teams work, identity-aware controls, observability, runtime security, cost optimization, and shadow AI visibility.
6
4
55
294,652
Runlayer retweeted
mcp is dead, long live mcp? collabed with opus to put together this 102 explainer. there's plenty of content on "what is mcp" not enough on MCP & context window i covered: - context bloat, and why it turned out to be a client problem - servers hiding all their tools behind search & execute - the "just use CLIs" take, shipped to a 5,000-person company - why boring standards win 0:00 - MCP is dead (again) 0:29 - The original sin: context bloat 0:53 - Plot twist: it was a client problem 1:23 - The meta-tool detour 1:56 - This year's hype: just use CLIs 2:37 - What MCP actually bought you 3:28 - Two-way street 3:50 - How standards win
2
6
22
1,364
Everyone is building an agent builder. Then they try to layer security on top. We did it the other way around. Runlayer Agents are powerful, secure by design, and easy to use. Every agent ships with identity, access controls, and deterministic policies built in. You don't have to choose between usability and security.
2
18
3,760
We ship roughly 200 features a month. And we've been so busy building, we almost forgot to tell you about it. So we're running it back with a four-week launch series. (Yes, that's a Runlayer pun. No, we're not sorry.) Meet us back here on Thursday. We have some catching up to do.
1
11
518
Runlayer retweeted
Jake Moghtader from @runlayer about agent runs benchmarks, secuirty and mcp at @AgenticAIFdn 🇳🇱 Monitoring, observable agentic workloads and tracing are the topics.
2
1
5
439
We're proud to be named an AI Security Endpoint Leader in @latiotech's 2026 AI Security Market Report. Demand for endpoint AI security is on the rise. Security teams need real controls over what agents can do, and Runlayer is delivering them. Learn how → runlayer.com/blog/runlayer-n….
2
11
2,621
In SF for the day reppin’ @runlayer at @browserbase Navigate. :)
1
27
584
Fal.Con 2026 was full of convos on the state of AI security. One thing leaders agreed on: AI is exposing the lack of security fundamentals at scale. We rounded up the top takeaways from the week → runlayer.com/blog/3-lessons-…
7
1,677
We're proud to partner with @SlackHQ on their latest Add to Slack feature. Each agent you build and use is governed by Runlayer, with agent identity, access control, and audit trails built-in. Wrangling agents should be as easy as building them. With Runlayer and Slack, it is.
4
6
19
4,743
Runlayer retweeted
Opinions on agentic engineering appear to be converging into two camps: "You should put a lot of planning up front, all the way down to program design, then let the agents cook", aka the @humanlayer_dev way. vs "Do a shit ton of investment in architecture/linters/LLM checks/automatic verification upfront, and then let agents rip. Garbage collect periodically", aka the @poteto way. I currently land somewhere in-between: - A bunch of research and planning up front, but skip program design unless I identify that a net-new abstraction will be needed, or I know I'm working on high-stakes/core code. - For "every day" stuff, I lean heavily on guardrails. - Frequent sampling of PRs that have been landing on main to spot problematic code that should've been caught by a guardrail. Add more guardrails to catch it, burn down the offenders. - Frequent sampling of hot spots in the codebase, to detect when human intervention is needed, e.g. an abstraction has grown out of control. Maybe I oughta build a heatmap visualization for this? - I also love @poteto 's take on the tier of guardrails (opinionated architecture > static analysis > tests > LLM checks)
11
6
114
15,725
Runlayer retweeted
so it seems like @runlayer CEO doesn't have an account here, but recently I stumbled upon something smart that he posted on his LinkedIn and I thought everyone will benefit from this here this Friday. think first
1
1
2
445
Runlayer Agents 🤝 @baseten Inference Run models like Kimi K3, GLM-5.2, DeepSeek-V4 Pro, and more. Frontier-class performance on inference you control now available for all your agents in Runlayer.
5
2
27
3,054
MCP 2026-07-28 dropped today. We got a sneak peek, and we're in good company. The best part? Massive improvements to MCP's auth and security posture.
3
1
16
1,592
Runlayer retweeted
This is exactly what we enable our customers to do. Our process is basically Uber's on steroids. 1. We pair an FDE with your AI champion. Every rollout starts by embedding one of our forward-deployed engineers with the person on your team actually building agents 2. We see what's already running. A discovery scan maps every AI client, MCP, and shadow connector across the company. In almost every org, 3–5 MCPs drive 85%+ of agent traffic, so we know exactly what to build on. 3. You build agents with your team, live. Working sessions where your team drives. They build the agent in a local session (Claude Code, Codex), wire in your connectors, then use the platform to see what it did, audit the run, and iterate. We end this with a working agent, not a bad prototype. 4. The platform makes the good agents reusable. Build a skill privately, iterate on it, then share it org-wide and invoke it from Slack. Literally, one person's S-tier workflow becomes everyone's. 5. The platform also optimizes every run. An agent optimizer audits each run for tool usage, prompt quality, and model choice, right-sizing Opus down to Sonnet where it holds up. 6. Now (and only now) do we turn controls on. Never as a hard stop: start in alert mode, build the allow-list, flip to enforce once a better path exists. RBAC on every agent, full session visibility, nothing yanked. TL;DR is let the most AI-pilled experts go crazy, give them a platform, and share their agents and expertise with everyone else at the company. Everyone else learns from these experts. Using @Runlayer, we almost always find the biggest wins hiding in plain sight. They're with your most AI-forward engineers. But the best agents beyond that are hidden in the processes your SMEs know by heart. It should be dead simple for them to turn that process into an agent. That's who we enable to run on a golden path to AI adoption. nitter.net/praveenTweets/status/2…
Agentic AI adoption is on fire at @Uber, and it's changing the way we build, not just in engineering, but across the entire company. Today, 99% of our engineers use AI tools. More than 70% of pull requests are attributed to local or cloud agents. And our engineers have built 2,500+ agent skills across the software development lifecycle. Those numbers are exciting, but they led us to a much bigger question: How do we bring agentic AI beyond engineering? Finance. Legal. Operations. Marketing. Customer Support. HR. Procurement. These functions run on complex workflows that are often manual, highly nuanced, and spread across dozens of systems. You can't automate them effectively by looking at process diagrams or documentation. You have to understand how the work actually gets done. So we created something called Agentic Pods. The idea is simple. We handpicked ~30 of our most AI-proficient engineers (people with deep knowledge of Uber's systems) and paired each of them with a domain expert from a business function. Then we gave every pod just two weeks. • Days 1 – 2: Shadow the expert. Observe every step. Document workflows. Ask questions. Build intuition. • Day 3: Prioritize opportunities based on scale, repetition, business impact, and data availability. • Days 4 – 5: Build a working agent alongside the person doing the job. • Days 6 – 9: Validate with several others performing the same work. Does it generalize? Does it actually make their job better? • Day 10: Ship. In just the past two months, we've run 16 Agentic Pods across 16 different business functions. • Capital allocation across 150 cities: 15 hours → 30 minutes. • Financial pacing reports: 2 days → 10 minutes. • Marketing web quality assurance: 2 weeks → 50 minutes. • Support workflow creation: 9,000 manual workflows → self-service automation. The productivity gains are impressive, but what surprised us most wasn't the speed. • It was how quickly engineers embedded in unfamiliar domains uncovered opportunities that had been hiding in plain sight. • The biggest wins rarely come from automating one task. They come from rethinking an entire workflow. Once you redesign the workflow around AI, you often eliminate handoffs, remove unnecessary approvals, replace legacy tooling, reduce vendor spend, and dramatically accelerate decision-making. • The workflow becomes the unit of automation - not the individual task. • The most impactful agent skills cut across teams, orgs, functions, tools, and systems. The biggest lesson? The best AI opportunities are rarely visible from the outside. You discover them by sitting next to the people doing the work, understanding every friction point, and building with them, not for them. We're now forming a dedicated team to scale this further and go deeper. They'll deeply understand the work, redesign it from the ground up, and use AI to fundamentally change how the business operates. It's exciting times!
7
7
210
50,390
Runlayer retweeted
Runlayer takes AI Engineer World's Fair in SF this week! Here's what's happening: - @rafalwilinski giving a talk on Self-Improving Agents, one of Runlayer's hottest new products, today at 12pm pt - Raffles for swag, including iPads & custom Nikes, at our booth. All you have to do is stop by (next to AWS & Microsoft) - Premier sponsor this year, so every attendee gets a lanyard with our logo. reminder that every company attending can become AI-native with @runlayer
1
3
18
1,755
Fortune featured @Runlayer and interviewed our CEO, Andrew Berman, on our latest fundraise, the future of AI enablement, and how Runlayer is the “Switzerland business, a neutral, cross-provider control layer” for the future of agents performing work. Link in the first reply.
2
11
5,048