Check a release's system requirements against what you run
System requirements decide whether software will install and run at all: supported operating systems and versions, minimum hardware, required runtimes and databases, browsers and network access. They are usually in an installation guide or release notes and differ between releases. Ask Search+ "What does this version require to run on Linux?" and the answer cites the requirements table so you can compare it with your environment.
Creating an account needs no payment.
Last updated October 2026
How to check system requirements with Search+
- Upload the docs for the exact release
Add the installation guide and release notes for the release you plan to install. Requirements often tighten in a new major version.
- Ask per platform and per component
Ask separately about the server, the client and any database or runtime, and name your platform. Requirements tables are often split by role.
- Look for supported versus minimum
Ask whether a value is a minimum, a recommendation or a tested configuration. Open the citation to read how the documentation words it.
Questions to ask about system requirements
Which operating systems and versions does this release support for the server component?
What minimum and recommended memory and CPU does the documentation give?
Which runtime or database versions are required, and are newer ones supported?
Which browsers are supported for the web console?
What ports or outbound connections does the installation need?
Did any requirement change since the previous release?
What to look for in system requirements
Documentation often gives a minimum that lets the software start and a recommendation for real workloads. Plan to the recommendation unless you are testing.
A platform listed as supported has usually been tested by the vendor. Versions not listed may work but are often outside the vendor's support.
Servers, agents, clients and databases often have separate requirement tables. Check each one you will install.
Release notes may announce that a platform will be dropped in a future version. That affects your upgrade path.
Upload both releases' documentation and ask Search+ to compare their requirements, with citations to each.
Search+ does not invent page or section locations that the documentation does not contain.
Requirements wording you may see and what to ask
| Wording you may see | What it usually signals | A follow-up question |
|---|---|---|
| "minimum" | Enough to start, not to perform | What is the recommended value for production? |
| "supported platforms" | Vendor-tested configurations | Is my exact version on the list? |
| "certified" | Formally validated configuration | What is the difference between certified and supported here? |
| "deprecated platform" | Support will end | In which release is support removed? |
| "or later" | Newer versions accepted | Is there an upper limit on the version? |
| "prerequisites" | Software to install first | In what order should the prerequisites be installed? |
What are system requirements?
System requirements are the hardware, operating system, software, browser and network conditions that a product's documentation states are needed to install and run it, usually split into minimum and recommended values per component.
System requirement questions
Can Search+ check whether my server meets the requirements?
Can it find requirements spread across several guides?
Can it tell me what changed in the requirements for a new release?
Does it distinguish minimum from recommended?
What if the requirements are in an image of a table?
Can I plan an upgrade from the answer alone?
Know what the release needs before you install it
Start a workspace, upload the installation guide and release notes, and ask what your platform needs.
Start a workspace