TitanCSA

Windows tools / Developer SDKs

Find the right tool for your Windows workflow.

Driver SDKs, virtual devices, input tools and diagnostics. Start with the job you need to do, then follow the matching guide.

Public documentation · Native Windows tools · Project-specific licences

Choose with evidence. Versioned source, documented first runs and an open input benchmark dataset.

Read the scope and known issues ↗

Project catalogue

Start from your use case.

Explore 60 projects and SDK source repositories across ten workflows. Preview limitations and separate driver requirements remain visible.

60 entries shown

Physical input

7 entries

Keep an integration using the historical Interception C API.

Start and scope

Use this edition's matching driver and SDK files for the legacy API.

Interceptor

Driver SDK

Read or remap keyboard, mouse and gamepad input in one integration.

Start and scope

Combined edition; supported hardware and device profiles are documented in its repository.

Work with a selected physical keyboard or mouse.

Start and scope

Requires driver access and explicit device selection.

Observe and transform reports from a supported physical gamepad.

Start and scope

HID, XInput/XUSB and GIP coverage depends on the documented hardware and profiles.

Integrate the Windows edition covering several input families.

Start and scope

Follow this edition's examples and use its matching driver package.

Build a gamepad-specific integration.

Start and scope

Check protocol and hardware support before a live test.

Build a keyboard and mouse filter integration.

Start and scope

Use the examples and installation instructions for this edition.

SDK integration

7 entries

Integrate Interceptor from several package ecosystems.

Start and scope

Start with the chosen wrapper's example and check its supported operations and native dependencies.

Integrate keyboard and mouse input into Node.js or TypeScript.

Start and scope

Specialised adapter; live use requires the Interceptor Keyboard & Mouse driver.

FyraInput

SDK sources

Find FyraInput user-mode SDK sources and packages.

Start and scope

The package repository does not include a kernel driver or installer.

Find packages for the gamepad-specific FyraInput integration.

Start and scope

Check this SDK's API and install the product dependencies separately.

Find FyraInput packages for keyboard and mouse integration.

Start and scope

Commands awaiting publication are identified in the README.

FyraDevice

SDK sources

Find FyraDevice user-mode packages.

Start and scope

Drivers, activation and installers are supplied separately from this package repository.

Create virtual USB devices using raw device descriptions.

Start and scope

Use this edition's driver and examples; read its evaluation and UdeCx limits.

Remapping and automation

7 entries

Write AutoHotkey scripts targeting a selected keyboard or mouse.

Start and scope

Adapted from evilC's AutoHotInterception; check attribution notices and the supported AHK versions.

Edit and inspect GPC gamepad scripts on Windows.

Start and scope

Independent project; read compatibility diagnostics rather than assuming every script or device works.

Adjust and visualise a joystick response curve.

Start and scope

Uses Interceptor Gamepad & Controller; select supported hardware.

Configure gamepad remapping, scripts and macros.

Start and scope

Complete example application; inspect input and output during an explicit test.

Edit keyboard/mouse remapping, scripts and macros.

Start and scope

Native application with a separate matching input-driver dependency.

MouseControl

Application

Run relative mouse movement code while one selected keyboard or mouse trigger is held.

Start and scope

Code editor with move/wait and an optional loop; selecting a trigger replaces the previous one. Release cancels future movements; accepted packets cannot be recalled. Use --preview for the offline interface.

Find the entry point for the Titan input-tool collection.

Start and scope

Follow each component's link and its own installation guide.

Input testing and QA

7 entries

Adjust gain, axes and motion for a selected mouse.

Start and scope

Per-device adjustments; live use requires Interceptor Keyboard & Mouse.

Prepare a gamepad repair or QA report.

Start and scope

Observe axes, drift and report cadence; export HTML/CSV without remapping buttons. Cadence is not end-to-end latency.

Test which applications may open a selected controller.

Start and scope

Rules apply to new opens; already-open handles keep their access.

HID-Fixture-Studio

ApplicationOffline validation first

Edit a HID descriptor and validate a fixture.

Start and scope

Start with offline validation; live tests require Vdevice.

Input-CI-Runner

ApplicationOffline validation first

Run JSON HID-report fixtures in a test pipeline.

Start and scope

Offline validation and explicit live runs are separate. Enqueuing a report does not prove an application consumed it.

Record a local input sequence and replay it for authorised QA.

Start and scope

Select one keyboard or mouse; recording and replay start explicitly. JSON/CSV exports are available.

TitanCSA-Benchmarks

DatasetRead online

Inspect independently received virtual-input measurements and reproduce the lab.

Start and scope

Public Hyper-V dataset, protocol-specific results and failed runs. An open Vdevice WDF teardown incident is documented; no physical-latency or universal speed claim.

Open WDF stability finding ↗

Virtual USB and serial

5 entries

Vdevice

Driver SDK

Create and control virtual USB devices through descriptors and reports.

Start and scope

Use the matching device-family examples. Driver evaluation rights are separate from the user-mode SDK.

Open WDF stability finding ↗

Explore a specialised virtual mouse-input integration.

Start and scope

Read this edition's report contract and dependencies.

Study Modbus RTU and SCPI simulation models.

Start and scope

Source preview: live COM startup has not been validated and a VM stall was observed. Usable release binaries are withheld; not ready for production deployment.

Study a CDC ACM backend and virtual serial-cable scenarios.

Start and scope

Source preview: no real COM transfer has been validated and a VM stall was observed. Usable release binaries are withheld; not ready for production deployment.

Transport one selected WinUSB interface over an authenticated, encrypted connection.

Start and scope

Bounded WinUSB bridge; not a universal redirector for arbitrary USB devices or classes.

Media and remote workstations

4 entries

Send your own images to an AVStream virtual camera.

