Captures the actual work
Clicks, typed values, dropdown selections and screen changes, each with a timestamp, element label, accessibility attributes and the page it happened on.
Chrome side panel · v0.2.4
Record once.
Generate everything.
Krivyo sits in your browser side panel and watches you do the work — in Oracle Fusion, Oracle WMS Cloud, SAP, Salesforce, AppSheet or any web application. One session becomes a reviewed, branded process document. No scripting, no screenshots pasted into Word at 11pm.
Shipping today
What Krivyo does while you work
Six things happen between pressing Start capture and getting a document you can hand to a client.
Rings what you touched
Every interacted element gets a ring drawn on the screenshot, so a reader's eye lands on the right field instead of hunting across a full-page grab.
Masks what shouldn't travel
Passwords, email addresses and recognised sensitive fields are masked before the screenshot is stored. Metadata is length-limited and common patterns are redacted.
Lets you fix it before anyone sees it
Rename steps, rewrite descriptions, crop a screenshot, move the highlight, drop a step that shouldn't be there. The capture is a draft until you say otherwise.
Exports a document, not a dump
A PDF with your document title, your company logo, your client's logo and who prepared it — set once in your profile, applied to every capture after that.
Hands over the raw material too
A ZIP containing raw-session.json, process-model.json and numbered screenshots — the structured record everything else gets built from.
The whole idea
One capture. Many artifacts.
The recording isn't the product — the structured process model underneath it is. Every output below reads from the same capture.
One capture
- 01CLICK Supplier Name
- 02ENTER Nordwind Logistics
- 03SELECT Standard supplier
- 04CLICK Save
- 05SCREEN Supplier created
process-model.json
Available now
- Process guide PDF
- Screenshot evidence pack ZIP
- Structured process model JSON
Being built on the same model
- AI-written SOPs
- Test cases
- UAT execution evidence
- Defect reports
- Training guides
- Organisational knowledge base
- Process analytics
- In-app guidance DAP
- Workflow replay & automation
Three moves
How a capture becomes a document
-
01
Start capture
Open the side panel and press Start capture. Nothing is recorded before this — not a click, not a screenshot.
-
02
Do the work
Run the process exactly as you would demonstrate it. Pause when you need to fetch something, resume when you're back. Krivyo builds the step timeline as you go.
-
03
Review, then export
Read the steps back, tidy the wording, crop anything that shouldn't be in frame, then download the PDF or the full ZIP.
Who it's for
People who document the same screen for the fourth time
- Functional and ERP consultants writing SOPs during rollout
- Business analysts capturing as-is process before redesign
- QA and UAT teams that need evidence, not memory
- Trainers building guides for go-live
- Implementation and enterprise operations teams
Where it works
Any application that runs in a browser tab
- Oracle Fusion
- Oracle WMS Cloud
- SAP
- Salesforce
- AppSheet
- Internal web apps
- Anything else on
https://
Krivyo reads the page the way a person does — labels, roles and accessibility attributes — so it doesn't need an integration with the application it's documenting.
Why security teams sign off
Your capture stays on your machine
Consultants record production screens. That only works if the data doesn't wander.
Recording is explicit
Capture begins when you press the button and ends when you stop it. There is no background listening.
Storage is local
Events and the process model sit in extension session storage. Screenshots go to the extension's local IndexedDB on your device.
Nothing uploads on its own
Screenshots and entered values are never sent automatically. Issue-report attachments travel only when you tick them yourself.
No sale, no ads, no brokers
User data is not sold, not used for personalised advertising and not shared with data brokers.
Where this goes
From a recorder to a process knowledge platform
Each stage reuses the same structured capture. Nothing here asks you to record your work twice.
- Shipped
Capture, review and export
Recorder, highlight overlay, privacy masking, PDF and ZIP export, document profile with company and client branding.
- Next
AI-written documentation
Step titles, descriptions and process summaries drafted from the captured model, with the confidence and provenance already carried on each step.
- Next
Testing and evidence
Test-case generation from a recorded path, UAT execution evidence and defect reports assembled from the same screenshots.
- Planned
Knowledge and analytics
An organisational knowledge base of captured processes, plus analytics across how work is actually performed rather than how it was designed.
- Planned
Guidance and replay
Digital adoption guidance layered onto the live application, workflow replay, and automation generated from a recorded process.
Stop rewriting the same SOP
Record the process once. Hand over the document. Keep the model for everything that comes next.
Chrome 114 or later. Works in the side panel.