VericSoft™ developer portal
Build test programs. Not driver glue.
SDK docs, the Driver Development Wizard, and a driver registry that states exactly how far each driver is validated — everything you need to build VericSoft test programs.
Getting started
Documentation is being written alongside the framework.
VericSoft is in early access. Docs land here as APIs stabilize: framework concepts, your first test program, sequences and sweeps, and result capture. Request SDK access to get them as they ship.
Driver architecture
Capabilities in, commands out.
Capability binding
Programs declare what they need ("SMU, 4-quadrant, 200 V"), not which box. Any conforming driver satisfies the program.
Isolated plug-ins
Drivers are versioned plug-ins with a stable contract — discovered at runtime, swappable per station.
Simulation mode
Every driver can run simulated, so programs and drivers are developed and tested without the bench.
Driver Development Wizard
A working driver in hours, not weeks.
The wizard scaffolds a driver from instrument metadata — plug-in skeleton, command-mapping stubs, a unit-test harness, and simulation hooks — then walks you through implementation and validation. Wizard access ships with the SDK.
Driver registry
Will it drive?
The registry catalogs instrument drivers by tier — Vetted (validated on hardware by RONTRON), Verified (certified third-party), Community, and Bounty open. The searchable catalog is being seeded from drivers built in active projects now.
Need a driver we don't have?
Tell us the instrument — manufacturer, model, interface. Driver requests directly shape the bounty board and vetting queue. Request a driver →