#17

Contents

• Groundwork for AI Ops
• Better Hosts
• Squashing Bugs

Groundwork for AI Ops

Eliminating the need to build custom integrations between ops tooling is one of the primary benefits of Noop. The essential operational responsibilities of running software are already integrated on the Noop Developer Platform. There’s no need, for example, to connect your CI system to your hosting platform or stream logs from builds and applications to a centralized place.

Because of all this existing integration, Noop also has contextual understanding of your applications. Among countless other examples, Noop knows when your application deployment fails. And with access to Application and Build logs — Noop can use these different sources of information to produce an analysis of what went wrong and propose a resolution.

We are in the process of using these data sources as context to a LLM, known as Cooperator, which can provide incredible insight into the condition of your running applications. We’ve previewed some of the upcoming capabilities in a talk from Tech Week earlier this year, the past month we’ve continued those explorations and are moving closer to release for general availability.

Better Hosting

Hosts are the servers that run Noop Service and Task Components. Each Noop Component has specific compute and memory requirements and each Host has specific compute and memory limitations. Noop is responsible for putting the Component (container) on the Host where that Component will fit comfortably within the Host’s resource constraints. To ensure that one Component doesn’t adversely impact the performance of another Component (or our own Host management service) on the same Host, Noop carefully manages the distribution of Components across the available Hosts.

In the past month we developed better guardrails to ensure Noop Components cannot adversely affect each other’s performance. We also added more scaling capacity to better adapt to an increased demand for deploying Components.

Squashing Bugs

As we’ve been developing AI capabilities we have been updating functionality across our platform. We’ve taken the opportunity to resolve a few bugs before they impact users. We logged fixes for:

• Performance-related issues that could surface while browsing logs
• Usage report publishing error
• The proper handling of setting and unsetting Environment secrets
• Reolving redirects after deleted entities
• Endpoint Route resolution edge-cases