Skip to content
Vehistra

Roadmap

Vehistra follows the requirements of a running operation. This overview shows the state – we deliberately name no dates.

Current state:Stable release

Completed12

  • Vehicle and driver core

    Done

    Vehicles, drivers, categories, statuses with defined business meaning and mileage.

  • Assignments with history

    Done

    Drivers, plates and keys as periods instead of overwritten fields.

  • Deadlines and maintenance

    Done

    Inspections with result and warning levels, service intervals by date and mileage.

  • Damages, accidents, workshop

    Done

    Damage reports, accident records with involved parties and witnesses, workshop orders with seven statuses.

  • Plates and insurance

    Done

    Inventory, free plates, reservations with expiry warning and insurance contracts per vehicle.

  • Reports and export

    Done

    Vehicle record, accident and workshop report as PDF, lists as XLSX or CSV.

  • Roles, permissions, audit log

    Done

    Seven prepared roles, permission checks in the services, a non-modifiable log.

  • Server and operations tools

    Done

    Twelve-step server setup, server diagnostics, updater and a verified backup before every migration.

  • Solo installation

    Done

    Operating mode selectable in the installer, a local database without network shares, and its own guide.

  • Public documentation

    Done

    The six guides as a website, searchable and in two languages.

  • MIT license

    Done

    Since version 1.0.0 Vehistra is published under the MIT license; the license file is installed with it.

  • Solo mode without a database server

    Done

    The database is a single file there; setup takes about ten minutes and requires nothing to be installed afterwards.

In progress1

  • Proving it in daily use

    In progress

    Up to 1.2.0 every version was published as a beta on purpose. Since 1.3.0 it is not – the record in day-to-day use keeps growing.

Planned1

  • Signed distribution

    Planned

    The release process signs the packages as soon as a signing account is configured – described in SIGNING-POLICY.md. Until then Windows shows SmartScreen on first start.

We name no dates for planned items until they are reliable.