How it works
Buy. Connect. Run. The designed path, in early access.
Products are specified but do not run on your systems yet, and nothing connects. Setup time is a published target. Pause, undo, export, and revoke are documented before you pay.
Products in the catalog77
Target 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 are specified for every product in the catalog. Connect and run are not available yet. The only thing that changes between products is which systems you would authorise.
01
Buy (or open a workspace).
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. Billing is closed in early access: you can open an early-access workspace with no card and join the waitlist for a plan.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 (planned).
Not available yet: nothing connects in this build. The design is that, for connected products, you authorise the systems named on the card — QuickBooks Online, Gmail, HubSpot — through OAuth, without mapping fields or filing an engineering ticket. Today you can record which systems you use and request a connection.
Hosted products are designed to run on nox.markets with no OAuth at all. Self-hosted products are designed to run in your environment under a licence; downloads are not available yet. The deployment model is on the card in that language, not as jargon.
03
It runs (planned).
Not available yet: no product runs on your systems in this build, and there are no runs, outputs or schedules. The specification: 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 are specified with human approval as the default. The designed controls are pause, revoke the grant, and export the log; log export is not available yet. Cancelling would not unwind work already written to your system of record.
| Deployment | What it means for you | Products |
|---|---|---|
| Hosted | Designed to run on nox.markets. No OAuth. | 14 |
| Connected | Designed to run on nox.markets and act in your tools through OAuth you can revoke. | 57 |
| Self-hosted | Designed to run in your environment. We license it. | 6 |
| Type | What you get | Products |
|---|---|---|
| Tool | A hosted desk you use directly. | 22 |
| Agent | A worker specified to act on a trigger or schedule. | 22 |
| Workflow | Specified 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. Not in this build: products do not run yet, so there is no run on your own data. An early-access workspace lets you request setup, and a person at nox.markets replies.
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 is the specified default: nothing is designed to post until a named person clicks. Products do not run yet.
- An audit trail, with export planned. The workspace settings page shows the 20 most recent rows today. Search, filters and export are not available yet. Planned retention by plan: 30 days on Starter, 12 months on Growth, 36 months on Scale.
05 — Proof three / median 40 min
The target: live without starting a project.
Setup time is on the card as a target for when products run. These figures are read out of the catalog, not chosen for this page.
- Fastest target setup
- 25minutesThe quickest of 77 products in the catalog.
- Median target setup
- 40minutesHalf the catalog is quicker than this.
- Slowest target setup
- 120minutesThe longest target setup time in the catalog. Still not a project.
Connect, configure, run (planned)
The designed setup, not available yet: authorise the system named on the card, set the mailbox, the schedule, or the approval matrix. The product drafts; you approve. It is the same three moves on every connected product.
The connector directory lists 136 systems, none of them connected yet. 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
The design, once products run: 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 specified as self-serve: it stops the product from acting, immediately, from your own identity provider if you prefer, and the stored connector secret is deleted within 24 hours. No connection exists in this build, so there is nothing to revoke yet.
06 — Before you pay
Try it on your own data first — once products run.
A demo on our sample documents proves that our sample documents work.
The goal is a path to run a sample on your own data before checkout. Not in this build: products do not run yet, checkout is waitlisted and takes no payment. An early-access workspace needs no card and grants no credits.
Tell us a document type you actually run — a vendor PDF, an invoice, a past-due aging — when you request setup, and a demo is there if you would rather talk first.
Start
Pick one job. Tell us which one.
77 products across 7 categories, each with a target setup time and a named failure mode. Early access: products do not run yet.
Early-access workspace. No card required. Billing is closed.
