Basic browser measurement should remain useful without an account. Paid plans add history, cross-platform analysis and workflow-level diagnostics.
Browser-based measurement, local processing and per-conversation usage metrics.
Historical trends, task profiles, model usage, exports and optional private sync.
Analyse loops, retries, routing decisions, failed attempts and workflow efficiency.
Plans differ by measurement depth, retained history and workflow analysis—not by access to the core local meter.
Local measurement is the entry point. Paid value begins when Veritiana stores history, aggregates behavior and explains patterns over time.
Understand basic browser usage immediately and keep the measurement local.
Build a persistent profile of how, where and why you use AI over time.
Diagnose repeated loops, oversized context and inefficient model or agent execution.
A pricing page should describe the commercial architecture now, without promising features that are not yet shipping.
The extension measures visible turns locally and provides immediate local feedback.
Authentication, anonymous profile claim, sync, aggregation, exports and account controls must be production-ready before charging.
This tier should be priced only after real usage proves which diagnostics save users meaningful time or money.
The browser extension creates trust and proves usefulness. The paid product begins where persistent history, comparison and diagnostics reduce uncertainty or waste.
Free local measurement demonstrates the product without forcing account creation.
Persistent history and aggregation form the primary recurring subscription value.
Workflow diagnostics become a higher-value product after measurement data exists.
The current product architecture treats core local measurement as the free entry layer. Final launch packaging can still change before publication.
No. The plan scope is defined, but the price should be locked only after the dashboard, retention period, exports and account controls are technically stable.
It explains the product trajectory, but it is clearly marked as a later phase and is not presented as purchasable.
Team pricing should be designed only after the individual data model, permissions, privacy boundary and dashboard value are validated.