Start and scope

Documented contract: BGR24, 640×480, 30 fps. Driver evaluation rights are separate.

Explicitly connect and disconnect one virtual monitor.

Start and scope

One 1080p60 SDR monitor, owned by the open control handle; no capture or network transport. Windows 10 build 19045 was qualified; Windows 11 and physical GPU/suspend-resume qualification remain pending.

Integrate an explicitly paired Windows LAN host/viewer.

Start and scope

Numeric IPv4, pinned TLS over TCP, GDI capture up to 1280x720 and optional SendInput in the same interactive session. No relay, secure-desktop/UAC control, audio, clipboard or file transfer. Matching runtime has a one-hour per-product/boot demo.

Networking

7 entries

Correlate processes, addresses and WFP connection stages.

Start and scope

Connection-lifecycle metadata; the sensor does not capture packet contents.

Test an application's handling of controlled UDP IPv4 impairments.

Start and scope

Target laboratory traffic and follow the documented bounds. It is not a general TCP/bandwidth impairment tool.

Observe incoming/outgoing Ethernet frames on a selected adapter.

Start and scope

Bounded capture with possible losses; layer-2 transmission is a separate operation.

Attribute local process/port/CIDR rule decisions.

Start and scope

Continue leaves other Windows filters in control; check behaviour on new flows.

Integrate a virtual network adapter into an application.

Start and scope

Read the packet contract, lifecycle and driver requirements.

Control an unlocked Windows console desktop through a dedicated host and portable viewer.

Start and scope

Direct Sunshine/Moonlight SDR H.264 up to 1080p; Vdevice supplies host-side keyboard/mouse input with its one-hour kernel-boot demo. No relay fallback, secure-desktop control, audio, clipboard/file transfer or gamepad forwarding.

Apply scoped WFP IPv4/IPv6 application, CIDR, protocol and port rules.

Start and scope

Native C++17 SDK and signed evaluation bundle. A one-hour kernel-boot allowance applies; this component is not a complete VPN.

Storage and files

7 entries

Obtain conservative changed-block maps and checkpoints.

Start and scope

Evaluate on an explicitly selected synthetic disk and follow the checkpoint protocol.

Hydrate Windows files on demand from an application backend.

Start and scope

Read-only backend, required runtime and limited demo; check CFAPI scope.

Explore per-process file I/O completion diagnostics.

Start and scope

Preview: Microsoft altitude assignment, signing and live qualification remain pending in the documentation.

Observe statuses and completions on the laboratory's synthetic disk.

Start and scope

Initially select an unpartitioned lab disk; software measurements do not establish physical-drive latency.

Explore audit/access rules scoped to folders.

Start and scope

Engineering preview: altitude, signing and live validation pending. No installable production-protection driver is provided.

Supply a user-mode backend for a virtual disk.

Start and scope

Follow the driver's contract, lifecycle and bounded-request rules.

Test error handling on a disposable RAM disk.

Start and scope

Synthetic test fixture; distinguish an accepted injection, an I/O result and filesystem state. It does not establish power-loss durability.

Windows diagnostics

6 entries

Driver-Readiness-Inspector

ApplicationNo additional driver

Prepare device and driver-service support reports.

Start and scope

Read-only HTML/JSON exports; this utility requires no additional driver. It is not a driver updater.

Explore Windows timing and load observations.

Start and scope

Read the measurement definitions; software timestamps are not hardware latency measurements.

Observe attributed process events.

Start and scope

Check event coverage and live-collection requirements.

Audit or deny direct launches belonging to an application.

Start and scope

Scoped to the owning client and its rules; an integration component rather than a complete antivirus.

Explore write rules for an application registry branch.

Start and scope

Preview: altitude allocation, signing and live qualification pending. Scope: HKLM\SOFTWARE.

Observe USB-request metadata and bounded payload samples.

Start and scope

Explicitly select one USB device; check supported transfers and capture limits.

Local automation

3 entries

Browser-Control-SDK

Driver SDKNo additional driver

Control a local WebView2 browser through an application SDK or MCP tools.

Start and scope

Navigation, inspection, forms and screenshots; Microsoft Edge WebView2 Runtime is required. This is browser automation, not whole-desktop control.

Titan-Local-AI

ApplicationNo additional driver

Use a French desktop interface for local GGUF text models.

Start and scope

Acquire model weights separately. File/browser tools depend on the model, with confirmation by default.

Validate a prefix and export USB HID barcode scans to local CSV.

Start and scope

US-ASCII keyboard-wedge scanner plus Enter; live use requires Interceptor Keyboard & Mouse.

Catalogue checked 2026-11-18. A public repository or source preview is not a promise of production qualification. Detailed source guide.

Practical guides

Understand the first decision.

Getting started

A first run without an input driver.

Start with browser automation, read-only diagnostics or offline fixture validation. Know what a successful first step actually proves.

Follow the guide ↗

Device architecture

Interception or a virtual device?

Choose between modifying an existing device's input, creating a new device and inspecting the Windows stack.

Compare the paths ↗

Measurement

Read a latency number in context.

Separate API calls, independently observed reports and physical latency. Keep protocol boundaries and failed runs in view.

Read the evidence ↗

Evidence over promises

Inspect the results behind the claim.

The publisher-operated benchmark lab retains raw QPC timestamps, versions, independent receiver checks and invalid trials. Its initial campaign measures selected virtual-device paths in Windows 11 Hyper-V.

Open the benchmark lab ↗

Known stability finding

Vdevice controller teardown reproduced two guest WDF queue-purge crashes. The finding remains open; successful timing rows do not establish teardown stability. Read WDF-001 and its scope.

Signing, demonstrated functionality and production qualification are different evidence levels. Choose the exact edition, release and device profile described by the project.