Operations | Monitoring | ITSM | DevOps | Cloud

We renovated the Civo Community Slack: Here's what changed and why

The Civo Community Slack has become home to over 35,000 engineers, platform teams, students, and practitioners. It’s one of the things we’re most proud of, a genuine space where the people who use Civo and the people who built Civo are in the same room. Since starting the Civo Community Slack, we’ve shipped an entirely new brand, launched Konstruct, and expanded our AI infrastructure.

Making Shared GPUs Even Safer with Kubex and HAMi-core

Table of Contents A few months ago, we introduced Kubex support for the KAI Scheduler to improve GPU sharing for production inference workloads. The basic model is simple: The KAI Scheduler handles placement and GPU sharing. Kubex continuously observes usage and adjusts those allocations as demand changes. KAI provides the scheduling foundation. It lets multiple workloads share a GPU while accounting for the amount of GPU each workload requests. Kubex then closes the loop.

What to Know About AI Code-to-Merge Platforms

AI coding agents can generate pull requests at a pace your team has never seen. The bottleneck has shifted from writing code to everything that follows: reviewing, iterating, and merging. AI code-to-merge platforms are the category of tools built to manage that entire lifecycle, from the moment an agent starts working to the moment code lands in your main branch. This article walks through ten questions you should ask before committing to a platform.

Build and run Datadog workflows from Bits Chat or AI agents

Teams use AI coding agents and Bits Chat to troubleshoot systems and handle complex tasks, often uncovering repetitive work worth automating. But turning those routines into workflows can still require switching tools and recreating context manually. Through the Datadog MCP Server, Workflow Automation now lets you build workflows from Bits Chat or AI coding agents like Claude Code, Cursor, and Codex.

The Missing Step in Mobile Release Operations: Store Screenshot Management

Mobile release teams are used to managing code, builds, test results, signing credentials and deployment approvals. Store screenshots often sit outside that system. They are treated as a final design request, passed between product, marketing and engineering in a collection of chat messages and shared folders.

AI Spend Is a Capacity Problem, Not a Billing Problem

Every organisation running models in production eventually reaches the same point: the AI portion of the cloud bill grows faster than expected, and the immediate response is to invest in visibility. Calls are tagged, spending is attributed, dashboards are created, and the results are shown to the teams responsible.