Memory costs on ICP are changing, and you might be thinking "what does this mean for my cycle bill"?
We were wondering the same thing, so we built a dedicated Memory Price Change view into CycleOps that teams can use to quickly understand the impact of the upcoming ICP protocol memory pricing update.
We operate CycleOps and ICPTopup as a tiny distributed team (two founders and some contractors). Like most small teams, we've always had more product improvements queued up than we could get to. UI papercuts, customer-reported bugs, and small polish work can be the difference between a product that feels good and one that feels neglected.
Since February, we've been shipping 5-10 of these incremental fixes every week, with most of the work done by AI agents. We took a continuous improvement process we've been running for years and adapted it so that agents handle the heavy lifting while humans stay in charge of the decisions that require taste, product context, and long term engineering perspective.
This article is a walkthrough of how we moved this process to agents, what is working, and what we want to do next.
We’ve shipped a broad set of mobile UX improvements, and CycleOps is now genuinely easy to use on your phone.
CI/CD pipelines just got a lot easier on the Internet Computer.
In this post, I'm going to show you how you can easily automate your deployments using CycleOps and IC Deploy Actions
No need to manually run dfx deploy command on your terminal, or spend hours configuring your custom github actions. Just plug in and use.
Heap overflow anxiety — gone. The new CycleOps V3 Blackhole adds 8 new in-depth memory metrics, with heap and stable memory alerts that keep your canister's data healthy and cost‑efficient.
Today we're very excited to announce a new integration with icp.ninja, the web based integrated development environment (IDE) that is the best place to kick start your Internet Computer development journey. We built a new protocol and API that enables icp.ninja users to create, deploy, and manage real canisters, right from the IDE.
Spot the metric anomaly, trace it to a code update, and uncover the bug—your CycleOps dashboard just got x‑ray vision.
Today, we’re excited to announce a direct integration with Research‑AG’s canister History Tracker, allowing developers to connect memory spikes and cycle burn surges back to the exact deployments that triggered them.
Today we're releasing the ability to create new canister smart contracts in seconds, and to manage them directly from your CycleOps dashboard.
No terminal. No dfx canister create ...<what args next?>. Just a few clicks.
Today, we're rolling out ICRC deposits for CycleOps, meaning you can fund topups directly from your SNS with a single Transfer SNS Treasury Funds proposal 🎉
Did you know that your canister can suddenly stop saving new data if it’s on a busy subnet and you haven’t set it up to reserve enough cycles for new memory allocations?
CycleOps now has monitoring and alerting features to help you stay on top of the important but lesser-known "reserved cycles" canister configuration. Here's everything you need to know about reserved cycles, and how you can set up alerts for them in just a few minutes!