//01
Help
Included from StarterExplains how to use your app step by step, based on the screen the user is on.
1 → 1Record a process once. Kirky drafts the guide and you approve it.
Manuals · Help center · Flow recorderProduct
Five layers. One assistant inside your app.
Turn them on one at a time. Each layer reads only what you connect, answers only what each user’s role allows, and shows where every answer came from.
Stacked from the ground up
At a glance
What each layer answers, and where it reads from
Help“How do I do this, on this screen?”Manuals, your help center, recorded flowsStarterKnowledge“What does our policy say about this?”PDF, Word, scans, Drive, SharePoint, DropboxStarterQueries“Which of my orders are open?”Your read endpoints, or Postgres on ScaleBusinessActions“Mark PO-2291 as shipped.”Your write endpoints and recipesBusinessCentinela“1,200 is much more than usual. Want to review it?”Your record history, per customer and productBusiness (nightly) · Scale (live)
At work
Each layer, inside a real screen
//02
Knowledge
Included from StarterAnswers from your PDFs, Word files and scans, and cites every source. When your documents don’t say it, it says it doesn’t know.
p. 4Every answer names the page it came from.
PDF · Word · Scans · Drive · SharePoint · Dropbox//03
Queries
From Business · direct database on ScaleAnswers from your live data with the user’s own permissions. Your credentials never leave your app.
≤ 3API reads per question, run in the user’s own browser.
Your read endpoints · OpenAPI import · Direct Postgres on Scale//04
Actions
From BusinessCreates or updates records only after showing a preview and asking for confirmation. It never deletes.
0Delete operations it can run.
Preview · Confirmation · Recipes · Create and update only//05
Centinela
Nightly on Business · live on ScaleGives a heads-up before an unusual value is saved. It never blocks.
10–40The usual range it learned for this customer.
Quantities · Recipients · Duplicates · Nightly reviewIn depth
How each layer works, and what you decide
//01
Help
Plan: StarterExplains how to use your app step by step, based on the screen the user is on. It knows the route and the page, so “how do I create an order?” gets the steps for the screen that’s open.
How it works
- 1Upload manuals or point it at your help center; it reads them once.
- 2Record a process with the flow recorder: you do it once, Kirky drafts the guide.
- 3Guides are paraphrased from what you published and always cite it.
What you control
- You approve every recorded guide before anyone sees it.
- You decide which screens each guide belongs to.
//02
Knowledge
Plan: StarterAnswers from your documents and cites the page. Every quote is checked word for word against the passage before it’s shown; when your documents don’t say it, it says it doesn’t know.
How it works
- 1Upload files, sync a folder or bulk-load through the API or CLI, with a cost estimate first.
- 2Scanned pages are read with OCR; duplicates are detected automatically.
- 3Each document gets an effective date, so a current policy outranks an old one.
What you control
- You confirm which version of a document is current.
- You decide which roles can read which folders.
- Answers warn when two of your sources disagree.
//03
Queries
Plan: BusinessAnswers from your live data with the user’s own permissions. The request runs in the user’s browser against your read endpoints, with their session, so your credentials never reach us.
How it works
- 1Import your read endpoints from OpenAPI, or register them by hand.
- 2Kirky picks the endpoint, fills the parameters and reads at most three per question.
- 3On Scale, a read-only connector you host can answer from Postgres directly.
What you control
- You choose which endpoints, and which fields of each response, it may use.
- Each role sees only the endpoints you grant it.
- The connector refuses to start with anything but read-only access.
//04
Actions
Plan: BusinessCreates or updates records, only after showing a preview and waiting for the user to confirm. It never deletes: delete is not an operation Kirky has.
How it works
- 1Register your create and update endpoints; delete is never offered.
- 2Every change is shown as a preview bound to the exact data that will be sent.
- 3Recipes chain steps you define; the model only fills in the values.
What you control
- You decide which roles can run which actions.
- Nothing is written until the user presses Confirm.
//05
Centinela
Plan: Business (nightly) · Scale (live)Gives a heads-up before an unusual value is saved: a quantity far outside the normal range, a report going to a domain that customer never uses, a likely duplicate. It never blocks.
How it works
- 1It learns the usual patterns from your history, per customer and per product.
- 2On save, your form asks Centinela; the check takes milliseconds.
- 3A nightly review runs the same rules over records already saved.
What you control
- You approve every rule before it runs.
- Users can mark a warning “not applicable”, which tunes it.
Do I have to use all five layers?
No. Most teams start with Help and Knowledge, which are in every plan, and add Queries, Actions and Centinela when they’re ready. Each layer is turned on separately.
Does it work with any web app?
Yes, as long as you can add a script tag and your backend can sign a token for the signed-in user. It works with React, Vue, Angular and server-rendered apps.
What happens when Kirky doesn’t know?
It says so. In Knowledge and Queries every claim must come from a source; anything it can’t back up is removed, and if nothing is left the answer is “I don’t know”.
Which languages does it speak?
Spanish and English from day one. It answers in the language of the user’s session, whatever language your documents are in.