User manuals that keep up with your product.
Atloria’s agent drives your app, captures every screen, and writes the manual — per release, per locale, with secrets and PII redacted before a pixel is stored. The agent drives your app; nobody records a human.
A real product’s manual, generated by Atloria, on the customer’s own domain — live right now.
# no human clicks this — the agent drives the real app → navigate /settings/billing 200 screen ready → capture 2 shots · annotated ✓ callouts placed → redact email · card · token ✓ burned into pixels → re-shoot locale: ar (rtl) ✓ same flow · new UI ← page written. grounded in the live screen. no recording of a person.
Nobody records a human
Screen recorders watch a person click through your product once — then the screenshots age. Atloria doesn’t need the person.
Record a human
- ✕ Someone clicks the whole flow by hand — once.
- ✕ The UI ships a change; every screenshot is now wrong.
- ✕ Another language means recording the whole thing again.
Drive the app
- ✓ The agent navigates the real, running app itself.
- ✓ When the UI changes, it goes back and re-shoots.
- ✓ A new locale replays the same flow — no human in the loop.
How it works
One parse of your repository turns into a styled, screenshot-rich manual — six steps, no recording session.
Parse the repo
Atloria reads your code — the same parse that writes your developer docs.
Drive the live app
An agent navigates the running product, screen by screen — no human recording it.
Capture & annotate
Two to four screenshots per page, with callouts placed on what matters.
Structure from the screens
The information architecture is built from what the screens actually show.
Style it
Rendered in one of four manual styles, modeled on the tools your buyers already know.
Publish
A branded hub, a subdomain, or your own custom domain with an automatic certificate.
Four styles, modeled on tools your buyers know
full methodology →Each style is graded against the public docs of the market leaders it emulates — not one generic bar. We publish the two we’ve validated: 8.2 enterprise and 8.4 mid-market.
Enterprise
Dynamics 365 · Salesforce · NetSuite
User/admin split, learning paths, reference + concept tiers.
Mid-market
Odoo · Zoho · HubSpot
One section per app, config + usage colocated, decision-point framing.
SaaS
Monday · Notion · Intercom
Flat IA, “get started” per feature, friendly voice.
Corporate
SAP · Oracle Fusion · Infor
Separate App-Help / Config / Operations books; blended validation ongoing.
SaaS sits at 7.9, at the gate. Corporate has passed the structural bar; its blended score is still in validation, so we don’t headline a number for it. See the published benchmark for the full per-style breakdown.
Kept current, per release
A push triggers a staleness check: Atloria diffs your code against your docs, finds the exact pages a change touched, re-shoots the affected screens, and redrafts. A manual that describes what the product did two releases ago isn’t a manual — it’s a liability.
- ✓ Push-triggered — webhook or GitHub App, on every change.
- ✓ Precise blast radius: only the pages the change actually affected.
- ✓ Re-shoot and redraft in one click; your edits are protected on regeneration.
Shipped, not “coming soon”
Outdated-documentation flagging is a checkbox other tools are still promising. Ours runs today, off the AST — deterministic, not a reminder to go check.
Per locale, re-shot
Each language is a first-class doc version, not a machine-translated afterthought. Translations are sourced from your product’s own strings, and the agent replays the same flow to re-shoot every screenshot in that locale’s UI. Spanish, German, Japanese, Arabic — all peers; right-to-left scripts are handled natively.
Per-language versions
One doc version per locale, not a translation layer bolted on top.
Product-sourced strings
Translations come from your app’s own copy, so the words match the screen.
Screenshots re-shot
The same flow replayed per locale — the UI in the reader’s language.
RTL, natively
The reader flips end to end for right-to-left scripts.
Live proof today: the Healthy manual ships in a right-to-left locale — one attribute of the property, among many.
Redacted before a pixel is stored
Captured values are scrubbed twice — client-side on the way out, then re-scanned on the server for emails, card numbers, tokens and JWTs — and screenshot redactions are burned into the pixels. A redacted region can never be recovered from the stored asset; there’s no clean original hiding behind a black box.
How redaction works →Humans in the loop, too
The agent does the heavy lifting, but your team and your users can feed the manual directly — with two embeddable widgets you drop in with a script tag.
Recorder widget
Real user clicks become redacted draft manual pages — every step scrubbed for PII and secrets before it’s stored, then handed to your team to publish.
Tour player
Any captured flow replays in-app as a spotlight walkthrough — the same on-page guidance you’d expect from a product-tour tool, generated from the flows you already have.
One parse, two audiences
The same parse of your repo writes the developer docs and the end-user manual. Nobody schedules a second documentation project — it’s the same knowledge, re-audienced for people who will never read code. To our knowledge, no other manuals vendor ships both from a single source.
See it, and the numbers behind it
Live manual
docs-test.shoteco.com
A real product’s user manual on the customer’s own domain — 470+ generated pages with public version history, screenshots captured by agents driving the live app. Nothing on it was written by hand.
Open the manual →Published benchmark
8.2 / 8.4 — scored and shown
We grade every generated manual against rubrics modeled on the products buyers already know, and publish the numbers: 8.2 enterprise, 8.4 mid-market. To our knowledge, no other manuals vendor publishes any quality score at all.
Read the methodology →The manual writes itself. From your code.
Point Atloria at a repo and get docs in about a minute — then let the agent go drive the app and shoot the manual.