One scenario becomes a tutorial, a manual, and a test.
tessvia derives cross-service tutorial delivery, auto-generated manuals, and E2E tests from a single scenario of record.
tessvia, by the architecture
Projections derived from one scenario (tutorial, manual, scenario-test)
Core package split (core, react, adapter)
Single scenario of record (immutable revisions)
Core capabilities
Delivery, UI, and execution are split into separate packages around a React-independent core.
utt-core (React-independent core)
Scenario schema (zod) and a TutorialEngine that drives start/next/skip/complete step control, plus audience and trigger evaluation.
utt-react (UI layer)
TutorialProvider and the useTutorial hook, plus a full set of UI components: Overlay, Spotlight, Tooltip, CenterModal, and BottomSheet.
utt-adapter
A React-independent adapter providing data-tutorial-target resolution, an action registry, a progress store (remote/local), and an HTTP service client.
tutorial-service (delivery API)
A delivery and progress-tracking service built on Node's standard http only. It manages scenario CRUD and per-service delivery/progress in DynamoDB.
Why tessvia
Stop rebuilding onboarding per service
Services like promptflow simply embed the SDK and reuse the same delivery and progress-tracking backbone.
One scenario, several deliverables
An authored scenario is derived, at the same time, into an in-app tutorial, an auto-generated manual, and an E2E test — a single-source design.
No DOM selectors in delivery payloads
targetId is resolved by the app's own Target Registry, so delivered data never depends directly on DOM structure.
Secure authentication via Onion SSO
Authoring and admin screens sign in through Onion (OAuth 2.0 + PKCE).
Cost-governed AI generation
Manual auto-generation avoids Anthropic's pay-as-you-go API, running instead on cost-capped, multi-provider setups including an in-house $0 local LLM option.
Who it's for
Built for teams handling onboarding, manuals, and testing across multiple services.
Product teams / PMs
Teams that want to manage onboarding and in-app guidance for multiple services in one place.
Frontend engineers
Developers who want to embed utt-react / utt-adapter as an SDK to add tutorials to their own apps.
QA / test managers
Teams that want to reuse tutorial scenarios directly as E2E tests (Playwright).
Manual authors
People who manage and publish manuals auto-generated from operation scenarios.
Keep selectors out of the delivery JSON — that's the foundation of a tutorial platform that survives change.
Frequently asked questions
The utt-adapter HTTP service client talks to the central tutorial-service (delivery API), which delivers scenarios and tracks progress per service.
Try tessvia
Embed the SDK and deliver tutorials, manuals, and E2E tests from a single scenario.