01
Choose what to record
Start with a piece of work or a credential that matters to you.
For individuals
Your work deserves a record you can share.
Keep signed records of your work and credentials, then share the evidence when someone needs to check it.
For individuals
A record of the work you actually shared
A record can help you show what you submitted, which issuer signed it, and whether the content has changed. Use the personal portal to organize supported records and share verification links.
Recording a file does not independently prove legal authorship or ownership. Keep the original work and any other evidence relevant to your situation.
For individuals
Create, retain and share your evidence
02
Create or collect the proof
Use the personal portal to manage supported records and their details.
03
Share it in context
Give the recipient a verification link and explain what the record represents.
Details and limitations
Privacy, revisions and the limits of a personal record
Keep the exact work you want to share
Use personal Verify when the record belongs to your own work: a statement, document version or supported credential. Choose what the recipient actually needs to see. If you publish text through Proof Frame, review the text and public fields before signing. A private original file is not automatically stored or published just because its fingerprint is recorded.
After creating a record, retain your original file and share the proof link with context. A recipient can inspect an intentionally public proof without creating an account. For later changes to a signed statement, use a linked revision rather than implying that the original signed bytes were rewritten.
When your work becomes an integration
Move the integration setup to Console when you are building software, issuing on behalf of an organization or coordinating a team. This choice is about the task, not whether your job title is developer or whether you employ other people. Your personal records remain in Verify; signing up for Console is not an automatic transfer.
A matching fingerprint supports a content-integrity check. It does not award copyright ownership or independently validate a qualification. Recipients should review issuer assurance and current status alongside the signature. Check your personal plan's actual allowances before creating or publishing additional records.
Watch the idea · 30 seconds
Which version did you approve?
When a statement changes, keep a clear link to the earlier signed version. Explain the change instead of hiding the history.
AI presenter and illustrative scenes. This is a product explanation, not a live verification result or customer testimonial.
Choose where to create a statementRead the explanation without video
An announcement can change after people have read it. Truthlocks Proof Frame supports signed statements and linked immutable revisions. Recipients can inspect the evidence behind the version they received. Changing a demonstration copy does not rewrite the original record. A valid signature supports integrity checks; it does not independently make the claims true. Choose your organizational issuer in Console or your personal statement workflow in Verify.
Two workspaces. Choose by what you want to do.
Building an app? Start in Console.
Developers, businesses and teams share the same Console. Verify is for personal records and checking shared proofs. You do not need a large team to choose the developer path.
console.truthlocks.com
Business & Developer Console
Build with APIs and SDKs, manage workspace credentials, register issuers and AI agents, invite teammates and review usage. Start in sandbox, then complete onboarding for production.
Create a Console workspaceverify.truthlocks.com
Personal Verify portal
Manage your own documents, credentials and signed statements. Share a proof link with someone who needs to check your record. Personal plans and records stay in this portal.
Create a personal accountOnly checking a record? Open public verification. No account is needed for an intentionally public proof. Compare accounts and sign-in options.
Before you start
The details that matter.
I'm a developer working alone. Which account do I need?
Use Business & Developer Console when you are building an application, integrating an SDK, managing agent identities or configuring workspace API access. Choose it even when you are the only person building the integration. Enter accurate project and organization information; production access still requires the applicable onboarding checks.
Is there a separate developer console?
No. Developers and organizations use Console at console.truthlocks.com. Documentation explains how to build; Console is where you manage the workspace, credentials, issuers and environments used by your integration.
What is Verify for?
Verify at verify.truthlocks.com is the personal portal for your own records and statements, and the public place to check shared proofs. A personal account is not the workspace for your company's team, organizational issuers or business integrations.
Do recipients need an account to check a public proof?
No. Open an intentionally public proof link or the public verification page. Creating and managing records requires the appropriate account; inspecting public evidence does not. Private records remain subject to access controls.
I already signed up in Verify. How do I build an integration?
Keep your personal records in Verify. Create or join the appropriate Console workspace for the integration, and use its credentials with the matching API environment. Signing in to Verify does not automatically move personal records, subscriptions or permissions into Console. Contact support if you need help choosing or locating a workspace.
Does choosing Console enable production or paid usage immediately?
New business workspaces begin in sandbox. Complete the required onboarding and approval steps before production access. Billing country verification, account permissions, plan limits and provider setup still apply. A sandbox example is not evidence of production readiness.