Skip to content
Axolix
4 min read

ERM and Ducky Shut Down: How to Choose an ERLC Platform That Won't Disappear

ERM and Ducky — the two largest ERLC platforms of 2026 — both shut down within five weeks. What the shutdown notices actually said, and the compensating signals to look for when choosing a platform that won't disappear.

  • ERLC
  • ERM
  • Ducky
  • shutdown
  • guide

Research date: 10 November 2026. All facts below come from official shutdown notices, source repositories and archived pages. Part of the ERLC platform comparison series.

Within five weeks in late 2026, two of the largest ERLC management platforms stopped existing. If your community ran on either — or if you're choosing a platform today — their shutdowns are the most useful data points in the market.

What happened

Ducky — claimed 15,107 communities and roughly 991,000 users — shut down on 11 August 2026. Its official notice is unusually candid: interest and motivation "significantly decayed", and the codebase was "unnecessarily complex and messy". ERLC API keys were deleted from its database and a global key deactivation was requested. The data-export tool stayed up for two months and was then taken offline on 12 October 2026; all data has been deleted. The notice recommends Melonly as a migration destination. Ducky's v1 source remains on GitHub under AGPL-3.0.

ERM (Emergency Response Management) — claimed 28,000+ servers, free, whitelabel — shut down on 12 September 2026. Its GitHub readme states it "has shut down forever"; the readme documents the date and the release of the source under CC BY-NC-SA for self-hosting, but does not state a reason. Notably, ERM's last major engineering act was migrating to the ER:LC API v2 in July 2026 — weeks before folding. Its domain now redirects to a data-export tool. A small community fork ("ERM CE") has appeared since; its own site was unreachable during our fact-check pass, so its claims remain unverified.

Read those together and the lesson isn't "the market is dying" — demand didn't leave either platform, and the survivors are shipping actively. The lesson is that success at scale is not self-sustaining: 15,000 and 28,000 communities could not keep two volunteer-scale teams motivated and unblocked.

What this means when you choose a platform today

1. Prefer published engineering evidence over popularity. Changelogs with dates (Melonly's V5.12.1, October 2026; Boomerang's Panel launch, 28 October 2026), public status pages and real documentation predicted survival better than install counts — Central's 32,200 servers did not come with any of those. See the full comparison.

2. Ask about API v2 — it's the canary. Maintaining an ER:LC integration is real, ongoing work: rate-limit handling, error-code changes, endpoint migration. A vendor that hasn't touched its integration documentation in two years (Trident's docs still describe the 2024-era PRC API) may be one upstream change away from a bad month. What the API demands.

3. Own your data. Ducky deleted everything on schedule; the export window was two months. Ask every vendor: what do you store, how do I export it, in what format, and can I self-host if you fold? ERM's answer (open source, self-hosting guide) is why some of its communities kept operating. Ducky's communities that hadn't exported lost their rosters, infractions and histories entirely.

4. Know who operates the platform — and how concentrated that is. A solo developer is not disqualifying — Axolix itself is a solo-developer project, and Boomerang is a sole trader — but concentration means the bus factor is the platform factor. Look for compensating signals: multiple maintainers, a registered entity, public status pages, published incident history.

5. Don't pay lifetime fees without thinking about it. A lifetime licence is only worth what the vendor's expected survival is. Ducky's Plus+ subscribers were paying right up to the shutdown.

If you're migrating from ERM or Ducky now

  • From ERM: export via the redirect tool at ermbot.xyz while it exists, or self-host the CC BY-NC-SA source per the repo's guide.
  • From Ducky: the export tool closed on 12 October 2026 and data was deleted — rebuild from your own Discord records; the shutdown notice's Melonly recommendation is one documented path, and the free tiers of Boomerang, CADLY and County Control are alternatives worth trialling in the same week.
  • Whichever destination: re-run your Roblox verification under the new platform, and re-establish role mappings — that data did not come with you.

The ecosystem this year proved both halves of the same truth: platforms here can die suddenly, and the good ones are easier than ever to evaluate before you commit.