Product surfaces overview

Paybond is delivered across site surfaces (marketing, docs, demo, console) with different audiences and trust boundaries. Product-wise, public lead is Kit; Harbor, Ledger, and Signal are architecture behind the SDK.

If you only read one screen, use the chooser and the map below to decide where to go next.

Where should I start?

I’m evaluating the product

Start with use cases and pricing, then validate the lifecycle hands-on.

Browse use cases →

Pricing →

Proof lab →

Middleware trace →

I’m implementing

Go straight to docs and API references, then authenticate to reach your tenant console.

Docs →

API reference →

I’m operating a tenant

Use the console for day-to-day operational workflows once you’re authenticated.

Open console →

Setup →

Audit →

I’m reviewing security / trust boundaries

Start with the trust-boundary rules below, then continue into the product and API docs.

Trust boundaries →

Docs →

Surface map (at a glance)

Surface → purpose → tenancy

Surface	Example routes	Purpose	Tenancy / trust boundary
Public marketing	`/`, `/pricing`, `/use-cases/*`	Story and discovery, entry points	Public (no tenant)
Documentation	`/docs/*`	Product documentation, SDK guides, and API reference	Public (no tenant)
Interactive demo	`/demo`, `/demo/agent-trace`	Kit Proof Lab (release vs refund) and developer middleware-trace replay	Public (no tenant)
Session-establishing	`/signup/*`, `/login`	Create or resume an authenticated session	Public but security-sensitive
Operator console	`/console/*`	Operate disputes, audits, settlements, policies	Tenant-scoped (server-derived tenant context)

How they connect

Public → Demo → Docs → Signup / Login → Console (tenant-scoped)

Paybond product components

Kit first; architecture behind it

Public lead is Kit. Harbor, Ledger, and Signal are platform internals behind the SDK — distinct from the site-surface map above. Each keeps its branded name; the subtitle is the plain-English role.

Kit integrates → Harbor evaluates → Ledger records → Signal builds standing

Brand	Subtitle	When you need it	Route
Kit	Developer SDK	Integrating agent runtimes — authorize-before, verify-after, signed receipts	`/kit`
Harbor	Evidence evaluation	Deep dive: signed intents, evidence evaluation, and release or refund behind Kit	`/harbor`
Ledger	Platform provenance	Deep dive: append-only signed history for audits and compliance exports	`/ledger`
Signal	Platform standing	Deep dive: optional standing derived from verified outcomes	`/signal`

Agent runtime
    │
    ▼
Kit
Developer SDK
    │
    ▼
Harbor
Evidence evaluation
    │
    ▼
Ledger
Platform provenance
    │
    ▼
Signal
Platform standing

Trust boundaries

Tenant isolation rules (practical)

These constraints keep public surfaces useful without becoming an authority source for tenant context.

Public surfaces can render content and links, but must treat client-provided identifiers as untrusted input.
Session-establishing surfaces handle sensitive auth and billing flows; they may redirect into tenant-scoped areas only after the server establishes session state.
Tenant-scoped surfaces must never derive tenant context solely from URL params or client storage; they should rely on server-side session/auth context.

Surface details

Public marketing

Overview and use cases, plus entry points—no tenant required.

/: landing page with product story and anchor sections (e.g. Product surfaces).
/pricing: plans and signup entry points.
/use-cases/*: deeper use-case guides per problem shape (e.g. multi-agent workflows, compliance export bundles).

Interactive demo

Hands-on Kit Proof Lab and a secondary developer middleware-trace replay — no tenant required.

/demo: Kit Proof Lab — edit travel booking evidence, watch release flip to refund, inspect a Portable Receipt.
/demo/agent-trace: developer replay of paybond agent sandbox smoke JSON as an animated middleware timeline. Also linked from /guides/middleware-trace and /kit/cli.

Open proof lab →Middleware trace replay →

Documentation

Product documentation, SDK guides, and API references—no tenant required.

/docs/*: markdown-based docs for Kit, platform concepts, and API docs.

Browse docs →

Authentication entry points

Public pages that create or resume an authenticated session.

/signup/*: public signup funnel (including billing flows when enabled).
/login: public login surface.

Tenant-scoped operator console

Operational UI for a specific tenant—requires authentication and tenant context.

/console/*: the operator console. This surface is tenant-bound and should only be reachable after authentication.

How the surfaces connect

A recommended journey

A simple path from initial understanding to hands-on validation to onboarding.

Start with Public marketing to understand what Paybond solves.
Use the Interactive demo to validate the lifecycle and artifacts without provisioning a tenant.
Go to Docs for product concepts, SDK guides, and API references.
Use Signup/Login to establish an authenticated session.
Operate inside the Console once tenant context is established.

What is public vs. tenant-bound (quick checklist)

Public /, /pricing, /use-cases/*, /docs/*, /demo
Session-establishing /signup/*, /login
Tenant-scoped /console/*