Still active, and we’re still the topping up a significant portion of the ecosystem. TLDR: you can use the tool Ohshii built to buy cycles with $$, and you can then allow CycleOps to smartly allocate those cycles to your apps over time. These services actually work well together. The difference is that CycleOps smartly distributes your cycles to canisters based on defined topup rules and those canisters’ usage over time. It also comes with monitoring analytics and topup history over time so you can track costs and predict expenses. Not to mention alerts for when you run low on ICP or cycles. You can currently pay for topups in ICP or cycles, so if you want to go the credit card route I’d point your agent at docs.cycleops.dev/docs/cycle… and have it put the cycles you’ve paid for onto the ledger so that you can approve CycleOps to smartly distribute them across many apps and they aren’t all stuck on a single canister. Let us know if you have any questions

3 years now and counting

To learn more about maintaining your topup rules, read more on the CycleOps changelog 👇 docs.cycleops.dev/changelog/…

New on CycleOps - smart topup rules 🧠 Canister freezing cycle balance thresholds can increase over time 🥶, especially for canisters with large memory requirements. CycleOps smart topup rule suggestions help you adjust your topup thresholds to stay unfrozen and running 🔋

And to learn more about how to set up push notifications on your CycleOps account - read more on the CycleOps changelog 👇👇 docs.cycleops.dev/changelog/…

CycleOps’ push notifications feature is powered by @mr_research_ag's notification service, an open-source web push stack for Internet Computer apps. If you want to bring push notifications to your dapp, check out github.com/research-ag/notif…

New On CycleOps - Push Notifications! For the busy dev on the go - get critical canister alerts 🚨 for topups, low balance, memory, and more pushed directly to your phone 📲

If you want to learn more about the workflow, read the full article or send us a message! docs.cycleops.dev/changelog/…

You can submit feedback requests in the app, or just DM us on this app. This workflow heavily leverages human judgement, but agents do all of the leg work, including writing all the code. When it comes to fixing exceptions, the pipeline is even simpler.

We've released more bug fixes and UI improvements in the past month than ever before. It's all thanks to an agentic workflow we built based on our old purely human-driven processes. If you use cycleops.dev or icptopup.com, submit more requests! If they're actionable they'll probably be done in a week.

We hope this tool helps you identify your most impacted services and realize future cost savings. Have questions or curious about the upcoming protocol memory price changes? Check out the changelog to learn more 👇 docs.cycleops.dev/changelog/…

It also displays a full breakdown of how the memory cost increases will impact each individual canister, ordered by the canisters in your account that utilize the most memory

The new memory cost page 🗒️ - Estimates how much your account's overall memory costs will increase - Shows your new estimated overall cycle costs (including both memory + compute costs), and the overall % cost increase from the new memory price changes.

Hey IC devs 👋 Wondering how the upcoming 2.5x protocol memory cost changes will affect your cycle bill? We were curious too! 😅 So we built a dedicated memory cost change dashboard so that you can use to quickly understand and plan for the before and after cost impact. 🔥 🧵

Ready to get started? Manage your canisters on cycleops.dev Read about it on the changelog: docs.cycleops.dev/changelog/… #InternetComputer @DFINITYDev

Deposit more ICP to fund your canisters, from the beach. (7/7)

Set up a new automatic top-up rule, while you’re riding transit. (6/7)

Set up monitoring for your SNS canisters, during your launch meeting. (5/7)