Glow’s AI endpoint bet shows why payment teams need tighter controls

Glow’s emergence from stealth at a $1.2 billion valuation is another sign that enterprise security teams are being pushed to rethink where risk now lives. According to TechCrunch, the startup is targeting a new class of endpoint risks created by the rapid adoption of AI agents and developer tools inside enterprises. That matters beyond cybersecurity because the same shift is changing how finance, operations, and engineering teams control access to sensitive payment systems.

TechCrunch reported that Glow raised $180 million in an all-equity Series A round backed by Sequoia Capital, Cyberstarts, Greenoaks, and Redpoint Ventures, among others. The company says it is building an endpoint security platform that monitors and controls software, AI agents, and developer tools running on employee devices. As co-founder and chief executive Roi Tiger put it, “AI lands on the endpoint” (TechCrunch).

For payments teams, the practical takeaway is not that every new AI tool is a threat. It is that the number of places where sensitive actions can originate is growing. Invoice approvals, payout changes, wallet operations, and settlement workflows increasingly sit inside browser-based tools, internal dashboards, and developer environments. When AI assistants are added to that mix, companies need tighter access policies, clearer audit trails, and fewer manual workarounds.

That is especially relevant for businesses moving money across crypto, stablecoins, and fiat rails. A payment platform is only as safe as the controls around who can initiate transactions, who can change destination details, and how teams review activity. Radom’s payments stack is built around those operational needs, with crypto payments, billing, invoices, payment links, payouts, and conversion in one place. Radom describes the platform as one where businesses can “use one platform for payments, billing, conversion, and settlement” (Radom pricing).

In practice, that matters because payment operations are no longer isolated from the rest of the business. A finance team may need to reconcile customer payments, a developer may need API access for checkout flows, and an operations lead may need to trigger payouts across multiple currencies. If those workflows are spread across too many systems, the risk is not only fraud or misuse. It is also simple operational error, which can be expensive when funds move quickly.

Glow’s pitch also reflects a broader reality for internet businesses: security and payments are converging. The same companies adopting AI tools for support, coding, and internal automation are also managing subscriptions, marketplace payouts, contractor payments, and treasury movement. That makes access control and payment infrastructure part of the same conversation. Teams need systems that support growth without making every change a manual process.

For Radom customers and prospects, the useful question is how much of your payment stack still depends on ad hoc permissions and one-off approvals. If your business accepts crypto payments, settles in fiat or crypto, or runs payouts at scale, the safest setup is usually the one with the fewest disconnected tools and the clearest operator controls. Radom’s crypto payments page is a good starting point for teams evaluating hosted checkout, payment links, invoices, subscriptions, and APIs (Radom crypto payments).

AI is not just changing how enterprises build software. It is also changing how quickly sensitive business actions can be initiated, reviewed, and repeated. That is why the Glow story is relevant to payment operators. The companies that will handle this well are the ones that treat security, approvals, and money movement as one operating problem, not three separate ones.

For teams reviewing their own stack, the next step is usually simple: map who can initiate payments, who can approve them, and which systems hold the source of truth for balances and settlement. If that process is fragmented, it is worth looking at platforms that combine payment acceptance, payout workflows, and conversion in a more controlled environment.