apps/

Package account mounts the signed-in caller's OWN account self-service surface natively in the unified cloud binary — the Go port of the console's two NON-proxy Next server routes (app/keys + app/onboard) plus the money/store data bridges the statically-exported console needs (task #41, "True 1-binary FE").

Package admin mounts the god-mode admin surface (/v1/admin/*) the Hanzo Admin Console (admin.hanzo.ai, apps/operator) calls, per the api.ts contract.

Package admission is the launch-control GATE for Hanzo's hosted services — the COMPLETE waitlist feature, COMPOSING the ONE flag engine (clients/flags) one-way.

Package ads mounts the Hanzo Cloud /v1/ads/* surface: a native-Go, per-org ad-campaign store on Base/SQLite.

Package affiliates mounts the Hanzo Cloud /v1/affiliates/* partner-commission surface: a native-Go, per-org affiliate program on Base/SQLite that pays partners an ONGOING COMMISSION on the metered spend of the customers they refer.

Package agent mounts the hanzoai/agent orchestrator into cloud: POST /v1/agent (+ /v1/agent/presets, /v1/agent/conversations).

Package agents mounts the Hanzo Cloud /v1/agents surface: per-org autonomous agent definitions and their runs.

Package agentskills serves the Agent Skills Discovery surface (/.well-known/agent-skills/) from a catalogue embedded into the ONE cloud binary.

Package ai wires the hanzoai/ai module into a cloud binary: it installs the money, ingest and telemetry callbacks cloud BUILDS but cannot INSTALL, then mounts ai.

Package analytics mounts the Hanzo Cloud /v1/analytics/* surface: a native-Go, per-org analytics read API over the `hanzo` datastore warehouse (the `datastore` cluster).

Package answer is the native answer engine: the bounded plan → search → read → rank → synthesize → cite → follow-up loop behind POST /v1/ask when a `mode` (search|news|research|deep) selects web grounding.

Package ask is the UNIFIED GROUNDED ADVISOR: POST /v1/ask.

Package auditlog mounts the ORG-SCOPED audit trail surface (GET /v1/audit): an org admin's read of THEIR OWN organization's security-relevant events off the same tamper-evident, hash-chained store the AuditTrail middleware writes and the admin god-view (/v1/admin/audit) reads.

Package authors mounts the Hanzo Cloud /v1/authors/* OSS-author surface: a native-Go, per-org program on Base/SQLite that pays open-source AUTHORS a royalty on the metered platform spend of the orgs who DEPLOY their projects on Hanzo.

Package automations mounts the Hanzo Cloud /v1/automations/* surface: the Connectors+Automations engine (HIP-0106, task #51).

Package base embeds the Hanzo Base app engine in-process in the unified cloud binary (the HIP-0106 base fold) — the in-binary replacement for the standalone `ghcr.io/hanzoai/superbase` pod, whose whole job was `base.New()` + serve.

Package benchmark mounts the Hanzo Cloud /v1/benchmark/* surface: the native benchmark ARENA — run the top-N canonical public benchmarks against any model or endpoint, under ONE standardized harness, measure Hanzo's own models (enso, zen), and reconcile any external provider-reported claim against that measurement.

Package billing mounts the CUSTOMER-facing, org-scoped billing surface (/v1/billing/{usage,balance,gpu-eligibility,gpu-charge,payment-methods}) on the unified cloud binary.

Package blueprint mounts the Hanzo Cloud /v1/blueprint/* surface: the compute-cost basis for the OSS-template economy.

Package books is the revenue BOOKS spine: a native double-entry ledger that records hanzo.ai's real prepaid-credit revenue on per-org Base/SQLite, exposed at /v1/books.

The node registry: which bot nodes are connected, and how to reach one.

Package bots is the CONTROL PLANE for a bot run: a task the bot runtime executes on a surface — a desktop or terminal sandbox it drives — with a LIVE session (the URL the hanzo.app /vnc panel embeds to watch/attach).

Package campaign mounts the Hanzo Cloud /v1/campaign/* surface: the top-level go-to-market orchestration plane.

Package captable folds hanzoai/captable into the unified hanzoai/cloud binary as an in-process subsystem (HIP-0106) — the PILOT of epic #96 (fold the Captable,Inc app into cloud, drop Next.js/Prisma/Postgres).

Package catalog is the CROSS-ORG discovery lens: one place to find every project, app and site the fleet has built, whichever org built it.

Package catalogsync is the REVERSE half of the storefront loop: it consumes the commerce COMMERCE stream and turns each `commerce.product.created` into ONE content.EnsureCatalogAsset call, so a newly-created catalog product gets its ecom asset rendered (design == slug) — the mirror of the forward edge (clients/content storefront.go) that publishes a rendered asset back onto the product image.

Package channels is the /v1/channels transport plane: the portable chat envelope, per-org access policy (pairing / allowlist / open), a durable inbox, and outbound send across the connected chat transports (Discord, Slack, Teams, Telegram).

Package cloudflare is the per-org Cloudflare asset plane for the unified Hanzo Cloud binary — the first-class /v1/cloudflare/* surface (sibling of /v1/dns and /v1/domain) that manages an org's Cloudflare Zones/Analytics, Pages, Workers, Workers AI, R2, KV, and D1 through the SAME per-org, KMS-sealed API token the org connected via clients/integrations.

Package cms declares the Hanzo CMS content model as DocType fixtures on the framework engine (clients/framework).

Package code mounts the Hanzo Cloud /v1/code/* surface: a native, per-org code-intelligence engine for AI coding agents and the hanzo.app UI.

Package coding is the keystone that turns @hanzo from a chatbot into an engineer: it orchestrates ONE autonomous coding run — register a live agent session, dispatch the job to the bot-gateway sandbox runtime, mirror the sandbox's progress into the session live, verify the pushed branch landed in native git, and open a native "PR" work item — then returns a Result the trigger surface (Slack today, console/API tomorrow) renders.

activeplan.go answers the subscription paywall's ONE question: does org X hold a LIVE PAID plan? It is the commerce "active-subscription check" — the tier sibling of CheckEntitlement (per-product license).

Package company mounts /v1/company — Hanzo Company, the Stripe-Atlas-class incorporation + fundraising product.

Package compliance mounts the ORG-SCOPED compliance operations surface (/v1/compliance): the company's own KYC/KYB onboarding verification, accreditation STATE TRACKING, and a compliance-scoped read of the tamper-evident audit trail (the SOC 2 posture surface).

Package connectorruntime executes an automation connector's action NATIVELY in-process — no Node.

Package content is the Hanzo agentic-marketing lane: the marketing content loop (generate → CMS → review → approve → publish → distribute) built natively on the framework DocType engine, the ONE Go-native replacement for the bespoke karma Python scripts, multi-tenant for ANY brand (org = tenant, project = brand/site sub-scope).

Package crawl is Hanzo Crawl: fetch one URL and return its readable content as markdown, in-process, in Go.

Package crm mounts the Hanzo Cloud /v1/crm/* surface: a native-Go, per-org CRM (companies, contacts, opportunities) on Base/SQLite.

Package cron is the platform's ONE cron system: durable schedules on the embedded hanzoai/tasks engine (cloud.EmbeddedTasks) replacing every k8s CronJob.

Package dataroom folds hanzoai/dataroom (a Papermark fork: Next.js + Prisma + Postgres, "open-source DocSend/dataroom") FULLY into the unified hanzoai/cloud binary as an in-process subsystem (HIP-0106, task #101 / epic #96).

Package datastore holds cloud's one connection to the analytics warehouse — the shared columnar store behind the usage, observability and billing ledgers.

actions.go — the two GitOps write actions.

Package destinations is the native fan-out plane: it TRANSLATES the canonical /v1/event stream (clients/analytics) into each connected ad/analytics platform's own conversion schema and forwards it server-side — Google Analytics 4 (Measurement Protocol) + Meta (Conversions API) end-to-end, with X/LinkedIn/ TikTok/Reddit against the same interface.

Package dns forwards the console's DNS dashboard traffic (/v1/dns/*) to the Hanzo DNS control plane (dns/plugin/hanzodns), which owns the authoritative zone/record store.

Package do mounts the Hanzo Cloud DigitalOcean-native infra surface — /v1/vpcs and /v1/load-balancers — on the unified cloud binary (HIP-0106).

Package domain is Hanzo Domains — the DOMAIN-REGISTRATION product: search a name, see its price (with Hanzo's markup), buy it billed through the customer's prepaid wallet, and have it born pointing at Hanzo's own authoritative nameservers.

Package entitlements is the per-org product-enablement plane for the unified Hanzo Cloud binary: the /v1/orgs/:org/entitlements surface the console's paid- product sidebar reads to decide which products to SHOW, and org owners / super admins write to TURN a product on or off.

Package erp declares the ERPNext-core business model as DocType fixtures on the framework engine (clients/framework).

Package esign folds hanzoai/esign (the Documenso fork — "open-source DocuSign") into the unified hanzoai/cloud binary as an in-process subsystem (HIP-0106, task #100, epic #96).

Package eval mounts the Hanzo Cloud /v1/evals/* surface: a NATIVE, org-scoped evaluation system that replaces the retired 3.x observability-console fork (the crash-looping console proxy this file used to be).

Package exec exposes the Code Interpreter ("Run Code") surface on the unified cloud-api /v1 plane, per HIP-0106.

Package experiments is cloud's unified EXPERIMENT primitive: A/B testing as ONE value whatever the variant KIND is — a feature flag, an ad creative, an email subject, a model id.

Package finance is the ZAP-native money subsystem: a per-CUSTOMER, double-entry PREPAID WALLET on the native ledger core.

Package flags is cloud's NATIVE feature-flag engine: definitions live in per-(org, project) SQLite (cloud.OrgDB — {DataDir}/orgs/{org}/projects/{project}/ flags.db, encrypted at rest via cek) and evaluation runs in-process through the embedded hanzo-flags evaluator (github.com/hanzoai/flags/go) with PostHog-compatible semantics: rollout hash, full property-operator set, variants, payloads.

Package fleet is the ONE per-org registry of attached compute (BYO k8s clusters / BYO GPU / bare metal).

Package framework mounts the Hanzo DocType engine into the cloud binary.

Package functions mounts the Hanzo Cloud /v1/functions surface: a per-org serverless function registry.

Package gateway is the /v1/gateway subsystem: the RUNTIME config plane for the cloud edge ("gateway role").

browse.go — Hanzo Git's JSON read/browse surface: the machine-readable twin of the server-rendered UI (ui.go).

Package gojahost runs a Hanzo Node service's goja bundle (a self-contained, ESM-free JS file exposing globalThis.handle(req)) inside the unified cloud binary, per HIP-0106.

client.go is the ONE HTTP path from this subsystem to the Lux chain-data plane.

Package guide mounts the Hanzo Cloud /v1/guide/* surface: the Business AI Guide, an interactive launch checklist every org completes on-site.

Package help is the Hanzo Support product: the Frappe-Helpdesk model rebuilt as DocType fixtures on the native framework engine (clients/framework), plus a thin /v1/help subsystem (subsystem.go) for the one plane the generic, secure-by-default framework surface deliberately cannot serve — the PUBLIC help center.

Package iam folds Hanzo IAM into the unified hanzoai/cloud binary as an in-process subsystem (HIP-0106) — the LAST binary-consolidation piece: "one Go binary (hanzoai/cloud) embeds IAM + KMS + o11y".

Package idv is the ONE identity/business verification seam the Hanzo cloud binary uses to orchestrate a KYC (individual) or KYB (business) check through an external provider.

Package index mounts the Hanzo Cloud /v1/index/* surface: a native-Go, multi-tenant full-text index on Base/SQLite that speaks the Meilisearch REST dialect.

Package ingress is cloud's embedded, runtime-configurable edge — the /v1/ingress subsystem.

connectors.go is the per-USER connector plane — /v1/connectors, the sibling of the org-scoped /v1/integrations surface.

Package k8s holds the Kubernetes coordinates the cloud binary addresses — the GroupVersionResources that identify our own CRs and the upstream objects we read.

Package kafka embeds the Hanzo Stream Kafka-wire adaptor (github.com/hanzoai/ stream) as an in-process cloud subsystem (HIP-0106), translating the Kafka protocol to/from the embedded JetStream (clients/pubsub).

Package kms embeds luxfi/kms in-process inside the unified Hanzo Cloud binary per HIP-0106 ("all Go embeds in cloud"), replacing the legacy Infisical fork.

connectors.go is the per-org app-connector control plane: OAuth into Slack / GitHub / Google, store the token in KMS (never plaintext, never logged), and sync external documents INTO the same per-org knowledge store + vector index as manual pages.

GET /v1/usage/activity — the per-day contribution series (GitHub-style heatmap + timeline) for ONE authorized subject.

Package legal mounts the ORG-SCOPED legal-document surface (/v1/legal): a versioned, org-overridable library of standardized templates, a PURE merge-field generation engine that renders those templates from the org's own company/cap-table data, a KMS-sealed store for the generated documents, and the e-signature + filing seams that carry a document to execution — all on the shared audit plane.

Package link is the unified AI login manager's registry: the org+user-scoped record of WHICH provider accounts (Claude Max, ChatGPT Plus, a Hanzo API key, a raw provider key) a developer has signed into, ON WHICH MACHINES, with each account's latest usage snapshot.

Package marketing mounts the Hanzo Cloud /v1/marketing/* surface: the native-Go GTM engine folded from github.com/hanzoai/marketing onto the ONE cloud framework (zip/Fiber + cloud.Deps + per-org SQLite), the twin of clients/crm — NOT a proxy to a standalone pod, and nothing Python in the mount path.

Package marketplace is the /v1/marketplace surface: listing, discovery, and install of tools + agents per org/project, plus monetized listings that declare a price + recipient wallet and enforce through the x402 seam.

Package meet is the CONTROL plane for the virtual office: it decides who may join which room, and says so by minting a short-lived LiveKit access token.

Package membership is the LIVE writer-membership source: the K8s Endpoints poll that plugs into internal/org's Source seam so the horizontally-scaled cloud tracks its CHANGING pod set instead of a static list.

Package metering is the ONE way every Hanzo product meters usage to commerce — the single billing source of truth — so that every product (not only the LLM/cloud path) can be paid for.

Package ml mounts the Hanzo Cloud /v1/ml/* and /v1/train/* surfaces: a thin, tenant-scoped bridge that turns three Kubeflow-family CustomResources into a small REST API.

Package money is the ONE exact money value for the Hanzo cloud finance stack: a USD balance carried at 18-decimal (EVM/ERC-20) precision, so an off-chain ledger amount and an on-chain uint256 credit balance are THE SAME INTEGER — no conversion or rounding at the boundary.

Package mpcseal is cloud's client-side-CEK sealing client for the SEPARATE MPC node ring (ghcr.io/luxfi/mpc).

Package notify folds the Hanzo Notify SEND surface into the unified cloud binary (HIP-0106), mounting /v1/notify/* natively in-process — the native replacement for the standalone notifyd (github.com/hanzoai/notify) Deployment.

O11Y LLM-OBSERVABILITY EVENT INGEST — the native-Go write path for LLM-observability events (traces / observations / scores), folding the RETIRED console-worker (a Node BullMQ→Valkey→Datastore worker) into the one cloud binary.

Package payout is the ONE attributed-credit money seam shared by the credit programs — referrals, affiliates, authors: read an org's metered spend (the qualify / accrual base) and grant a promo credit to its wallet (a payout made in credits, landing in commerce's Credit/trial bucket).

Package plan mounts the @hanzo/plans catalog into the unified cloud binary under /v1/plans/*, per HIP-0106.

applylive.go — the ONE version-monotonic deploy mechanic shared by the image-source path (deployImage) and the git build reconciler.

Package plugin is the control plane for the host's zip-native plugins: what each host is running, and the operations that change it — enable, disable, reload, and pin to (or roll back to) a named version.

Package prefs is the per-USER preference plane for the unified Hanzo Cloud binary: the /v1/prefs surface behind the user menu on every Hanzo surface (console, insights, and anything else that renders "signed in as").

Admin surface for the catalog enablement overlay (SuperAdmin only).

Package principal is the ONE place the cloud data plane turns a request into a org.

Package product exposes the read-only Search and Vector product surfaces the Hanzo console panels call at api.cloud.hanzo.ai, per HIP-0106.

grant.go — how CI gets bytes into a site's S3 prefix WITHOUT holding a bucket credential.

Package prompts mounts the Hanzo Cloud /v1/prompts surface: a per-org, versioned prompt library.

Package provisioning is the Hanzo Cloud provisioning control plane.

Package pubsub embeds the Hanzo PubSub core data plane (NATS + JetStream) as an in-process cloud subsystem (HIP-0106) — the same fold pattern as iam/kms/tasks.

Package referrals mounts the Hanzo Cloud /v1/referrals/* viral-loop surface: a native-Go, per-org referral program on Base/SQLite that grants promo cloud credit through the SAME commerce ledger path as clients/admin.grantCredit (the trial/Credit bucket, tag grant:referral).

Package research mounts the Hanzo Cloud /v1/research/* surface: the R&D EVIDENCE plane (HIP-0512 §"Hanzo Research").

Package rollingcap installs the ai gate's rolling-window AI-spend cap — the Anthropic-style burst limit that resets continuously (usage older than the window drops out of the trailing sum, so there is no fixed reset boundary).

ops.go mounts /v1/bot/* — the runtime's OWN operational paths (health, and the surfaces the console Bot module links out to), relayed verbatim.

Package s3admin is the ONE shared S3 access path for the unified cloud binary.

Package samples is the fleet's compute-utilization time series: ONE table, ONE writer seam, ONE read face that every compute source feeds.

Pure core of the SBOM lens: the wire types, the CycloneDX parser, the row builder, and the datastore value coercers.

Package search is THE search entry point: ONE surface, POST /v1/search, that answers "what is RELEVANT" over a tenant's own data.

Package settings is the per-org, per-product configuration plane for the unified Hanzo Cloud binary: the /v1/settings/:product surface behind every product's detail view in console.hanzo.ai (#59).

Package share fronts the zrok controller so a Hanzo org can publish a local service to a public https://<token>.share.hanzo.ai URL — "ngrok on our own stack" — folded into the ONE cloud binary.

Package sites is the public site-server for published projects: the host-routed edge that turns `<slug>.hanzo.app` into the static site a user deployed to OUR S3.

Package social mounts the Hanzo Cloud /v1/social/* surface: a native-Go, per-org social-media store on Base/SQLite.

Package s3 is the Fiber-facing subsystem that exposes an org-scoped S3 object-storage file manager as /v1/s3/* on the unified Hanzo Cloud binary (HIP-0106).

Package sync is the universal sync service (/v1/sync): cloud↔cloud data sync between connected platforms, expressed as Syncs the engine runs.

Package tasks mounts the Hanzo Tasks HTTP + UI surface natively onto the unified cloud binary per HIP-0106 — the follow-up named in cloud's durable.go ("consolidating that surface into cloud").

Package team mounts the Hanzo Cloud /v1/team/* surface: the native-Go port of hanzo team-go (HIP-0106, task #45) into the unified cloud binary.

Package templates mounts /v1/templates — the Hanzo starter-kit gallery, in TWO layers that never mix:

Package tools is the ONE tool plane for Hanzo Cloud: a single registry where every callable capability — a connector action, a user function, a zap service route, a cloud /v1 control ("full-cloud-control"), an agent, a skill, or a tool on an org's own external MCP server — is a Tool with a Source, a JSON-Schema, a per-(org,project) activation state, and an optional price.

Package tracker mounts the Hanzo Cloud /v1/tracker/* surface: a native-Go, per-org issue tracker (projects + issues) on SQLite.

Package translate serves POST /v1/translate — the ONE translation surface, two tiers behind one endpoint, one auth path, one meter (HIP-0516).

Package treasury mounts the Hanzo Cloud /v1/finance/* surface: the platform's OWN fund/reserve accounting, one layer ABOVE the per-org commerce credit ledger.

Analytics entitlement contract.

Package validators mounts the Hanzo Cloud /v1/validators/* surface: the "click → provision node + queue registration" pipeline behind GDA/SDM validator onboarding on lux.cloud.

Package venue is the org-scoped "connect a cloud account" plane: an org links its native cloud-provider accounts (DigitalOcean / AWS / GCP), and Hanzo DISCOVERS the Kubernetes clusters in each account and FOLDS them into the ONE fleet (clients/fleet) — the same registry clients/visor surfaces at /v1/clusters and clients/ml federates workloads onto.

board.go — GET /v1/fleet: the org's compute, from every source, on ONE board, each unit carrying its latest utilization.

Package wallets is the Hanzo Cloud accounts/wallets/custody/keys/sign surface (/v1/wallets/*): one configurable custody seam over three orthogonal signing backends, selected PER WALLET by its Kind.

Package webhooks is the platform-global webhook layer (HIP-0106): ONE registry plus ONE dispatcher that delivers ANY event on the platform bus to org-registered HTTP subscribers.

Native Go meta-search — the SEARCH half of /v1/websearch, replacing the reverse proxy to the (retired) SearXNG pod.

World plan enforcement contract.

Package x402 is the Hanzo Cloud native x402 pay-per-use subsystem (HTTP 402): challenge → the client pays → proof submitted → verify → serve → settle.

Package zen wires the hanzoai/zen serving layer into a cloud binary.

client.go is the ONE HTTP path from this subsystem to Hanzo Zero Trust — the OpenZiti-based fabric controller (hanzoai/zt) at zt-controller.hanzo.svc.