Skip to main content

Live trial and production checklist

After onboarding, a tenant administrator completes the Live-readiness controls and submits an activation request in Client Admin Portal. No payment card is required for the complimentary allowance, but an independent Assayra assurance approver must confirm the workspace, Country Assurance Pack, regional route and enabled production capabilities before Live can be selected. Approved workspaces receive up to 10 complimentary checks using real capture, evidence handling and Assayra-owned engines.

That controlled activation validates the end-to-end path. Ongoing production volume, broad country coverage and automated approval remain governed release decisions.

The tenant Launch Centre and GET /v1/onboarding are the canonical readiness view. The response evaluates current configuration rather than a manually ticked list: every check includes its owner, required/recommended classification, test action, evidence detail and blockers. The Web SDK exposes the same response to administrator tooling:

const readiness = await proofline.onboarding.readiness();
if (!readiness.goLive.summary.readyToRequest) {
  console.table(readiness.goLive.checks.filter(check => check.status !== "complete"));
}

GET /v1/capabilities remains public; GET /v1/onboarding requires a tenant administrator session and never exposes applicant evidence.

Before the complimentary Live trial​

  • Complete workspace setup and verify the administrator email.
  • Enrol administrator MFA and publish the intended workflow.
  • Confirm the enabled capabilities and deployable Country Assurance Pack.
  • Submit the Live activation request and wait for independent approval.
  • Select Live from the environment control after approval.
  • Issue a separate pl_live_… API key and store its one-time secret.
  • Use consented real subjects only; do not reuse Sandbox fixtures.
  • Treat every outcome as trial evidence until your intended scope is approved.

After the tenth Live application, choose a package in Plan & billing. Sandbox and its credentials continue to work while checkout is incomplete.

Integration readiness for ongoing production​

  • Production tenant and region/residency approved.
  • Explicit workflow IDs stored per use case and environment.
  • Signed configuration package diff reviewed and promoted by two distinct live approvers.
  • Narrow production API keys stored in a secret manager.
  • Application creation and network retries use stable idempotency keys.
  • Applicant invitation URLs never reach logs or analytics.
  • Webhook raw-body verification, timestamp window and deduplication pass.
  • Your backend reconciles authenticated final state.
  • Review, reject, expiry and unavailable paths are handled—not only approval.

Experience readiness​

  • Custom domain ownership and TLS are verified.
  • Branding/locale release is published and rollback tested.
  • Camera/NFC permissions and denial recovery are tested.
  • Supported mobile devices and browsers complete every workflow variant.
  • Accessibility and keyboard/text-resize checks pass.
  • Email delivery, SPF/DKIM/DMARC, bounces, link scanning and expiry are tested.

Assurance readiness​

  • /v1/capabilities reports every required module as liveEligible: true.
  • Supported scope includes the exact countries, regions, document types, devices and attack classes in the launch.
  • Country Assurance Pack approved for application type and region.
  • Required document/model/data routes are promoted and current.
  • Missing/unavailable signals fail closed.
  • Thresholds and human fallback are evaluated on an approved corpus.
  • AML candidates cannot reach automated approval.
  • Maker-checker behavior matches tenant policy.

Operational readiness​

  • PostgreSQL RLS, object storage/KMS, malware scanning and protected metrics active.
  • Backup, restore, PITR and Flowable recovery rehearsed.
  • SLO alerts reach a named on-call destination.
  • Key, webhook secret and certificate rotation rehearsed.
  • Configuration rollback rehearsed through the governed approval ledger.
  • Every enabled usage meter produces one event under idempotent retry and no applicant evidence appears in meter metadata.
  • A closed billing period is finalized and reconciles against provider invoice lines; deliberate mismatches enter needs_review.
  • Evidence KEK provider is AWS KMS or the approved remote HSM/key broker; local KEKs and legacy PLENC1 reads are disabled.
  • Load/soak, failure, rollback and incident drills completed in the target topology.
A Live trial is not broad country approval.

Complimentary checks prove the real capture and engine path. Automated production decisions begin only after the required country, model, template, data and evaluation controls are approved.