When the server dies, should the machine still work?

I own a cloud-dependent 3D printer, and I’m less worried about losing remote monitoring or cloud profiles than losing the machine’s basic operating path. If the vendor shuts down its servers, I think the printer should still be able to run jobs locally, home, calibrate, expose diagnostics, and support ordinary repairs without requiring an account.

That doesn’t mean manufacturers must provide every online feature forever. A permanent maintenance mode could use signed local firmware, rollback protection, offline logs, recovery documentation, and a clearly defined end-of-support image that remains installable after the servers disappear. The security and safety concerns are real, but they don’t automatically require permanent server dependence.

Glowforge’s documentation is unusually explicit that internet access is required for use, while MakerBot’s CloudPrint retirement in late 2025 shows how account-based workflows can vanish—even though it did not prove every affected printer was completely unusable. Should an offline fallback be a right-to-repair requirement, an industry standard, or simply a buying criterion for makers? Have you seen a device become unusable after cloud support ended?

I’d define the requirement around a local control plane, not “offline mode” as marketing language. The machine needs a documented recovery path, local homing and calibration, and a way to load jobs. Signed firmware can preserve the vendor’s trust model; the server should not be the only place where that trust can be exercised.

The security objection is legitimate, especially for machines with heaters, lasers, or high-force motion. But “only our server can authorize maintenance” is a much broader claim than “only signed firmware may run.” A model-specific final image with a protected recovery path seems like a reasonable compromise.

I’d make it an explicit buying criterion before making it a mandate. Buyers already compare build volume and serviceability; offline operation belongs on that list. If enough makers reject account-locked hardware, vendors get a commercial signal without being forced to support cloud features indefinitely.

The MakerBot example is useful precisely because it needs careful wording: CloudPrint and login services ended, but official guidance still pointed some users to legacy software, USB, or offline workflows. I’d like manufacturers to publish the final supported image and compatibility matrix at launch, not during shutdown panic.