Help Center
Step-by-step guides for every stage, including buyer sign-in, first submission, reviewer handoff, and billing.
Start with these buyer and reviewer questions
These guides are written for teams that already have artifacts, need a cleaner handoff, and want plain-language answers before starting the first paid live batch or forwarding a proof package.
Fast answers
- What does AttestLayer do?
It turns exported artifacts into PASS/FAIL output and, on PASS, a signed verification kit. - Does AttestLayer need system access?
No. The normal proof flow uses exported artifacts only. - Does FAIL cost credits?
No. Paid credits burn only when a verified PASS kit is issued. - Is this a certification?
No. It is not an audit opinion, compliance certification, or legal advice. - Who should buy first?
Usually a technical, security, compliance, operations, or buyer-facing owner starts. Procurement or finance may review the package. - What should we upload?
Exported evidence packets, approval artifacts, review-support files, and related proof material you are allowed to share. - What should we not upload?
Secrets, private keys, root credentials, API tokens, unrelated personal data, or files you are not allowed to share. - What should reviewers use?
Use the Reviewer Pack, public verifier, and bundled offline verifier.
Featured articles
Choose your starting path
Use this when you need the cleanest path between one real evaluation, the first paid live batch, and recurring coverage only when the need repeats.
What happens after I buy Activation-10?
Use this when a buyer, operator, or procurement reviewer wants to understand exactly what the first paid live batch activates next.
What does FAIL mean, exactly?
Use this when someone needs a plain-language explanation of PASS / FAIL under the active ruleset, exact blocker visibility, and why FAIL does not consume credits.
How do I forward the output internally or to a reviewer?
Use this when the issue is not evidence creation but making the handoff cleaner for procurement, security, finance, or counterparties.
Who inside a company usually owns this process?
Use this when a team needs a realistic buying map across technical owners, buyer-facing teams, procurement, security, and finance.
Does AttestLayer replace our trust center, security review, or compliance work?
Use this when someone is worried AttestLayer is being positioned as a vague compliance umbrella instead of a structured proof and handoff layer.
What files should we prepare before the first submission?
Use this when a buyer already has exported artifacts and wants to know what makes a strong first paid live batch or Pilot submission.
What can a reviewer verify independently?
Use this when a reviewer, account team, or buyer needs the short explanation of what Verify, Registry, and the proof package actually let them check.
Supporting guides
Email & access
How onboarding email, buyer sign-in, and secure access links work.
Eligibility & risk checks
How Pilot access checks work and why free evaluation is still controlled.
Upload rules
Browser and API upload paths, supported formats, and what happens after upload.
Billing & validity
Credit validity, upgrade rules, invoice paths, and refund boundaries.
Legacy after-purchase guide
Operational overview for teams already inside the first paid live batch flow.
API access
Optional technical access after the browser-first flow is already live.