A product manual, generated from the product itself.
Healthy is a real Sherkety-ERP customer — Sherkety is Atloria’s sibling product. Atloria generated Healthy’s end-user manual, and it’s served live on the customer’s own domain. This is real-world output, not a logo-wall placement: everything below is a link you can open.
471
manual pages
v47 active · public version history
docs-test.shoteco.com
the customer’s own domain
auto-provisioned TLS certificate
Agent-captured
screenshots
agents drive the running app, not a person
What this actually is
Sherkety ERP is Atloria’s sibling product, and Healthy is one of its customers. We pointed Atloria at Healthy’s product and generated the end-user manual its customers read — then published it to Healthy’s own domain. We’re telling you the relationship plainly because the proof doesn’t depend on hiding it: the manual is real, it’s live, and nothing on it was written by hand.
We’re showing it here for the same reason we show our own monorepo docs and a public repo run through /try — because you can open all three and check them yourself. That’s the only kind of proof this page trades in.
What the manual covers
The manual is a mid-market-style help center: one section per part of the product, config and usage colocated, written for the person using the software — not the one who built it.
- ✓One manual page per screen and workflow in the product
- ✓2–4 real captured screenshots per page, re-shot when the UI changes
- ✓A reader built for end users — no code, no API surface required
- ✓A public version history (v47 active) you can browse like any release log
How it was built
Three attributes of this property — each a capability that ships in the product, shown here doing real work.
On the customer’s own domain
The manual is served from docs-test.shoteco.com — the customer’s domain, not a subpath of ours — with the TLS certificate provisioned automatically. Publishing to a custom domain is a shipped, live-proven capability, not a bespoke setup.
Screenshots captured by agents
No one recorded a click-through. Agents navigate the running app and capture each screen the manual describes; when the UI changes, they go back and re-shoot. PII and secrets are redacted before a pixel is stored — redacted regions are burned into the image.
Localized, right-to-left
The manual is published in Arabic with a native right-to-left reader — the whole page flips, not just the text. Localization is one attribute of this property among several; the same pipeline publishes any language as a first-class doc version.
The bar this is scored against
We publish a manuals-quality benchmark — 8.4 mid-market and 8.2 enterprise, validated against the products each style emulates. Healthy is a mid-market-style manual; the methodology is public.
See the manuals benchmark →Generate your product’s manual the same way.
Point Atloria at your repo. It drives your app, captures the screens, writes the manual — and can publish it to your own domain, in your customers’ language.