Call for Tool Showcase Submissions

The 26th International Conference on Runtime Verification (RV 2026) invites contributions to its Tool Showcase, dedicated to showcasing mature, emerging, and experimental tools in runtime verification and closely related areas.

Presenters will present their tools during a dedicated Tool Showcase session.

Note that participation in the Tool Showcase does not require having a paper at RV.

Dates

• Submission Deadline: August 10, 2026
• Notification: August 17, 2026

All deadlines are anywhere on Earth.

Objectives and Scope

The Tool Showcase aims to map out the landscape of available RV and RV-related tools and to create an openly accessible overview of their capabilities and performance characteristics. By bringing these tools together in a common forum we aim to:

• Provide a clear snapshot of the current state of the art in RV tooling.
• Encourage reproducibility and transparency in tool evaluation.
• Motivate performance and usability improvements across multiple dimensions.
• Foster collaboration between research groups working on complementary aspects of runtime verification technology.

There will be a light review process for the tool showcase, mainly evaluating relevance to RV, ease of running the tool, and clarity of accompanying extended abstract. Everyone is welcome to contribute a tool package (details below), and present it at the conference in the Tool Showcase.

We solicit submissions of tools related to runtime verification and adjacent areas, including (but not limited to):

• Specification languages and monitoring frameworks
• Online and offline monitoring engines
• Stream-based and trace-based analysis tools
• Parametric monitoring and decentralized monitoring tools
• Hybrid systems and cyber-physical systems monitoring
• Security and privacy monitoring tools
• Testing, enforcement, and repair frameworks
• Benchmarking infrastructures and trace repositories
• Toolchains integrating verification, testing, and deployment

Tools may target any application domain (e.g., distributed systems, blockchain/smart contracts, embedded systems, cyber-physical systems, AI systems, etc.). Both academic prototypes and industrial-strength tools are welcome.

Outcomes of Tool Acceptance

Accepted tools will:

• Be presented in a dedicated Tool Session at RV 2026.
• Be included in a centralized RV tool and benchmark repository.
• Have their associated extended abstracts published in the RV 2026 proceedings.
• Contribute performance data to a shared overview of the RV tool ecosystem.

Our broader objective is to catalyze collaborative progress in runtime verification tooling—encouraging joint efforts to improve tools along any interesting dimension, including performance, formalism, scalability, domain applicability, usability, and integration.

Contribution Requirements

Each contribution must include:

1. The Tool

   • A working implementation (prototype or production-ready). See Submission Instructions below.
   • An extended abstract (up to 4 pages long) describing the supported formalisms, what the tool does, and its main features, highlighting key results where applicable. Please submit as PDF. This abstract should also contain links to access the tool, as described under Submission Instructions below. Abstracts for accepted tools will appear in the Conference Proceedings.
   • A User Guide, containing at least clear installation and usage instructions. Please submit as a PDF.

2. A Benchmark Suite

   • One or more benchmarks the tool can run against out-of-the-box.
   • Clear instructions for execution of each benchmark.
   • Description of benchmark characteristics (e.g.,formalism, trace size, property complexity, domain).
   • Metrics reported (e.g., runtime, memory usage, etc).

The goal is not to rank tools competitively, but to build a shared benchmark repository that enables meaningful comparison and highlights strengths along multiple dimensions, such as:

• Runtime performance
• Memory consumption
• Scalability
• Supported formalisms
• Domains
• Modularity and extensibility
• Ease of integration and usability

Submission Instructions

To keep things simple, authors should include, in their extended abstract, a link to download the tool. This should be source code rather than pre-compiled binaries since the latter have OS dependencies that might make it hard for us to run the tool. For example, the tool source code could be hosted on a github repo, in a Google drive where a zip can be downloaded, a personal webpage, etc. The tool could also be web-hosted, i.e., it is run through the browser with nothing to download.

What matters is that anyone with the link can access the tool at that link without needing to have special permissions. (Usually this could be checked by accessing the link in an “Incognito” browser window, aka a new Fire window in DuckDuckGo, aka a new window in TorBrowser, etc).