kiran bond.log retweeted
MCP is not an integration strategy. We raised $15M from Bessemer to prove it.
If you are building an enterprise agent that needs to connect with your customers’ critical systems, simply integrating with the Salesforce MCP isn’t going to cut it.
1. MCP isn’t going to help you backfill millions of transactions from your customer’s NetSuite, or millions of accounts from your customer’s HubSpot. For that, you need robust sync infrastructure.
2. Enterprise customers do not use tools out-of-the-box. Their CRMs, ERPs, and all the legacy systems of record have custom objects, custom fields, and bespoke workflows. MCP will not help you navigate that complexity.
3. MCP is built for real-time querying. Some work is better done async, especially when you are dealing with strict rate limits that many SaaS products have. You need async workloads and smart retry logic.
Ampersand is the integration infrastructure for deeply connecting with your customers’ systems of record. Because the SaaSpocalypse didn’t happen. The world still depends on CRMs, ERPs, HRISs, and ITSMs.
Your AI is vaporware without deep integrations with your customers’ systems of record.
Introducing @WithAmpersand: integration infrastructure for enterprise agents.
We power 11x, Orb, and Square's ability to take agentic action in systems of record like Salesforce, SAP, NetSuite, and Workday.
Ask anyone serious about building AI and they’ll tell you:
- The SaaSpocalypse didn’t happen. The world depends on CRMs, ERPs, HRISs, and ITSMs.
- Your customers customized their deployments beyond recognition.
- Systems of record companies are basically monopolies. They never had to make their APIs and MCPs user-friendly.
- Docs don't explain half the weird edge cases you'll hit.
- One bad write can blow up your pilot or renewal.
- Once you finally get it working, someone changes a field and it breaks again.
The world's data lives in structured databases. AI needs a translation layer to work with it.
So, for your AI to truly transform the way enterprises work, you'll need deep integrations built for:
- scoped permissions
- bi-directional actions
- real-time speed for agents
- custom objects, fields, and workflows for each of your customers
We built Ampersand to power the future of software.
AI didn't trivialize writing integrations. It made them the critical path.
I believe that deeply, so I didn't make a launch video about Ampersand.
Instead, it's the best builders I know explaining just how big of a challenge this is.
Token whiplash? That’s what happens when years of pushing AI adoption collide with rising token costs.
That’s why we’re introducing Glean Intelligence, a new layer of our enterprise AI platform, that brings model choice, auto routing, and AI usage together.
Our latest benchmark puts that impact in perspective. Glean averaged $0.58 per query vs. $2.98 for Claude Cowork, with 81% lower token costs and a 78% preference rate.
AI doesn’t live in one front door anymore. 🚪
At Glean:GO, we introduced Glean AI Gateway, one governed layer for LLMs and MCP. It gives enterprises control and ownership over the models, context, skills, and memories behind every front door.
Own your AI wherever work starts.
Meet Glean Tau, the only desktop AI workspace that unifies local files, apps, and code with comprehensive enterprise context in one governed place.
It plans, executes, reviews, recovers, and acts on your behalf from a single desktop surface.
Live from #GleanGO 🎥
The intelligence era is here….and it’s powered by Glean. 💡
Glean’s context across your work makes it more efficient, secure, and proactive.
From Glean Tau, our new desktop AI workspace, to autorouting, a unified AI gateway, and proactive independent agents, our new updates unlock AI’s potential.
Join the live Glean:GO keynote today at 9am PT to see them all in action: glean-it.com/4iuEceD
Glean:GO making an appearance in NYC 🗽
See you tomorrow at 9 am PT for our morning keynote. glean-it.com/4gxHM5c
OpenAI cut Luna 80% last week. Everyone's cheering cheaper tokens. But an agent's bill is tokens × steps × runtime, not price per token. A model 80% cheaper that burns 10 steps where a good harness needs 3 still costs more. The harness sets your spend, not the sticker.
Four frontier models shipped in three weeks. A fifth is two months late. If either fact moves your roadmap, you don't have an AI strategy, you have a dependency. Build the layer that swaps models without a rewrite. Three-horse race. Bet on the track, not one horse.
so this is apparently what happened, according to OpenAI and Hugging Face’s own posts. wild.
tl;dr:
• OpenAI cyber eval – GPT-5.6 Sol and a more capable pre-release model ran ExploitGym with cyber refusals reduced
• containment bypass – exploited a zero-day in the eval’s package-registry cache proxy
• OpenAI internal movement – escalated privileges, moved laterally, and reached a node with internet access
• Hugging Face targeted – inferred HF might host ExploitGym models, datasets, or solutions
• HF initial access – a malicious dataset abused two code-execution paths to run code on a processing worker
• HF internal movement – escalated to node access, stole cloud and cluster credentials, and moved into internal clusters
• result – OpenAI says the models obtained test solutions directly from HF’s production database
• 🫠 defender twist – HF says commercial frontier models blocked parts of the forensic analysis, so it switched to self-hosted GLM 5.2
i’d thought about sci-fi scenarios like this before, but assumed they were at least a couple of years away.. and that by then we’d be better prepared, with proper protections in place.
apparently not. here we go.
We're partnering with @huggingface to investigate an unprecedented security incident.
Cyber-capable OpenAI models compromised Hugging Face production during a benchmark evaluation.
Sharing preliminary findings to help defenders understand emerging risks:
openai.com/index/hugging-fac…
GLM 5.2 is now in beta for Glean Assistant 🤝
In our evals, the open model reduced token costs by 35% while delivering completeness comparable to GPT-5.4
GLM 5.2 in Glean is hosted in the US or EU with leading inference providers compliant with zero data retention. No data ever goes to the model developer.
Everyone agrees context is the bottleneck now. The hard half nobody says: context you can't govern is a data leak with good latency.
kiran bond.log retweeted
A year ago, many companies were betting on the right AI front door: picking a single assistant or locking into one frontier model provider.
Today, many are realizing that the interface layer is changing too quickly. The real place to standardize is underneath it, at the platform level.
A few things have changed:
- Interfaces are evolving too quickly. One team wants AI in Slack. Another wants it in the browser, the IDE, or inside the tools they already use. If every new surface requires its own approval and policy, companies spend more time governing AI than adopting it.
- Frontier pricing is rising while open-source models keep improving. Most enterprise tasks do not require the most expensive model. The advantage will go to companies that can route intelligently by task, not companies that commit too early to a single provider.
- Patchwork governance doesn’t scale. Leaders want platform fundamentals: consistent security, centralized visibility into token usage, and proactive cost controls across the system.
Companies need infrastructure that can apply policy consistently, provide visibility into usage and cost, and make it easy to change interfaces or models as the market shifts.
That is why we built the @glean AI Gateway. It supports 30+ models across open-source and proprietary providers, from OpenAI, Claude, and Gemini to NVIDIA, while keeping security, governance, and cost control in one place.
The front doors will keep changing. The companies that get the most value from AI will decouple the interface from the infrastructure behind it.
→ 2 hours saved per employee, every week
→ $2.7M+ in owner change orders reviewed and processed by agents
→ 90% company engagement
How does a major infrastructure firm get results like that?
McCarthy Holdings, Inc. used Glean to give teams better context, connect scattered information, and turn manual work into faster workflows.
The best coworkers act independently and collaborate where work happens, and that’s no different for an AI coworker.
Our new independent agents have identity, context, memory, proactivity, and accountability built in so they can act on their own while staying within the permissions, policies, and guardrails your organization sets.
Watch an independent agent work with oncall engineers to take an issue from start to finish 👇
kiran bond.log retweeted
Today, we're officially introducing the new Vybe.
We started as "Lovable for internal apps." We spent the last year building the infrastructure: permissions, integrations, databases, workflows. Everything companies need to actually trust software inside their business.
Then, OpenClaw came out and started showing what was possible with agents for personal use cases. Everything clicked for us.
The infrastructure we'd built wasn't just useful for humans anymore: it was exactly what agents needed to operate inside real companies and teams.
What happens when agents can work 24/7, with the right context, the right permissions, and access to your company's tools?
A founder becomes a one-person army. A small team operates like a much bigger one.
That's the mission we fell in love with at @vybe_build. Our agents have names and roles. They have their own email, Slack, phone number. They prep meetings, follow up with leads, run ops, update CRMs, build internal tools.
Vybe runs on Vybe.
We're onboarding 10 teams a week to run AI-native companies.
kiran bond.log retweeted
"This is the first time ever that I can remember that technology costs the same as people, and you're making that comparison: choose tech or people”-@jainarvind


















