WORKBENCH / PRODUCT DOCUMENTATION
Set up your desktop, choose the right processing route and check the result before acting.
Signed Windows evaluation · 2.3.2-preview.3 · installation checks 5 November 2026
Install preview.3 from the release guide. Expected publisher: vSecure Solutions LLC. Optional local AI support is a separate signed package. The existing films show the previous evaluated interface; use the current release check for installation and package identity.
Download signed Windows evaluation 2.3.2-preview.3Use the official installation guide to check the available Windows or Linux channel. The private-AI evaluation described here is newer than the last reviewed Store package; installing an older public release does not add these preview features.
The private workflow was evaluated on Windows 11 x64. It needs WebView2, an AVX2/FMA/F16C-capable x64 processor, at least 8 GiB RAM and sufficient free memory. The app checks readiness before starting; your IT team qualifies the exact release on its managed devices.
Use a supported Debian/Ubuntu amd64 package and the private runtime approved for that build. An unlocked Secret Service is needed for normal credential storage. Private processing also requires the supported isolation dependencies; Windows acceptance does not qualify a Linux deployment.
Open the official installation guide. Use Microsoft Store → Library for Store updates; use the approved updater for a direct installation. Save current work before changing channels.
Install the approved local AI component before handling private sources. Preparation may need a network connection and disk space; confidential work begins only after readiness checks pass.
Use the examples below first. Verify the result, Stop, Clear and the approved save destination before using permitted organisational data.
In the evaluated build, sign in to Workbench with your Hub account. Workbench can obtain the Operator connection from that verified identity and your current access rights; another Vigthoria password entry is not required for this supported connection.
Google, Microsoft and social accounts still need their own provider consent. The standalone CLI has a separately authorised device credential. Disconnecting Workbench clears its local connection; it does not sign every browser or device out of external providers.
A cloud plan needs a valid account, service entitlement and available capacity. Prepared private tasks can run offline while their verified plan remains valid. Initial setup, sign-in, fresh planning and online services need a connection.
Selected source → local processing → answer → your review → approved save location.
Confidential extracts, private questions, calculations and answers stay in this private workflow on the device.
Account and connection information + a general task choice → a reusable workflow plan.
The private planning request contains only the selected task type: budget, register or document. It does not send the source, filename, private question or result.
This boundary applies to the dedicated private workspace. The standard Assistant, shared project context, media providers, email, CRM and social publishing have their own online data flows. Only use those routes for information your organisation permits you to share.
Choose budget, register or document in Private workflows. If online planning is needed, it receives the general task choice, not your confidential source. Plans are verified and expire after seven days; a reused plan keeps its original date.
Wait for readiness to pass, then select a permitted local file. Enter the private question here. Do not paste confidential text into the standard Assistant or the website support chat.
Check extracted facts and calculations. The local AI has a bounded context and can make mistakes. An answer supports the reviewer; it is not an administrative decision.
Choose a destination your organisation permits. Stop cancels the current inference; Clear removes the current working view. Exported files remain where you saved them. A synced folder or backup can copy an export elsewhere.
UTF-8 TXT, Markdown, CSV and TSV; one input file up to 1 MiB, 10,000 rows and 64 columns. Private AI accepts a source extract up to 12,000 bytes and a question up to 2,000 bytes, within a 4,096-token context; answers are capped at 320 tokens. Larger sources need an approved, focused extract. Scanned PDFs and Office files need an approved local conversion first.
Processing uses bounded CPU and memory, one local inference at a time and a 120-second deadline. Insufficient memory or isolation failure prevents the private task from starting. Resource pressure can stop it; there is no automatic transfer of the private task to the cloud.
Use a trusted, managed endpoint. Device encryption, operating-system administration, screen capture, crash data, backups and folder synchronisation remain part of your organisation’s controls. Clearing the workspace does not promise forensic erasure or device-wide prevention of data sharing.
These are demonstration cases, not customer records or measured productivity claims.
A fictional total of €48,000 is compared with a €45,000 limit. The result is a €3,000 variance for a human reviewer to check.
The fictional entry DEMO-002 in source row 3 is missing its status. Workbench highlights the gap for follow-up; it does not invent a status.
Ask about a date or responsibility in a short fictional project memo. Compare the answer with the selected source and keep only reviewed results.
Plan and coordinate work in the standard connected Assistant. Review selected project context before sending it: context submitted to an online service leaves the device.
Vigthoria Tables, Vigthoria Documents and Vigthoria Presentations are productivity previews. Check the available engine, file behaviour and required format compatibility for your installed version before relying on them.
Use the documented device and project permissions for coding tools. Review the selected files, allowed operations and destination service. Private-AI isolation does not automatically cover another agent or external tool.
Prepare content, verify the connected account, preview media and approve publishing. Provider permissions and plan access apply. A local publishing worker needs the device awake, online and running; account connection alone does not prove a post succeeded.
Media generation with your own provider keys follows that provider’s processing and billing rules. Check what is sent before using source material. This is a separate connected workflow.
Private processing uses the device for its own approved task. General GPU offload, third-party compute sharing and commercial compute rewards remain unavailable.
Academy format: explanations on the left, the actual Windows interface on the right. Both films use fictional examples and show genuine results. They demonstrate an evaluation build; cuts and held views are labelled.
Start with a 30-minute discussion using fictional or public sources. A proposed four-week pilot on three to five managed Windows devices follows agreement on release, IT, data protection, supplier terms and procurement. It is a proposal, not a published government-certified product or a new fixed-price subscription.
Agree the permitted data and export destinations, administrator access, support access, retention, accessibility needs, incident responsibilities and success measures. Keep source records and raw measurements in approved client storage. Compare complete effort and quality against your best existing approved workflow.
The current evaluation does not establish centrally enforced private-only fleet policy, SAML/SCIM, security certification or permission to process classified records. If these are required, resolve and qualify them before a pilot. Keep decisions affecting people’s rights with the responsible authority.
For your first enquiry, share the task and requirements only. Do not send confidential documents, private records or credentials through the public contact form or support chat.