How it works
Buy. Connect. It runs in the tools you already open.
No engineering ticket on Starter or Growth. Setup time is a published number. Pause, undo, export, and revoke are documented before you pay.
Products in the catalog77
Published setup times25–120 minutes
Connectors in the directory136
01 — The path / 3 steps
If setup needs a project plan, it does not ship.
The same three steps for every product in the catalog. The only thing that changes between them is which systems you authorise.
01
Buy (or start the trial).
Pick a product the way you pick software: name, hours at a stated volume, setup minutes, price, and whether it is a
tool,agent,workfloworpack. Or start a 14-day Growth trial — 25,000 credits, no card.There is no permanent free agent tier. Unattended work that runs at 2am cannot be given away without turning our cost of goods into your usage.
02
Connect.
For connected products you authorise the systems named on the card — QuickBooks Online, Gmail, HubSpot — through OAuth. You do not map fields. You do not file an engineering ticket.
Hosted products run on nox.markets with no OAuth at all. Self-hosted products run in your environment and we license them. The deployment model is on the card in that language, not as jargon.
03
It runs.
An agent or workflow fires on the schedule or trigger you set and writes its output into a tool your team already opens — a draft bill in Bill.com, a reminder from the AR mailbox, a payroll preview Gusto can import. A tool is a desk you sit at: invoices, quotes, a cash view.
Finance products default to human approval. You can pause, revoke the grant, and export the log. Cancelling does not unwind work already written to your system of record.
| Deployment | What it means for you | Products |
|---|---|---|
| Hosted | Runs on nox.markets. No OAuth. | 14 |
| Connected | Runs on nox.markets, acts in your tools through OAuth you can revoke. | 57 |
| Self-hosted | Runs in your environment. We license it. | 6 |
| Type | What you get | Products |
|---|---|---|
| Tool | A hosted desk you use directly. | 22 |
| Agent | A worker on a trigger or schedule that acts. | 22 |
| Workflow | Multi-step automation across systems, often with no UI of its own. | 20 |
| Pack | A curated bundle sold as one job to be done. | 13 |
02 — The objection / 3 proofs
You have done this before and nothing went live. Fair.
A seat licence, a workshop, a four-month consulting build. Here is why this ends differently, stated as three things you can check before you spend anything.
Why pilots stall
A pilot stalls for one of three reasons, and none of them is enthusiasm. Either it never worked on real documents, only on the sample the vendor brought. Or it worked and then security would not sign it off. Or it worked, security signed it, and nobody had the four weeks of integration work the demo quietly skipped.
So those are the three things to check, in that order, before the meeting rather than after it.
What this page is not doing
It is not telling you the technology is different this time. It is telling you what is published before you buy: a time-saved rationale with a named failure mode, a data-handling block per product, and a setup time that is a promise rather than a guess.
If any of the three is missing on a product page, that is a reason not to buy that product. We would rather write that here than argue it on a renewal call.
03 — Proof one / 77 products
It will work on data like yours — and you can check before paying.
Every detail page publishes a time-saved rationale: hours at a stated volume, with the arithmetic written next to the number. A measured evaluation (dataset, sample size, result) is planned and not published yet.
- A time-saved rationale on every product. Hours per month plus the derivation — volume times minutes per item, such as 18h from 800 tickets/month × 1.5 min. Catalog math, not a measured accuracy. A published eval is planned.
- A real input and its real output. Plausible business documents, never lorem ipsum, never a screenshot attributed to a company that did not agree to it.
- Hours with their volume attached. Time saved per month is on every card and derived in the sentence — the volume and the minutes per item, not a round number.
- A path to run it on your own data before checkout. In this build the 14-day Growth trial is that path, and it is the only completable one: checkout is scaffolded and takes no payment.
04 — Proof two / 6 finance agents and workflows
It will not create a compliance problem — and the review starts before the call.
The security review is the step that kills pilots. Everything a reviewer asks for is published, including the parts that are not finished.
- A per-product data-handling block. What is read, where it is processed, how long it is kept, whether a human can see it, and the sentence that customer data is not used to train models.
- A public subprocessor list. Every model provider included, with 30 days notice before a new entity processes customer personal data.
- Honest compliance status. SOC 2 Type II is in progress. It is not held, and the trust center shows the dated roadmap rather than a badge.
- Autonomy stated per product, with approval as the finance default. For finance and back-office agents and workflows, human approval exists and is the default. Nothing posts until a named person clicks.
- An exportable audit trail. Every action logged, exportable, with retention by plan: 30 days on Starter, 12 months on Growth, 36 months on Scale.
05 — Proof three / median 40 min
You can get this live without starting a project.
Setup time is on the card as a promise, not an estimate. These figures are read out of the catalog, not chosen for this page.
- Fastest published setup
- 25minutesThe quickest of 77 products in the catalog.
- Median published setup
- 40minutesHalf the catalog is quicker than this.
- Slowest published setup
- 120minutesThe longest published setup time we sell. Still not a project.
Connect, configure, run
Authorise the system named on the card. Set the mailbox, the schedule, or the approval matrix. The product drafts; you approve. That is the whole setup preview, and it is the same three moves on every connected product.
The connector directory lists 136 systems. Which of them a given product actually uses is on that product's card — and if a product needs a connector we do not have, its page says so before you buy, not after. An integration with no product behind it is not coverage, and we do not count it as any.
See the connector list.
Off switch
Pause in the dashboard. Revoke OAuth. Hosted data follows the retention line on the product. Work already in your system of record is not unwound, because that work is yours.
Revoking a grant is not a support ticket and it is not a downgrade path — it stops the product from acting, immediately, from your own identity provider if you prefer. The stored connector secret is deleted within 24 hours.
06 — Before you pay
Try it on your own data first.
A demo on our sample documents proves that our sample documents work.
Every product has a path to run a sample on your own data before checkout. In this build, checkout is waitlisted and takes no payment, so the 14-day Growth trial is the completable path: 25,000 credits, no card, and it converts or ends on day 14.
Bring a document type you actually run — a vendor PDF, an invoice, a past-due aging. If you cannot, the trial is still faster than a meeting, and a demo is the fallback rather than the path.
Start
Pick one job. Have it running this month.
77 products across 7 categories, each with a published setup time and a named failure mode.
14-day Growth trial. No card required.