Discover projects. Understand their uses.

A map from project to practical use

A name and a link are only the starting point. OpenViST explains a project’s purpose, supported tasks, technical stack, requirements and documented constraints. Where sources support concrete steps, a profile includes a source-based guide.

Three project roles

• Infrastructure: chains, protocols, model runtimes, APIs and data services that other systems depend on.
• Builder tools: frameworks, SDKs, libraries and developer tools for creating or integrating software.
• Apps: applications and agent systems used directly to complete a task.

These roles complement the four subject areas; they do not replace the project’s specific resource type. Research projects may remain outside these three roles until their practical role is documented.

What belongs here

A project must fit AI, agents, blockchain or crypto and have sufficient official evidence to explain its function. An official repository or technical documentation is preferred. Closed-source applications may qualify through official product documentation and publisher-identified store records. Appearing in a store search or mentioning AI is not enough.

Evidence has levels

Source checks establish what the linked materials document. They do not prove that OpenViST ran the software, audited its security or confirmed every compatibility claim. A source-based guide is separate from an execution test. Unknown requirements stay unknown.

Five ways to use OpenViST

• Directory: discover technical projects, official resources, documented tasks and practical guides.
• Recipes: inspect reusable scripts organised by language and version, with requirements, sources and recorded test scope.
• Tools: use free utilities for tasks such as JSON, CSV, text comparison and code images. Browser utilities process input locally. The hosted Link Auditor instead requires an account and website-control verification and runs a bounded audit on OpenViST infrastructure; a self-hosted download is also available.
• Learn: follow free beginner lessons with explanations, commands, exercises and source links. Start with the ten-lesson Terminal & VPS route, then connect the foundations to practical recipes and tools.
• Journal: understand architecture choices, integrations and trade-offs connected to the projects we cover.

Directory browsing and project search share the same catalogue. Search and filters narrow its published records. Selected starting points are editorial selections, not popularity rankings.

Independent and evolving

OpenViST is an independent project based in Luxembourg. Inclusion cannot currently be purchased. Project representatives may submit evidence and corrections; verification does not give them control over independent editorial conclusions. Read the Editorial Policy for our standards.

Technical crypto coverage

Wallets, networks, protocols and documented crypto tools remain part of the Directory. Profiles explain their technical purpose and practical use. OpenViST does not offer a catalogue of coins or listed shares, price charts or investment rankings.

OpenViST Recipes

Our open script library connects documented tasks to practical examples for AI, agents, blockchain and crypto. OpenViST prepares library drafts, checks their sources and records independent tests before publication. Readers can inspect, adjust and download published examples for their own environment, or propose improvements for review. Test reports describe their actual scope; they do not guarantee production behavior.