Decision
Cancelled Akountify subscription. Apify shadow test passed: Reina confirmed 8 engagements marked Missed by the legacy scraper were in fact Complete on the live post (0% accuracy on those rows). Michael called the switch the same day: “We are gonna switch over today.”
Supersedes and closes: AWS + Accountify to Apify Migration Evaluation (go/no-go was Aug 12; shadow ran through Aug 20 before final call).
Context
The Aug-06 decision set a one-week Apify shadow test with a go/no-go by Aug 12. The shadow ran longer; Hermes posted a comparison in Megaphone showing 8 paid engagements on the live post that the legacy scraper called Missed ($110 at stake in that sample alone). Reina spot-checked and confirmed all 8 as Complete. Rafael also confirmed no concerns with the cancellation: “Since we saw that the Apify solution works even better.”
Separately, Rafael flagged and confirmed the Megaphone dev DB was already stopped (Hermes had done a prior AWS cost sweep). No further action needed there.
Options Considered
- Keep Akountify + AWS: rejected - Apify accuracy clearly superior, cost delta too large.
- Continue shadow without full switch: rejected - accuracy proof was conclusive.
Consequences
- Akountify subscription cancelled by Michael on 2026-08-20.
- Apify is now the sole engagement-confirmation system for Megaphone.
- Megaphone dev DB remains paused (already stopped before this decision).
- Rafael to monitor for engagement bugs over the next few days.
- Cost savings details: see Owner tier.
- Watch: any engagement accuracy regressions flagged by Rafael in eng.
Source: eng thread p1787247639818729, Megaphone thread p1787230939200759