kbpd.ai — home Talk to us

Pricing

Here's what's in the starter kit.
Then we'll talk about price.

Every license includes the production-ready scaffold, the brand canon, the design-source pipeline, the orbital cluster system, and lifetime updates through v7 launch.

Business Model

What the purchase actually changes.

The launch offer is deliberately local-first: inspect the evidence, buy the kit, run it on your machine, and expand into hosted access only after the buyer controls are real.

01 · Evaluate

Read proof before buying

Proof Studio and the working draft show claims, limits, and current evidence in public.

02 · Own

Buy the software kit once

The starter kit is a local package: site scaffold, content system, brand system, proof frame, and local MCP.

03 · Protect

Keep the license boundary clear

You own what you build. The kit itself is not for resale, redistribution, or unlicensed pass-through.

04 · Expand

Move to hosted only when it is ready

Hosted access is a later service with sign-in, buyer controls, usage visibility, cancellation, and support in place before anyone pays for it.

Open Proof Studio Read the working draft Review license boundary Compare team licensing

What the archive contains

Starter kit bill of materials

Your purchase includes the same launch scaffold, brand instance, local MCP surface, and license boundary that the public proof pages inspect.

START_HERE.md

Operator guide

First five minutes, deploy path, reskin path, support route, and local MCP setup.

included
LICENSE.md

License boundary

What the buyer may use, what they may not redistribute, and how the purchase boundary travels with the files.

included
VERSION

Release marker

Injected by the release assembler so operators can identify the archive they received.

generated at release
scaffold/

Astro scaffold

Static marketing site code: layouts, pages, motion, orbital mark, proof frame, and specimen surface.

assembled from web source
instance/

Brand instance

Design-source graph, generated design outputs, and launch-instance material used to reskin the scaffold.

assembled from instance source
mcp/

Local MCP server

Offline-first stdio server for health, search, context reads, linting, and diagnostics.

included
hosted access readiness contract

Hosted access readiness contract

Phase 2 requirements for hosted access; included for review, not as a live hosted service.

included

Local MCP

The included access layer is read-only and offline.

Server
kbpd-local
Transport
stdio
Hosted account
not required
Network
none
  • kbpd.health local:health

    Check whether the extracted starter-kit paths are readable.

  • kbpd.search context:search

    Search local scaffold, instance, and kit text files.

  • kbpd.read_context context:read

    Read a relative text file from the extracted starter kit.

  • kbpd.proof_index proof:read

    Read the bundled public Proof Studio evidence index.

  • kbpd.lint kit:lint

    Scan public outputs and kit text for private paths, ticket keys, and forbidden vocabulary.

  • kbpd.diagnostics kit:diagnose

    Summarize local MCP configuration and available tools.

Inspect local MCP proof Open MCP evidence JSON

Run path

Four commands prove the local path.

  1. 01
    Install the scaffold cd scaffold && pnpm install
  2. 02
    Run the local site pnpm dev
  3. 03
    Verify the kit root node mcp/local-server.mjs --self-test
  4. 04
    Exercise the MCP tools node mcp/smoke.mjs

Not included yet

Hosted access waits for 9 public readiness gates.

Sign-in, billing, account access, usage visibility, cancellation, customer support, service monitoring, and abuse handling ship before recurring hosted access is sold.

Claude Desktop

Claude Desktop local install path

The local Claude Desktop Extension package is source-built around the same read-only MCP server. It points Claude at the extracted starter kit; it is not hosted Claude access.

Already proven

Source package and server smoke exist.

  • .mcpb package builds from source without manual edits.
  • Bundle manifest declares six read-only tools and a required directory picker.
  • Bundled server self-test passes against a freshly assembled starter-kit archive.

Remaining gate

One human Claude Desktop smoke before stronger offer copy.

  • Human Claude Desktop install/import smoke.
  • Claude Desktop tool list shows all six local tools.
  • kbpd.health and kbpd.proof_index succeed from Claude Desktop against a fresh kit.

Not included yet

Hosted Claude remains Phase 2.

  • Hosted Claude custom connector.
  • Claude access tokens.
  • Team scopes, usage dashboard, or remote revocation.
Manifest
0.3
Entry
server/local-server.mjs
Config
kbpd_kit_root
Status
source-built; human Claude Desktop install smoke still required
Inspect local MCP runbook Review hosted boundary

Why buy the starter kit

Inspect the mechanism before you buy it.

The starter kit is not a promise hidden behind a sales call. It packages the surface grammar, proof frame, local MCP path, and corpus-backed workflow so you can inspect the model locally first.

Cold start
one blended answer
Corpus-backed
roles + prompt archive
Public claim
demonstrator
Hermes public copy patterns Archive prompt records Mnemosyne session memory
Inspect this proof Review license boundary

corpus trace

Cold start vs. corpus-backed council

Sanitized projection
The public claim is not that a name improves prose. The claim is that retained corpus and role-specific prompt archive patterns make the output easier to audit.
A council run beats one generic lens launch candidate / public summary

Purchase Path

Local first. Hosted later. Clear boundaries from day one.

The launch offer is a software kit you can inspect locally. Hosted access will be a separate offer after the customer experience and support model are ready.

Inspect local MCP proof Read the working draft See the rollout path

Buyer review path

Do not buy from a claim. Buy from the inspectable trail.

  1. 01 live Evidence room

    Start with the public fact register, evidence values, source handles, and row limitations.

    Review proof data
  2. 02 live Local MCP proof

    Check the included local server tools before treating hosted access as part of the offer.

    Inspect local run
  3. 03 published License boundary

    Confirm what you can build, what you cannot redistribute, and where team licensing starts.

    Read license
  4. 04 live Purchase support

    Use one support page for access help, payment records, returns, and future account boundaries.

    Open account path

What you get

Downloadable kit, local proof path, launch-window updates.

What stays protected

No resale, redistribution, or client pass-through outside the license.

What is not promised yet

Hosted access and service plans wait for Phase 2.

Free 30-day access

Free 30-day access

Get the starter kit free during the launch window.

Drop your email and we'll send the starter-kit access link. No card required. After 30 days, the paid tiers below take over, and you keep your kit.

Paid tiers below - what you'll see after the window closes.

Licenses

For teams under $5M annual revenue

For organizations at $5M or above

Different situation?

Tell us what you're building.

Multi-entity, consulting-practice license, or a custom deployment? Open a thread and we'll scope it specifically.

Tell us about your situation See how to start Book a demo