Custom software project · Active development
Workbench Vault
A local, offline-first workspace for documenting real work on projects and physical objects with structured cards, relationships, files, history and user-owned data.
Workbench Vault is an active development project, not a finished V1 application. Its domain, storage, search, backup and application foundations are real and tested; the complete end-user workflow and production interface are still being built.
Current product evidence
A development shell over a real local vault
The gallery shows verified captures of the current Unity development shell and implemented workflows. Workbench Vault currently uses one dark interface palette, so the same authentic captures remain visible in both Viken Data themes.
Inspectable gallery
Workbench Vault development shell
Open two genuine screens from the current Windows development build. Workbench Vault currently uses one dark interface palette, so the captures stay unchanged when the Viken Data theme switches.
Implemented foundation
Readable local data is the foundation of every workflow.
The project starts from a portable folder—the vault—as the source of truth. Cards, templates and workspace metadata remain readable files rather than records trapped behind a product account.
Generic cards and templates
The Core models typed fields, content blocks, relationships, timeline events, versioned templates and separate draft and complete validation modes.
Strict JSON vault storage
Canonical documents use strict UTF-8, bounded reads, schema checks and atomic replacement for individual files, with malformed entries reported rather than silently discarded.
Create, open and save workflows
Application-level use cases can create and open a workspace, rebuild its index, surface recovery issues and save cards through the same tested boundaries.
Search and Smart Lists
A rebuildable local index searches card fields, blocks, attachment names and related-card text. Smart Lists store filters and sorting rather than duplicate card data.
Backup, validation and restore
Local backup archives carry file sizes and hashes, reject unsafe paths and restore through staging into a new or empty destination after validation.
Blank and Workshop starting points
The foundation supports a generic Blank Workspace and an optional Workshop Pack for clients, vehicles or machines, service visits, parts and work reports.
Intended workflow
Capture the work, find its history and keep the files.
The first reference workflow is for an independent mechanic, technician or small service operation, while the underlying card model remains usable beyond one trade.
Scope and limitations
The foundations work; the product workflow is not finished.
The current Unity scene is a functional development shell for creating and opening workspaces and showing recovery issues. It is not yet the production Workspace Selector or the finished card workspace.
Major V1 interface work remains
The Template Builder, Card UI, Visual Workbench, complete attachment workflow, PDF reports and production builds are not yet finished.
Single-writer foundation
The current storage model does not yet provide a vault-wide lock, compare-and-swap or a transaction journal for multi-file operations and backups during concurrent writes.
Not business administration software
Accounting, fiscal invoicing, payments, inventory ERP, cloud sync, multi-user hosting, AI and OCR are outside V1.
Development status
A testable core with explicit release gates.
Core, Storage, Search, Application and Workshop Pack modules are exercised independently of the Unity interface. The development shell can create Blank or Workshop workspaces and open existing vaults while preserving readable data and surfacing recovery issues.
Before production use, the project still needs schema migration completion, an accepted scale profile, bounded full integrity scans, stronger multi-file and concurrent-write guarantees, hardened file preview and reporting, production player builds and release packaging.
If your team needs a different way to record and retrieve its work, explore our custom software development service. We can review the records, relationships and recovery needs of your workflow separately from the unfinished Workbench Vault release.
Project enquiry
Contact us about a custom local workspace.
Describe the records, relationships, files and recovery requirements to support@vikendata.com. We can assess whether a focused custom workspace is appropriate and clarify which Workbench Vault capabilities are still in development.