From promising tool to practical use.

The listed edition has an ongoing free way to use it. A required host platform, hardware, account, or service may have a separate cost. Each project page explains the free scope and known requirements.

No. OIC is open to discovery and participation across business models. Listings label software as open source, source available, or closed source and link to its actual terms. Those labels describe different rights.

Start with its capabilities, free scope, platform needs, release stage, publisher and documentation. Follow the original project link and evaluate the tool under your own security and change-control process. A catalog page is a starting point for that decision. Read the industrial use and security guide before connecting anything to a plant.

Each page identifies its publisher and source. Publisher-submitted listings are distinguished from entries OIC curated from public information. A listing does not make its author an OIC steward.

A useful industrial tool or edition with genuine ongoing free use, a responsible publisher, clear terms, practical details and a safe route to try or obtain it. The Listing Charter explains the full admission standard.

No. The listing profile needs a public repository so it can be reviewed. The application itself may be open source, source available or closed source. Keep your software, releases and support where you choose.

No. The form prepares a YAML listing in your browser and lets you download it. To request publication, place the profile in a public repository and open a listing issue. A maintainer reviews it before it appears on OIC.

Registered profiles are checked for changes. OIC reviews each proposed update against a specific source commit before publication; an unsuccessful refresh leaves the last approved listing visible.

Automated checks catch malformed profiles and unsafe link formats. A maintainer checks the free path, attribution, terms, requirements, links and practical usefulness. This is catalog admission review, including for founder projects.

No. The catalog does not certify software or independently verify downloads. OIC is developing separate, scoped evaluation methods that identify exact versions, test conditions, observations and limitations. Public verification claims need their own evidence and review.

Yes. Try a tool, report a missing requirement or offer a concrete improvement. Industrial practitioners can help identify the questions and failure modes that future evaluations should address. See ways to take part.