Trustlith
Developer Portal
ACTIVE DEVELOPMENT • PRE-PRODUCTIONBUILT ON CLOUDFLARE WORKERS & D1

Cryptographic authentication and transaction authorization built for high-trust digital actions.

The trust layer for every transaction. Trustlith binds user approval of sensitive actions—sign-ins, payouts, account changes, and administrative workflows—to device-bound asymmetric keys, deterministic canonical payloads, and authoritative server verification on Cloudflare Workers and D1.

Cryptographic modelDevice-bound ES256 (P-256)Keys stay on-device; never copied across devices
Authoritative runtimeCloudflare Workers + D1Atomic compare-and-set challenge resolution
Portal identityCloudflare Workers + D1Better Auth passkey-first identity, Turnstile, Email Service
Current stagePhase 3 in progressPublic portal preview; runtime provisioning bridge next

THE PROBLEM

Why ordinary OTP codes and generic MFA prompts fail high-risk transactions

Authentication is not just logging in. Modern SaaS and financial applications need verifiable proof that the right person, on an enrolled device, approved a specific action—not a relayed six-digit code.

PHISHABLE APPROVALS

Codes are decoupled from transaction intent

SMS, email, and static OTP codes can be relayed through phishing proxies without proving which amount, recipient, or action the user actually confirmed.

STATE AMBIGUITY

Interrupted mobile flows create security gaps

Key rotation, additional-device enrollment, and account recovery fail dangerously when mobile clients delete keys prematurely or skip authoritative server reconciliation after an uncertain network outcome.

TRUST BOUNDARY DRIFT

Control planes leak verification authority

Many developer portals blur browser sessions with runtime verification secrets. Trustlith keeps developer onboarding strictly separated from the authoritative Cloudflare Worker and D1 security ledger.

ARCHITECTURE

Explicit trust boundaries across client, edge, and ledger

Every Trustlith ceremony reconstructs deterministic canonical proof bytes server-side, verifies device signatures against scoped credentials, and records append-oriented audit chains.

  1. Customer App + SDK

    Creates a short-lived, single-use scoped challenge over server-authenticated API calls—never trusting browser approval flags.

  2. Cloudflare Edge + Trustlith API Worker

    Validates tenant/application/user scope, persists the challenge in Cloudflare D1, and reconstructs canonical signing bytes deterministically.

  3. Trustlith Authenticator (Flutter)

    Displays exact action context, requires explicit local user presence or biometric confirmation, and signs with the device-bound P-256 key.

  4. Authoritative D1 Resolution & Audit Chain

    Verifies the signature, commits an atomic compare-and-set terminal decision, and appends tamper-evident audit facts before returning the result.

RUNTIME AUTHORITY

Cloudflare Workers & D1 Security Plane

  • Authoritative tenant, application, device, credential, challenge, rotation, and recovery state in D1.
  • Fail-closed verification with explicit device/credential lifecycle states (ACTIVE, SUSPENDED, LOST, REVOKED, REPLACED).
  • Append-oriented, hash-chained audit ledger with fail-closed integrity key checks.
CONTROL PLANE

Cloudflare-Native Developer Portal Identity

  • This Next.js portal runs on Cloudflare Workers (trustlith-portal) with a dedicated Portal Identity D1 database—completely separate from Trustlith runtime D1 tables.
  • Customer authentication uses Better Auth with passkeys (WebAuthn), Cloudflare Turnstile, Cloudflare Email Service, and two-factor recovery codes under same-origin /api/auth/*.
  • Future runtime tenant/application provisioning bridges strictly server-side through signed admission contracts (Phase 3.0C).

DEVELOPMENT STATUS

Transparent engineering progress and roadmap

Trustlith is built in audited, security-first phases. Below is our verified current engineering state and what comes next.

IMPLEMENTED IN DEVELOPMENT

Verified engineering milestones

  • Phase 1 — End-to-End Local Flow: Working device enrollment, cryptographic login, and transaction authorization across Flutter Authenticator, Cloudflare Worker API, local D1, and a reference SaaS app.
  • Phase 2 — Lifecycle, Recovery & Audit: Device suspend/resume/lost/revoke controls, two-key rotation with restart-safe reconciliation, recovery ceremonies with recent-recovery restrictions, append-oriented audit chains, and development Apple Secure Enclave validation on macOS and physical iOS hardware.
  • Phase 3 (Portal Identity & P3.0C Contracts): Cloudflare-native passkey Developer Portal identity on dedicated D1, server-enforced multi-tenant organization isolation, and reviewed signed provisioning contracts.
IN PROGRESS & UPCOMING

Active roadmap

  • Phase 3.0C–3.4 — Provisioning & Pilot SaaS: Server-side portal-to-Worker provisioning bridge, application and API credential management, live test authentication, and first external SaaS integration.
  • Hardware Attestation & Push Wake-Up: Apple App Attest, Google Play Integrity, and wake-up-only push delivery for production mobile clients.
  • Production Edge & Operations Hardening: Cloudflare WAF/rate-limit tuning, key-rotation runbooks, observability pipelines, and independent production readiness reviews.

DEVELOPER PORTAL

Explore the Trustlith Developer Portal

Sign in with an existing developer passkey to access the authenticated multi-tenant organization workspace. Public registration opens once controlled verification is enabled.