Requirements should be based on tested builds—not guesses.
Sage does not currently publish a final production hardware matrix or minimum system requirements. This page defines how compatibility information will be communicated as validated builds become available.
Any earlier references to “certified hardware” or proprietary Vidran silicon should not be treated as a current public compatibility commitment unless supported by a future formal announcement and release documentation.
HARDWARE
Validated configurations
Future support lists should identify exact processor architecture, memory, storage, graphics, networking and peripheral requirements for each release channel.
SOFTWARE
Application compatibility
Compatibility claims should distinguish native Sage applications, supported runtimes, web applications, interoperability layers and unsupported software clearly.
LIFECYCLE
Support windows
Public releases should identify update eligibility, support duration and end-of-support conditions so organisations can plan responsibly.
FUTURE REQUIREMENTS FORMAT
Every supported release should publish enough detail to make deployment decisions.
Minimum
The lowest configuration on which Vidran has validated the release for its stated use.
Recommended
Configurations appropriate for smoother performance or more demanding workflows.
Known limitations
Unsupported hardware, drivers, peripherals or features documented explicitly.
Upgrade path
Supported transitions between builds, backup expectations and recovery requirements.