Pricing · Knowledge as Infrastructure

Three ways to buy.

Search tools re-read your archive every time you ask. This reads the sources once, writes down what they say, and keeps that writing current. Every price below is the whole price. No seats, no per-user math, and no sales call needed for the first two.

Rung 1 · Published Bases

Read free. Pay to stay current.

$39/month per base
or $390/year
  • Free: read every page of every published base. That part stays open.
  • Paid: the query interface. Ask a question, get an answer with citations that resolve.
  • Paid: change alerts. When the underlying law or market moves, you get an email saying what changed and which pages were rewritten.
  • Paid: the currency guarantee. The base moves when its sources move.
UAE Financial Free Zones Read freeSubscribe
US Finance Compliance Read freeSubscribe
Peptides Research Read freeSubscribe
Vertical SaaS Diligence Read freeSubscribe
Energy Storage Read freeSubscribe
Unlimited readers on one subscription. Priced per base, never per person.
Rung 3 · Private Archive

Your archive, maintained all year.

from $18,000/year
  • Your own document archive, compiled into the same cited, interlinked form and kept current as it changes.
  • One named owner for the engagement: me. A pilot runs 30 days with a day-21 review and usage data on the table.
  • The deliverable is plain markdown in a git repository. After handover it runs without me, and without any dependency on this practice.
Book a call
India engagements are quoted in INR and in conversation.
The Citation Guarantee

Every claim cites a provision that resolves to a document in the manifest. If it does not resolve, it does not ship.

This is checked mechanically, on every page, on every rebuild. It is also why a job can refuse to finish: if a source cannot be read, the pipeline stops and says exactly which source defeated it. A confident wrong answer is worth less than an honest gap, and the build is not allowed to confuse the two.

How a compile actually runs.

01

Fetch

Sources pulled from official portals, hashed, and recorded in a manifest. Never edited after fetch.

02

Compile

The corpus is written down once: instruments, obligations, entities, comparisons. Interlinked plain markdown.

03

Converge

Lint, fix, re-lint, until the pass comes back clean or the cap is hit. No silent oddities carried forward.

04

Gate

Mechanical pass/fail: zero dead links, zero uncited claims, every citation resolving. Fail means human review, not delivery.

05

Deliver

A git repository you own and a hosted copy. Then the maintenance loop keeps it true.

The honest bits.

What self-serve ever touches of your data: nothing, because there is nothing to touch.
Compile-on-demand takes public URLs only. No uploads, no confidential archives at this tier. That is a deliberate scoping choice, not a limitation being worked around.
What you own.
The compiled base is plain markdown with YAML front matter in a git repository. No proprietary format, no runtime dependency on this practice, no export problem. Open it in Obsidian, host it yourself, grep it.
Where the machinery runs.
Compiles run on infrastructure operated by the practice in India, calling model providers under their standard terms. Payments process through Dodo Payments.
Private archives and cross-border transfer.
For DIFC-regulated clients, transfers out of the free zone are papered with Standard Contractual Clauses and the notification to the Office of the Data Protection Commissioner is made before any document moves. The position is stated here so it can be asked about on the first call instead of the last one.
What is not claimed.
No customer logos, no testimonials, no results invented for this page. The published bases are the proof, and they are one click away, free to read.