Quickstart

Create your account

Visit app.kiket.dev/login?mode=register and sign up with email and password or with Google or GitHub. You'll land in an empty organization — its name is taken from your email domain, you can rename it later. For details on linking accounts and sign-in options, see Sign-in and accounts.

Pick the first outcome

In onboarding, choose the outcome you want to monitor first. Kiket shows what the template creates before you commit:

• process states and case types
• expected evidence
• likely scanner findings
• evidence sources to connect
• report output

For the fastest path, choose Load demo timeline or a template with a built-in evidence path such as production change approval.

Create your workspace and first process

The same guided flow creates the organization (if needed), the workspace, a GitHub configuration repository (from a template, a new repo, or an existing .kiket/ connection), and your first monitored process. You can rename the organization and workspace later.

If a workspace already exists but has no GitHub configuration repository yet (for example you created the workspace without connecting git), the app sends you through the same wizard again to attach or create a repo for that workspace. It does not create a second workspace.

When you finish, Kiket records a process linked to that workspace. That completes foundation setup; you are not asked to run full setup again on the dashboard unless you still need a config repository or a process model (the checklist deep-links to the right screen for each gap).

Activation checklist on Process Twin

After foundation is in place, the Process Twin dashboard shows an activation checklist—not a second onboarding wizard. Headings change by state:

• Get started — no workspace yet; the primary action points back to full setup.
• Connect GitHub configuration — workspace exists but no configuration repository is linked (or no org-wide repo) yet; the primary action opens guided setup for that workspace so .kiket/ can live in GitHub.
• Finish modeling — configuration repository is in place but no monitored process yet; the UI sends you to Processes.
• Activate your operational twin — workspace and process exist; the checklist focuses on evidence, cases, scans, findings, and audit output.

Each step still deep-links to the right screen and names the output it should create:

• raw events and normalized evidence
• the first monitored operational case
• a scanner run with explainable output
• a remediation trail or resolved gap
• an audit snapshot with integrity proof context

If you are evaluating Kiket, use this checklist as the acceptance path after setup: every completed item should leave visible evidence in the product.

Connect an evidence source

Open Settings → Evidence Sources and connect the source that can prove the process happened.

• GitHub for pull requests, reviews, commits, and deployment evidence
• Jira or Linear for work item status and ownership
• Slack or Teams for approval and incident context
• webhook/API ingestion for internal systems

Each source produces raw events, normalized operational events, evidence records, and scanner context. For programmatic setup, create scoped keys under Settings → API Keys — see API & SDKs.

Run the first scan

After one case and at least one evidence record exist, run or wait for the first scanner pass. The scanner compares the process model with observed reality and creates findings such as:

• missing approval evidence
• evidence source disconnected
• stale access review
• SLA risk or breach

Resolve one finding

Open Findings to triage the scanner output. The inbox groups actionable findings by severity, shows the linked case and evidence count, explains why the finding exists, and recommends the next remediation action. From there, open the case, preview evidence, or start remediation.

Generate the audit snapshot

Open Audit Room and generate a report for the monitored process. The report pulls from the same graph: process model, cases, evidence, findings, remediation, scanner runs, and optional integrity proofs.