Meet CycleOps. Proactive, automated, no-code canister management for the Internet Computer

Integrated Canister History :scroll:

CycleOps is 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.

Highlights :sparkles:

Metric overlays: Code change events are now layered directly onto your cycle balance chart–so you can easily

  • spot the update that introduced a performance bug :bug:
  • or show off the cycle savings from your code optimizations with the team :raising_hands:

History Timeline: A full timeline of controller changes, installs, and upgrades with WASM hashes with the actor who made the change—perfect for audits and post-mortems

Give it a spin – canister history is now live for all canisters monitored through CycleOps - no additional setup required :tada:

Learn more about canister history and other new CycleOps features in the changelog :backhand_index_pointing_down:

:folded_hands: A big thanks to @timo for his help with this integration!

Is there a way to use it with a caffine ai canisters? I tried adding it but it says it needs to be added as a controller and i don’t know how to do that

A bit of a late reply, sorry, but unfortunately caffeine doesn’t allow you to set controllers on your canisters, as far as I know.

Mobile UX Update :mobile_phone:

We just pushed a broad set of fixes to the CycleOps mobile experience, and it finally feels properly usable on a phone. I’ve been using it away from my desk and it’s a night-and-day difference.

mobile-external

We posted a short X thread with 7 quick clips showing the flows in action: https://x.com/CycleOps/status/2019077278219538819

Feedback request:

  1. Which mobile workflow matters most to you?
  2. What still feels awkward / slow on mobile?
  3. Any “on-the-go” flows you want us to prioritize next?

I’m currently just getting the spinny thing at the site on desktop.

Looking forward to the mobile version!

Thanks Austin! This bug cropped up yesterday in between releases. Should be fixed. Let me know if it persists.

A Tool to Answer Your Protocol Memory Price Change Questions

New on CycleOps!

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

Drill down into how your memory costs are projected to change account-wide

Or on a per-canister basis

Learn more about how you can use this tool on the CycleOps Changelog :paperclip: