The trust network for the software economy
Search by company name or website. No account needed.
What feeds your profile
- Company identity
- Security
- Privacy
- AI practices
- Data & hosting
- Company history
- Procurement
- Relationships
- Customer proof

Your Company Profile
Public records, company disclosures, connected systems and third-party evidence.
- Sources & dates
- Evidence status
- Change history
- One shareable link
- Fewer repeat questions
- Clearer buyer decisions
- Free company profile
Continuously witnessed, hourly, from live systems
Company identity
Show buyers what your company can prove.
- publishedpoint-in-time · published to the Trooth NetworkSeptember 11, 2026 at 4:00 AM CDTLatest
- re-witnessed63 of 65 live probes passed · 27 of 35 declarations recorded · signature validSeptember 11, 2026 at 4:00 AM CDTAppended
- re-witnessed63 of 65 live probes re-run · attestations carried forward from 2026-09-11September 11, 2026 at 4:00 AM CDTAppended
- publishedpoint-in-time · published to the Trooth NetworkSeptember 11, 2026 at 3:00 AM CDTAppended
Nothing is written over the top
Each observation is hashed and appended. A change is published as a new entry beside the old one, never as an edit to it.
Trooth's own record, read live
Trooth
trooth.co · Claimed First witnessed Sep 3, 2026
- Coverage
- 90 of 100 checks passing
- Last witnessed
- September 11, 2026 at 4:00 AM CDT
- Cadence
- Re-witnessed hourly
What is not settled stays visible
Every one of the 5 disciplines ran at the last pass. When one does not, it carries a word and a dashed mark here rather than a quiet pass.
Every category names its source
Each discipline says what was measured, where the reading came from, and when it was last read.
Reading 5 disciplines on one company.
5 disciplines, 5 carrying measured evidence
20 of 20 checks passing at the last pass
- Securitywitnessed
- AI governancewitnessed
- Businesswitnessed
This is Trooth's own company record, the same one a buyer sees.
Claim
A named officer, and proof of control over the domain. Checked once, then re-checked when either changes.
Connect
Read scopes only. Trooth never requests permission to write to a system it reports on.
Witness
Live configuration read from the source of record, not a questionnaire and not a screenshot.
Map
One witnessed fact answers a control in every framework that asks for it, instead of being re-collected per audit.
Sign
Append-only. An old reading can be replayed later and shown to be the same one.
Publish
Built from signed records. If nothing witnessed it, the page shows nothing rather than something.
Re-witness
Live probes re-run hourly. A result is compared to the last signed one, and a difference is published as a change.
The signed chain, stage by stage.
You grant Trooth permission to look. Write scopes are not requested, so Trooth can never change the systems it reports on.
Illustrative sample. The real run happens against your systems, and every line it writes is signed.
A buyer evaluating your category reaches your record the same way they reach anyone else's.
Ordering is mechanical and published: witnessed pages first, most recently witnessed at the top.
Before: the twenty-tab scramble
"Can you complete this 312-row security questionnaire by Friday?"
inbound · security review
"The SOC 2 report you sent is from last spring. Is there a current one?"
inbound · procurement
"Which subprocessors do you use today? Your website lists something different."
inbound · buyer diligence
With Trooth: one current record
Composite demonstration. The record stays current as evidence changes, not only when someone remembers to replace a PDF.
Drop it into your stack.
Five ways to read one witnessed record: a command, a pull-request check, a line of HTML, a single GET, or a connector your assistant reads. The scanner is report-only and needs no account, so you can run it before you decide anything.
Trooth Network is a listed app in the ChatGPT directory. In Claude, add it as a read-only connector. No key, no account.
# Add Trooth as a read-only connector (MCP)# ChatGPT: open Trooth Network in the app directory# Claude: Settings > Connectors > Add customconnect https://api.trooth.co/public/mcp# Report-only preflight from the terminaltrooth scan plan.json# .github/workflows/trooth.yml- name: Trooth preflight (advisory) uses: troothllc/trooth-action@v1 with: api-key: ${{ secrets.TROOTH_API_KEY }} plan-file: plan.json fail-on: none # report-only<div id="trooth-trust-badge" data-slug="your-co"></div><script src="https://trooth.co/badge.js"></script># Returns the signed, public Trust Profile (use your own slug)curl https://api.trooth.co/public/trust/your-coTrust is more than compliance.
Know who you’re trusting. A framework answers one question. A record answers the nine a buyer asks, and says how each is known.
What a buyer asks
Identity
ConfirmedA named human confirmed and domain control shown. Checked once, then re-checked when either changes.
Security
WitnessedRead from live systems and public endpoints, with the source and the moment it was read.
Privacy
Vendor declaredThe company's own account of rights, retention, and transfers, labelled as its words.
AI practices
Vendor declaredModels, training sources, and human oversight, as stated. Declared is not witnessed.
Data and hosting
WitnessedRegions and subprocessors read from the connected stack, so a change surfaces as a change.
Company history
Public-sourceIncorporation, filings, and published incidents, each pointing back at the record it came from.
Procurement
Independent third-partyTerms, insurance, and audit reports issued by someone other than the company or Trooth.
Relationships
ConfirmedA named counterparty attested under its own name. Not the company's word, and not Trooth's.
Customer proof
Customer reportedReported experience, kept distinct from measured data and open to dispute by either side.
How the record answers
Read the methodTrooth read it
Trooth witnessed Trooth read this directly from the company's connected systems and signed a receipt for what it saw.
Continuously observed Trooth re-checks this on a schedule; the stamp shows the last pass and the cadence.
A connected system supplied it
Integration supplied A connected third-party tool reported this through a read-only integration.
Someone independent issued it
Independent third-party An independent party (an auditor, an issuer, a registry) published this evidence.
Public-source Observed from public records or the company's public surfaces, with the source noted.
The company said it
Vendor declared The company stated this about itself. Declared facts are labeled, never blended with witnessed ones.
A customer said it
Customer reported Reported by a customer of the company. Reported experience is distinguished from measured data.
It is not settled
Disputed The company or another party disputes this fact. The dispute and its status are shown, not hidden.
Stale Past its expected refresh. Trooth keeps it visible and labeled rather than quietly deleting it.
Unknown Trooth has no evidence either way. Unknown is an answer, never a blank filled in.
- Search any companyA software company or a domain. No account, and no login wall in front of the record.Open the network
- Read the recordBefore you buy software, know what you are buying. Every fact carries its source and date, and the unknowns stay marked unknown.See a live read
- Compare two companiesSide by side on the same nine categories, so the difference is a row rather than an impression.Compare companies
- Check the evidence yourselfReplay a signed observation and confirm it is the same one. Trust that cannot be checked is just a louder claim.Verify evidence
Every claim shows how it is known.
Do not just tell me. Show me. The same rules for every company on the network, including this one. No plans, and nothing you can buy.
Where it came from
Every fact names its source: a live system, a public record, an independent third party, a named counterparty, or the company itself. You can always see which.
When it was read
Each fact carries the moment it was last checked. Live readings re-run hourly, and anything older than 48 hours is marked stale rather than quietly left looking current.
What happens on change
A new reading is compared with the last one. A difference is published as a change, so you can see what moved instead of only what is true today.
How history survives
Every reading is hashed and appended to a chain that is anchored daily, so an old record can be replayed later and shown to be the same one.
Why read-only matters
Trooth asks for no permission to change anything. It cannot touch the systems it reads, which is most of what makes the reading worth having.
Unknown and disputed
Unknown stays unknown, and it is never counted against a company. A disputed fact is checked again and published beside the dispute.
You cannot pay Trooth to look better. No paid placement, no pay-to-pass, no sponsored ranking. If Trooth ever charges, it will charge for tools that help you improve what’s true - never for the record of what’s true.
Make your company easier to trust.
Claim your page, connect what you choose, and let a current record answer the questions you keep answering by hand.
Claim your company page