macOS 27 May Kill Time Capsule, FOSS Fights Back

macOS 27 is poised to finally sever the last thread keeping Apple's discontinued Time Capsule backup appliances functional, as the operating system marches toward dropping support for AFP (Apple Filing Protocol) and SMB1 — the only two network protocols these devices speak. But the open-source community, armed with the knowledge that Time Capsules run NetBSD under the hood, is digging in to give the hardware one last shot at relevance.

Apple killed the Time Capsule product line back in 2018, but millions of the white and silver boxes still sit in closets and home offices worldwide, dutifully serving Time Machine backups over aging network protocols. With macOS 27 expected later this year, those devices face a hard cutoff that no firmware update can fix — because Apple stopped issuing those years ago.

Key Takeaways

• macOS 27 is expected to fully deprecate AFP and SMB1, the only protocols Time Capsule supports
• Apple's Time Capsule internally runs a modified NetBSD kernel, opening the door to community firmware
• No official Apple firmware updates have shipped for Time Capsule since approximately 2020
• FOSS developers are exploring custom firmware to add SMB2/SMB3 support to the aging hardware
• Millions of Time Capsule units remain in use globally despite the 2018 discontinuation
• The situation highlights a growing tension between planned obsolescence and right-to-repair movements

Apple's Protocol Purge Has Been Years in the Making

Apple began its slow retreat from AFP back in macOS 10.15 Catalina (2019), when it started defaulting to SMB for network file sharing. Each subsequent release has further deprioritized the legacy protocol, with macOS Ventura and Sonoma issuing deprecation warnings that most users ignored.

The shift makes technical sense. AFP was designed in the 1980s for AppleTalk networks, and while it served Mac users well for decades, SMB2 and SMB3 offer superior performance, better security, and cross-platform compatibility with Windows and Linux systems. Apple's own NAS integration in macOS now relies exclusively on modern SMB.

But Time Capsule never got the memo. The device's AirPort Utility-managed firmware caps out at AFP and SMB1, with no path to upgrade. Unlike a Mac mini or a Synology NAS, Time Capsule's firmware is locked down and hasn't received meaningful updates in roughly 5 years.

Inside the Box: NetBSD Powers Apple's Forgotten Hardware

What makes the Time Capsule situation uniquely interesting — and potentially salvageable — is what runs beneath its polished exterior. Apple built the Time Capsule and AirPort Extreme on a modified NetBSD kernel, one of the oldest and most portable open-source operating systems in existence.

This isn't speculation. Security researchers and hardware hackers have documented the NetBSD foundation extensively over the years. The choice made sense for Apple at the time: NetBSD's legendary portability meant it could run on the custom ARM-based hardware Apple selected, and its BSD license allowed Apple to use it without open-sourcing proprietary modifications.

The NetBSD foundation creates a crucial opening for the FOSS community. Unlike a completely proprietary embedded OS, the underlying system is well-understood, well-documented, and actively maintained by the open-source community. Key technical details that matter:

• The Time Capsule uses an ARM-based processor that NetBSD still actively supports
• The network stack is derived from NetBSD's own, meaning modern protocol support exists upstream
• Boot chain analysis has been partially documented by security researchers
• Storage management uses a standard disk format accessible to BSD tools
• The hardware itself — gigabit Ethernet, 802.11ac Wi-Fi, SATA drive bays — remains perfectly capable

The FOSS Community Grabs a Shovel

Several community efforts are now converging to breathe new life into Time Capsule hardware. The approach varies, but the core idea is consistent: replace Apple's frozen firmware with something that speaks modern protocols.

One approach involves flashing a custom NetBSD image onto the device, essentially upgrading the OS Apple abandoned. Because upstream NetBSD has long supported SMB2 and SMB3 through the Samba project's open-source implementation, a reflashed Time Capsule could theoretically negotiate modern connections with macOS 27 and beyond.

Another path explores running OpenWrt or similar embedded Linux distributions. While this requires more adaptation work — the Time Capsule's hardware isn't a standard router target — it opens up an even broader ecosystem of software. An OpenWrt-based Time Capsule could serve as a NAS, a modern Wi-Fi access point, or even a lightweight home server.

The challenges are real, however:

• Apple's boot chain includes secure boot mechanisms that complicate firmware replacement
• Driver support for the Time Capsule's specific Wi-Fi chipset varies across open-source projects
• The 2TB and 3TB hard drives in many units are aging and prone to failure
• No single project has yet produced a turnkey solution for non-technical users
• Bricking risk remains significant without proper documentation

Planned Obsolescence Meets the Right-to-Repair Era

The Time Capsule situation is a textbook case of planned obsolescence colliding with hardware that has no physical reason to stop working. The drives spin, the Ethernet ports link up, the Wi-Fi radios broadcast — but a software decision made in Cupertino renders the entire device useless.

This pattern is increasingly common across the tech industry. Google's Nest devices, Amazon's early Echo speakers, and Sonos's controversial 'legacy' product cutoffs all follow the same playbook: cloud-dependent or protocol-dependent hardware gets orphaned when the manufacturer moves on.

What distinguishes the Time Capsule is the NetBSD escape hatch. Most orphaned consumer electronics run deeply proprietary firmware with no open-source equivalent. The Time Capsule's BSD heritage means the community has a realistic — if technically demanding — path forward.

The EU's Digital Markets Act and evolving right-to-repair legislation in the United States add political momentum. While these laws primarily target smartphones and laptops today, the principle extends naturally to networking equipment. If Apple won't update the firmware, should users have the legal and technical right to do it themselves?

What This Means for Time Capsule Owners

For the average Mac user with a Time Capsule gathering dust, the practical implications are straightforward. Once macOS 27 ships, Time Machine backups to the device will likely stop working entirely. The workaround options fall into 3 categories:

Do nothing. Accept that the Time Capsule is end-of-life and migrate to a modern solution. A Synology DS223 or similar 2-bay NAS runs about $170-$250 and supports Time Machine natively over SMB3. Apple's own iCloud backup, while not a direct replacement, covers many use cases.

Stay on macOS 26. Delaying the upgrade buys time, but Apple's security update window for older macOS versions typically spans only 2 years. This is a stopgap, not a solution.

Go the FOSS route. For technically inclined users willing to accept some risk, community firmware projects offer the most sustainable path. Monitor projects on GitHub and the NetBSD mailing lists for turnkey images as they mature.

Looking Ahead: A Test Case for Hardware Longevity

The Time Capsule saga will likely become a reference point in broader debates about hardware sustainability and software support lifecycles. Apple sold these devices at premium prices — the 2TB model retailed for $299, the 3TB for $399 — with an implicit promise of long-term reliability. The hardware delivered on that promise. The software did not.

If the FOSS community succeeds in producing a stable, user-friendly custom firmware, it would demonstrate something powerful: that open-source software can extend hardware lifespans well beyond what manufacturers intend. It's the same principle that keeps ThinkPads running modern Linux a decade after Lenovo's last driver update, applied to networking hardware.

The timeline is tight. macOS 27 is expected at WWDC 2025 in June, with a public release in the fall. Community developers have months, not years, to produce something usable. The hardware is aging, the drives are failing, and each passing month shrinks the pool of functioning units.

But the shovel is in the ground. And if NetBSD's 30-year track record of keeping old hardware alive is any indication, the Time Capsule's story may not be over yet.