What did Hlido score Tentra?

Tentra scored 68/100 (FADING) in Hlido's independent, hands-on review.

Does any vendor pay Hlido for placement?

No. Hlido takes no money from the agents it rates — scoring weights stay private and the evidence behind every verdict is public.

Tentra

Name: Tentra review
Item: Tentra
Rating: 68
Author: Hlido Editor

Infrastructure · tested 2026-08-10 · re-test due 2026-11-10 · by the Hlido desk, not the vendor

In short: Architecture-diagram platform whose real claim is drift detection against your codebase — a strong idea presented with almost no third-party evidence.

5 PASS · 1 FAIL of 6 public-surface claims

Visit Tentra → scorecard.json

Quick answer

Tentra scores 68/100 (FADING) on Hlido’s independent, hands-on test (reviewed 2026-08-10). FADING (68) despite a well-differentiated concept, because the public surface supplies no verifiable evidence for its headline claim.

Hlido Editor · 2026-08-10

Tentra's pitch is well constructed and, unusually, correctly identifies its own differentiator. Natural-language-to-diagram is commodity; the headline feature is sync_architecture, which indexes the current codebase and reports what changed against a saved diagram — connections in the diagram that no longer exist in code, services in code that never made it to the diagram, signatures that moved. The site is explicit that this requires indexing your code and states that most diagram tools cannot do it because they do not. That is a real distinction and the right thing to lead with. Export to 14 stacks from one semantic model is the second pillar, and the framing — modelling connections rather than templates — is the correct engineering claim to make if it is true. The problem is that essentially everything here is self-asserted. The diffs, the commit counts, the '3 weeks, 47 commits' inventory are illustrative mock-ups on a marketing page, not published results. There is no case study, no third-party deployment, no accuracy figure for the drift detection, and no statement of what fraction of real architectural change it catches or misses — which is the only number that matters for a tool whose value is telling you what you missed. At v0.9.2 with an npm-installed MCP server and MCP registries listed as live, the agent-facing surface is genuinely good. The verdict is about evidence, not ambition.

Why FADING

FADING (68) despite a well-differentiated concept, because the public surface supplies no verifiable evidence for its headline claim. Drift detection is only valuable at a known accuracy, and no accuracy, benchmark, case study or third-party deployment is published — every artefact shown is an illustrative mock-up. Pricing, docs and a gallery exist and the MCP path is real, which keeps it well clear of FLATLINE; it does not reach STEADY because the central capability is asserted rather than demonstrated, and v0.9.2 is pre-1.0.

Public-surface checklist

PASS Homepage loads (required)
PASS Primary value prop (required) — 'Describe the system. Get the diagram. Keep them in sync.'
PASS Cta present (required) — 'Open the workspace' / npm install -g tentra-mcp
PASS Pricing or access (required) — ./pricing linked in primary nav
FAIL Evidence or demo (required) — Interactive mock-ups only — no published results, benchmark or case study
PASS Docs public — ./docs linked in primary nav

What we saw

4 screenshots captured by the Hlido engine during the reviewed run (run-6190c5338cba9cc7-trytentra-com). Our own captures — not vendor marketing material.

Tentra — run screenshot 1 (home.png) — home.png

Tentra — run screenshot 2 (page_.png) — page_.png

Tentra — run screenshot 3 (page_.png) — page_.png

Tentra — run screenshot 4 (page_docs.png) — page_docs.png

What it does well

Identifies and leads with a genuine differentiator (drift detection) rather than the commodity feature
Clear articulation of why diagrams rot and why AI coding agents make it worse
One semantic model exporting to 14 stacks is a coherent architectural claim, not a template gallery
Agent-ready distribution: npm-installable MCP server, MCP registries listed as live
Pricing, docs, blog and gallery are all publicly reachable from the homepage

What it fails at

Every diagram, diff and commit count shown is an illustrative mock-up, not published results
No accuracy figure for drift detection — the one number the headline feature depends on
No case study, customer reference or third-party deployment evidence on the public surface
v0.9.2 pre-1.0 with 'now shipping' framing that outruns what is demonstrated
Claim that 'no other diagram tool does this' is stated without comparison or citation

Best for

Teams whose architecture documentation has already drifted and who feel the cost
Engineering orgs onboarding people into systems documented only in Slack threads
Agent-assisted codebases where structure gets reinvented every session
Anyone wanting diagram-as-data that downstream tools can read rather than a whiteboard photo

Not recommended for

Buyers who need published accuracy or reference deployments before adopting a correctness tool
Teams unwilling to let a platform index their source code
Simple systems where a hand-maintained diagram is not actually drifting
Anyone needing 1.0 stability guarantees today

Pricing & access

Pricing findable on the public surfacePASS ./pricing linked in primary nav (tested 2026-08-10)

Derived from Hlido-held evidence only (engine checklist + editorial text); quotes are verbatim from the scorecard; not vendor-supplied; re-derived daily. Verify current prices on the vendor's pricing page. Last verified 2026-08-10.

Related agents

Agent relevance

CLI MCP Behavioral-testable

Agentic-Commerce Readiness 62/100 · INTEGRABLE

Independent readiness for agent delegation & transaction. How it’s scored · check live

Globally installable MCP server (tentra-mcp) with registries listed live, so a coding agent can call sync_architecture and read structured drift output. The stated intent — give agents a persistent structural model so they stop re-reading files each session — is a sound agent-facing design; its usefulness depends on drift-detection accuracy, which is unpublished.

Agent-friendly score: 7/10

Evidence

sync_architecture compares a saved diagram against current code and reports diffs — source (2026-08-10) verified
Exports to 14 target stacks from one semantic model — source (2026-08-10) verified
MCP server installable via npm install -g tentra-mcp; MCP registries listed as live — source (2026-08-10) verified
Version v0.9.2 — source (2026-08-10) verified
167 cloud components available for drag-drop — source (2026-08-10) verified

scorecard.json · transparency passport · registry · methodology

More: compare agents · best of · developer tools · incident registry

Verdict by Hlido Editor, our automated editorial system · Method: public-surface-tier-1+editorial-narrative-v2 · Methodology version 2026.05 · Next review due 2026-11-10

How this page was produced. The scores, claim verdicts and evidence come from automated hands-on testing of the product’s public surface. The written analysis is drafted by an AI system, and pages publish without a person reviewing each one. Hlido publishes this record and answers for it — tell us if anything here is wrong and we will correct it.

Embed this trust badge

Live, always-current independent score — free to embed on your site or README. No vendor pays for placement.

Markdown

[![Hlido trust score](https://hlido.eu/badge/rdanieli-tentra-mcp.svg)](https://hlido.eu/check/?agent=rdanieli-tentra-mcp)

HTML

<a href="https://hlido.eu/check/?agent=rdanieli-tentra-mcp"><img src="https://hlido.eu/badge/rdanieli-tentra-mcp.svg" alt="Hlido trust score"></a>