DFINITY Pushes Ahead With Long Lived Cloud Engine Plan in New ICP Proposal

A new governance proposal on the Internet Computer network is aiming to expand DFINITY’s cloud testing infrastructure with the addition of a new data centre designed to support a longer term cloud engine environment.

Proposal 141909, which is now live for voting on the $ICP network, outlines plans to add a new data centre identified as “dm1” to host cloud engine nodes. The move forms part of DFINITY’s broader effort to improve testing conditions for integrations and applications running on the Internet Computer.

According to comments shared by DFINITY team member rbirkner, the organisation has so far relied on short lived test cloud engines focused on rapid experimentation and feature testing. Those environments were built to move quickly without long term maintenance concerns.

The proposed long lived cloud engine is intended to serve a different purpose. DFINITY says it wants an environment capable of running integrations and applications over extended periods, allowing developers to assess stability, adaptability and maintainability under more realistic operating conditions.

The initiative is also tied to DFINITY’s ongoing “dogfooding” strategy, where the organisation actively uses its own infrastructure and tools internally to identify limitations and improve product readiness before wider adoption.

Supporters of the proposal argue that persistent testing environments are necessary as decentralised applications become more complex and require longer operational cycles. A stable cloud engine could help surface performance issues, compatibility concerns and maintenance challenges that may not appear in short term testing setups.

The proposal comes as the Internet Computer ecosystem continues to push towards broader enterprise and developer adoption, with infrastructure reliability remaining a key area of focus across decentralised cloud platforms.

DFINITY noted that additional proposals are expected to follow, including updates to node operator records and the eventual creation of the engine itself.