Operations | Monitoring | ITSM | DevOps | Cloud

Top Tips is a weekly column where we explore practical ways to navigate the technology shaping our everyday lives. This week, we're tackling a common feeling: the fear of not being “tech-savvy” enough, and sharing simple habits to help you become more confident, curious, and comfortable with the technology you use every day. Ever felt like you’re the only person in the room who doesn’t understand what everyone is talking about? That little fear of looking clueless?

Perplexity was a big name a few years ago. But, we haven’t heard much out of them lately. There are plenty of posts on social media criticizing Perplexity to that effect. One thing that the posts miss is that Perplexity is still the king of AI search. Google is giving it a run for its money with the AI previews on Google search, but Perplexity still wins out in several measurable ways.

During your last major outage, several monitoring tools raised alerts and every one of them was correct. What none of them could say was which alert explained the others, so the opening stretch of the incident went on assembling a picture the systems already held between them. That time shows up in your availability numbers, your SLA credits, and your board report. AIOps platforms close that gap by grouping the alerts caused by the same failure and handing your team one incident with context attached.

As intelligence becomes increasingly accessible, competitive advantage shifts to the operational capabilities that transform insight into consistent, confident action. As AI makes operational insight easier to generate, competitive advantage is shifting to the platforms, workflows, and operational foundations that turn intelligence into trusted action.

Every organization running AI agents has already made a hosting decision. Most made it by accident. The sales team switched on the agent built into their CRM. Engineering is piloting a coding agent in a vendor’s cloud. Someone on the data team deployed a LangGraph service to a VM with a database key in an environment variable, and someone else is running an agent framework on a laptop with production credentials in a dotfile. Each of these is a hosting decision.

The most common reason to create an API key in CloudZero is to send data, such as AI telemetry or billing exports. Until now, that meant picking individual scopes from a list and hoping you chose the right ones. That works on day one. The problem is day ninety. Permissions on a key have always been a snapshot of the day you created it. A new AI telemetry endpoint ships in October, and a key created in August has no idea it exists.