aprity
The platform

Your living single source of truth.

Functional documentation, business rules and a feedback loop at the centre — object, process and rule docs in business language, each with a confidence score that traces back to its source, current with every scan. Execution graph, integration map and impact analysis sit one layer deeper, for when you need them. No downloads, no stale files.

Portal — documentation dashboard
The living portal home — documented objects, business rules, screen flows, processes and integrations, current with every scan.
Documentation

Functional docs with a confidence score and traceability

Every object, process and rule is documented in business language — a plain narrative of what it does, not a metadata dump. A confidence score tells you how certain the analysis is, and every claim links back to the exact metadata it came from.

  • Object · process · rule pages in business language
  • Confidence score per doc
  • Source traceability on every claim
Object documentation
An object page — business narrative, a confidence score, blocking-rule counts, and tabs for rules, actors and automations.
Screen flow — functional journey
A screen flow documented end-to-end — its functional journey, plus the validation rule and automation behind it and the records each one touches.
Screen flows

Every screen flow, walked step by step

aprity documents each screen flow as a functional journey — the steps a user moves through, the records it reads and writes, and the validation rules and automations behind it. What each rule enforces and what it blocks, narrated in business language with a confidence score, never a raw XML dump.

  • Functional journey, step by step
  • Validation rules & automations explained
  • What each rule blocks, in business language
Feedback

Correct the AI once — applied to every future scan

On any doc, your experts can correct, reject, add to or clarify what the AI wrote — tied to the exact object or rule it describes. An admin reviews each submission, and on the next scan the approved corrections are fed back into the model as expert input that takes precedence over its own inference. The documentation regenerates sharper every time, so your org's knowledge compounds instead of living in someone's head.

  • Correct, reject, add or clarify — per doc
  • Admin review and moderation
  • Approved corrections steer the AI on the next scan
Feedback moderation
Feedback moderation — expert corrections sorted and resolved, then fed back into the AI on the next scan.
Change history
History — business rules added, modified and removed between analyses, most recent first, each in business language.
Change history

Read what moved between scans

Each scan is a point in time. Compare any two and see exactly which business rules were added, removed or changed — described in business language, not a technical changelog.

  • Scan-to-scan business-rule diff
  • Added / modified / removed
  • Business language, not a git log
Execution graph

Walk the real call graph

Follow a flow, process or trigger through its actual execution path. Expand any node to see what it reads, writes and calls next — rendered from the deterministic graph, not inferred.

  • Interactive, zoomable
  • Node-level read / write / call
  • Deterministic, reproducible
Execution graph
Execution graph for an object — entry points and business rules grouped by event.
Integration map
Integration map — inbound, outbound and bidirectional flows, filterable by direction and category.
Integration map

See every system your org talks to

A map of inbound and outbound integrations — API gateway, e-signature, ERP and more — with the objects and processes each one touches. Driven by the code's actual call-sites, not declared metadata alone.

  • Inbound + outbound
  • Object-level coupling
  • External system inventory
Impact analysis

Change one component — know what depends on it

Pick a field, object or Apex class and a change type, and aprity computes everything downstream that depends on it. Deterministic, so the answer is the same every time and safe to act on.

  • Computed, not guessed
  • Deletion / modification / renaming
  • Built for change reviews
Impact analysis
Deterministic impact analysis — pick a component and a change type to compute the downstream blast radius.
Deterministic first, AI second

The graph is computed. The AI only narrates.

Dependencies, impact and the execution graph are computed deterministically from your metadata — reproducible and verifiable. The LLM explains and answers on top, with citations; it never makes a decision that lands in the graph.

Explore the portal on your own org.

14-day trial, dedicated sandbox, read-only access. No credit card.

Start free trial
Start free trial