Docs / 06 of 14

How products work

How tool, agent, workflow, and pack products run: deployment models, activation, pause, runs, and what a product will not do. For workspace admins.

Sep 15, 20263 min read

Every catalog listing is a Product with a slug. You buy a job, not a canvas. This page is the operator view: how a product is shaped, how it starts, how it stops.

Product types

`product_type`	What the admin operates
`tool`	A hosted desk the user sits at. Someone is at the keyboard. Example pattern: assemble and send an invoice.
`agent`	A worker on a trigger or schedule. It runs when nobody is typing. Example pattern: watch an AP mailbox and open a draft bill.
`workflow`	Multi-step automation across systems, often with little UI of its own. Example pattern: payroll file in, preview out.
`pack`	A curated bundle sold as one job-to-be-done. Entitlements expand to the member products. Example pattern: month-end close prep.

tool / agent / workflow are three delivery shapes for the same promise: pre-integrated, named for the job, with a time-saved rationale on the card. A pack is the bundle.

Deployment

The card shows deployment in buyer language, not as jargon.

`deployment`	Where it runs	How it acts
`hosted`	On nox.markets	In the product UI. No OAuth.
`connected`	On nox.markets	In the customer's systems of record through grants you can revoke.
`self-hosted`	In your environment	We license it. Nothing in that path is required to leave your network. Runs consume 0 credits (your keys).

starter and growth cover hosted and connected. self-hosted is an enterprise (and licensed) path. BYOK model keys are a scale / enterprise option and bill at 0.35× credits. Configuring BYOK in the dashboard is Not yet available in this build.

Acquisition vs running

A Product has one acquisition pricing_mode:

one-time — perpetual license in this Organization for that slug. Runs still spend credits.
subscription — a per-product recurring line, or a standalone monthly for buyers who refuse a plan.
included — covered once the Organization's plan tier reaches tierIncludedFrom.
usage — metered overlay. Credits are the unit of work for runs even when acquisition is one-time or included.

You can own the product. You cannot own the inference, except on self-hosted.

Access is not the price tag. Access is an Entitlement. See Managing entitlements.

Activate

Confirm a live Entitlement (active, trialing, or grace) at /dashboard/products.
For connected products, authorize required integrations. Required connectors are marked on the product record.
Open /dashboard/products/[slug]/settings: schedule or trigger, output destination, approval owner.
Run once on your own data from /dashboard/products/[slug].
Inspect /dashboard/products/[slug]/runs.

setup_minutes on the card is the promised click-path for an admin who already has rights in the connected system. Packs can exceed an hour; the card states the number. Do not treat “under an hour” as universal.

Concurrent scheduled agents: 3 on starter, 12 on growth, 40 on scale, unlimited on enterprise. Hitting the cap is a plan limit, not a product bug.

Pause, resume, off switch

Use Pause this product on product settings. Confirmation: {name} is paused. It will not run until you resume it. Data already in your system of record is unchanged.

Pause is not revoke. Pause stops triggers in nox.markets. Revoke the OAuth grant if the product must not be able to act even if someone hits Resume. See Connecting integrations.

Cancellation of a plan does not unwind invoices, bills, or CRM records already written. That work is in your system of record.

Runs and autonomy

A run consumes the product's published credits_per_run (and overflow on Class H/X bands) up to the per-run ceiling. The loading state names the cost: Running. This uses {credits} credits ({usd} at your rate). Ceiling {max}.

Every agent and workflow states an autonomy level on the product page. For finance-backoffice, human approval exists and is the default. Extracted fields should cite the source document. You are approving, not trusting.

READ_ONLY Entitlements (grace after trial end, failed payment, or downgrade) open the UI and history. Run, schedule, and triggers stay off. API calls for that product return 403 with code entitlement_read_only.

Packs

A pack Product is entitled like any other. At resolve time, member products in the pack's Collection are expanded into their own Entitlement rows with reason pack:<pack-slug>. You operate the members as separate product workspaces. You do not buy the members twice.

What products will not do

They will not invent a late fee, pay a vendor bill, or submit payroll because a model felt confident.
They will not map fields for you on a system that is not on the card.
They will not stay accurate if you skip the named failure mode on the product page.
Third-party sellers are not in the launch catalog. Listings are first-party: we built them, we integrate them, we pick up the phone.