Preparing WhiteLyin
Skip to main content
WhiteLyin
Back to public PDF tools
WhiteLyin Core

More governed tool capacity when work needs an account.

Runtime keeps account, entitlement, billing, and catalogue posture for LyinTools. Product-specific execution now belongs to the independently deployed LyinTools application.

Open Core View PDF catalogue Contact WhiteLyin
Why Core

Account-backed posture for higher-trust work.

Core remains the signed-in workspace lane for tenant identity, entitlement, audit, billing, and support posture.

  • Tenant identity and product access records remain Runtime-owned.
  • Usage, support, and billing posture remain Runtime-owned where governed.
  • LyinTools-specific execution routes, workers, and providers are not served by this deployment.
Public lane stays simple

Public catalogue remains available without an account.

The public PDF lane in Runtime is catalogue-only until an independently governed LyinTools launch URL is recorded.

  • No upload form is served by the Runtime main site.
  • No LyinTools worker or product-specific API is registered here.
  • Core is recommended when account, entitlement, billing, or support posture is needed.
Paid compute

OCR and heavier processing use account quotas.

Some document operations are CPU-heavy or can use paid providers. Core keeps those operations behind sign-in, subscription rules, page limits, and operator approval.

Governed

Cost-aware tool access

When a tool uses higher compute or external provider fallback, Core can enforce daily page limits, tenant monthly caps, and upgrade-required posture before execution begins.

Trust posture

Clear limits before production use.

Core does not change the legal meaning of uploaded documents. Visual stamps are not digital signatures, repair does not guarantee recovery, and OCR results must still be reviewed by the user.

Open Core account lane Privacy notice Acceptable use