Tester access uses license numbers, not a public purchase flow yet.

TraceLayer is opening the public PWA carefully. Tester license numbers unlock the app preview, device activation, plugin entitlement gates, and install readiness while core public information remains visible.

The license model is built to be calm and self-hosted friendly: no frontend secrets, no public registry files, no invasive always-online lockout, and no payment provider connected on this page.

You can run TraceLayer on your own infrastructure, use the public PWA at app.tracelayer.online as tester access opens, or choose a hosted TraceLayer path when managed cloud operation is the better fit.

What a tester license unlocks.

Tester keys are manually issued while the product is still under active development. They are scoped to app-preview capabilities and can be expanded as modules become ready.

Public PWA access

Activate a license number in the public app to unlock tester-only app routes, install readiness, and workspace setup.

Device activation

The app tracks activation slots by device session so testers can refresh or deactivate the current browser without reusing the plaintext key.

Plugin gates

TraceLayer modules show whether required entitlements are active, missing, locked, or available as core functionality.

Offline grace

Previously validated access can continue during temporary authority outages until the grace window ends.

Install readiness

The browser-managed PWA install path can unlock for licensed testers while signed native packages stay blocked until real signed artifacts exist.

Public-safe payloads

Responses avoid plaintext keys, registry paths, signing secrets, raw device identifiers, and private operational controls.

Deployment choices.

TraceLayer is not meant to force one hosting model. The same product direction supports licensed tester access, self-hosted installs, and managed cloud hosting.

Self-hosted TraceLayer OS

Download and run TraceLayer with your own server, storage, websites, and infrastructure. Your deployment stays under your control.

Public PWA tester path

Sign up or receive a tester license number, activate it at app.tracelayer.online, and install the browser PWA when your device is eligible.

Hosted/cloud option

Future hosted plans can operate TraceLayer for users who want managed infrastructure while preserving clear export, license, and safety boundaries.

Tester journey.

  1. Request early access or receive a TraceLayer tester license number.
  2. Open the public app at app.tracelayer.online.
  3. Activate the license number on the Tester Access or Licensing page.
  4. Save a tester workspace on Account, then create a working copy project.
  5. Review plugin gates, install readiness, and onboarding state before testing workflows.

Loading public-safe license authority status...

Entitlement preview.

You can test whether a license number resolves public-safe entitlements here. The form does not create or manage licenses; it only asks the public entitlement endpoint what a submitted key can unlock.

  • Core TraceLayer information remains visible without a license.
  • Tester install and protected module access require the right entitlements.
  • Invalid, disabled, revoked, expired, or deactivated keys remain locked.
  • Billing lookup keys are modeled for later, but no billing provider is connected here.

Check a license number

Use the public app for real tester activation and device/session controls.

Current limits.

The tester program is intentionally narrow until the product account, billing, and package distribution systems are production-ready.

01

No self-service checkout

Tester keys are issued manually during the preview period.

02

No native package yet

Signed desktop packages stay unavailable until checksum, signature, notarization, and rollback metadata exist.

03

No core lockout

Public product information and core local concepts are not hidden behind a constant online check.

04

No secret payloads

Public pages and public APIs must not expose private registries, signing secrets, infrastructure credentials, or internal-only controls.