TruthSpine: Local Project Context, Pricing, Risks, and Evaluation

Kingy verdict: TruthSpine has a clear, specific proposition: maintain a compact local record of project decisions, sources and next work, then expose that record to several coding assistants instead of rebuilding context in every chat. The V1 evidence is entirely first party and the application source is private, so the right response is a small-project trial with source tracing, privacy inspection and direct measurement—not acceptance of the vendor’s token-reduction table as an independent benchmark.

What TruthSpine does

TruthSpine is a desktop application from TimeProof Labs. A user connects a folder, repository, GitHub repository or project documents. The application indexes material it considers truth-bearing and maintains project context that includes sources, decisions, history and next work. Supported coding and chat workspaces can request that context through connectors, reducing the need to paste a project explanation into each new conversation.

The official materials emphasize local-first operation. The public README says the desktop application runs on the user’s computer and keeps project content local by default. The vendor also describes SHA-256 parent-child lineage for tracking changes in project truth. Those statements are useful design claims, but a buyer should still inspect network activity, update behavior, connector permissions, crash reporting and any feature that can send context to the selected AI provider.

Supported workspaces and private source

The current site lists a wide set of compatible surfaces, including VS Code, JetBrains IDEs, Claude tools, Cursor, Codex, GitHub Copilot, local model interfaces and several agent clients. Official VS Code Marketplace and JetBrains plugin pages provide identifiable connector distribution points. Compatibility can change by connector and version, so test only the exact editor, agent and operating system planned for use.

The GitHub repository is a public product hub for downloads, release notes, support and discussion. Its README explicitly says the private desktop application source is not published. TruthSpine should therefore not be described as open source merely because a public repository exists. Security review must rely on the distributed package, published security and privacy material, checksums, observed behavior and any additional evidence TimeProof Labs provides.

Vendor-reported context reductions

TimeProof Labs publishes several context-reduction figures. Its current page reports five project examples ranging from 87.96% to 99.95% reduction between indexed source tokens and a compact “Whole Project Context.” A separate example says 1,089,135 source tokens were reduced to 5,861 context tokens, or 99.46%. These are company claims, not Kingy measurements or proof that an agent retained every relevant detail.

The site itself notes that compact context does not mean permanent memory of every source detail. That caveat is essential. Token compression can omit a constraint, prefer a stale decision or hide uncertainty. An evaluation should ask questions whose answers changed over time, require citations back to current sources and test whether the system surfaces conflicts instead of silently choosing one.

Pricing and commercial boundary

The official site offers a 14-day trial. A one-time $95 purchase unlocks TruthSpine V1 and its 1.x maintenance updates on one active computer; future major versions are separate purchases. Those are vendor-published terms reviewed on July 29, 2026 and can change. Confirm taxes, refund terms, activation, device transfer, offline behavior, support and update policy before purchase.

There is no public developer API in the reviewed product material, and the private desktop application is not an open-source release. Connector installation does not remove the cost of the AI workspace receiving the context. Teams should include model subscriptions, usage, connector administration and human verification when comparing total cost.

How Kingy would evaluate it

1. Use a non-sensitive project with documented architecture, conventions, decisions, rejected alternatives and a known change history.
2. Ask the same source-grounded questions in two supported workspaces before and after TruthSpine connection. Record correctness, citations, omissions and token use.
3. Change one important decision, delete one source and add a conflicting document. Measure update time and whether the conflict is exposed.
4. Inspect local files, processes and outbound connections; test connector revocation, uninstall, project deletion and device transfer.
5. Compare the full source set with the compact context and identify which facts were lost, summarized or prioritized.

Kingy reviewed the live product page, public product hub, README, release notes, connector listings, dated public-hub commit and dated company announcement. We did not install TruthSpine or reproduce its measurements. Performance numbers in this profile remain explicitly attributed to TimeProof Labs.

Primary sources

• TruthSpine official product and pricing page
• TimeProof Labs public product hub
• Official README and source-code boundary
• Official V1 release notes
• Official VS Code Marketplace listing
• Official JetBrains connector listing
• Dated public-hub launch commit
• TimeProof Labs dated launch announcement