Skip to content

What is Kiket?

Kiket is a workflow-as-code platform built for teams in regulated industries—pharma, finance, healthcare, and government—who need automation that auditors trust and developers love.

The Problem We Solve

Traditional workflow tools force a choice:

Approach Speed Flexibility Compliance
Point-and-click tools (Jira, Monday) Fast setup Limited customization Manual audit trails
Low-code platforms (ServiceNow, Salesforce) Months to deploy Vendor lock-in Expensive compliance add-ons
DIY automation (Zapier, n8n, custom scripts) Depends Unlimited No audit trail, black-box

Kiket delivers all three: deploy in minutes, customize everything as code, and get blockchain-anchored audit trails built in.

Core Principles

Everything as Code

Your workflows, boards, dashboards, and AI prompts are YAML files in your Git repository:

your-repo/
├── .kiket/
│   ├── workflows/
│   │   ├── change-request.yaml
│   │   └── incident-response.yaml
│   ├── boards/
│   │   └── sprint-board.yaml
│   ├── analytics/
│   │   └── team-metrics.yaml
│   └── agents/
│       └── triage-agent.yaml

Why this matters:

  • Version control — Every change is tracked, reviewable, and reversible
  • Pull request workflows — Workflow changes go through the same review process as code
  • Portability — Your configuration is yours, not locked in a vendor database
  • Reproducibility — Spin up identical environments for testing, staging, production

Open Extension Model

Extensions run on your infrastructure—not ours. Build in any language, deploy anywhere:

graph LR
    A[Kiket Platform] -->|Signed Webhook| B[Your Extension]
    B -->|API Call| A

    subgraph Your Infrastructure
        B
        C[Your Database]
        D[Your Services]
    end

    B --> C
    B --> D

    style A fill:#7C3AED,stroke:#fff,color:#fff
    style B fill:#F59E0B,stroke:#fff,color:#000
  • No vendor lock-in — Extensions are standard HTTP endpoints
  • Any language — Python, Node.js, Ruby, Go, Java, .NET—or anything that speaks HTTP
  • Any hosting — Vercel, AWS Lambda, Google Cloud Run, Kubernetes, bare metal
  • Your data stays yours — Extensions can connect to your databases, APIs, and services directly

Compliance by Default

Every action in Kiket creates an immutable audit record:

graph LR
    A[User Action] --> B[Event Log]
    B --> C[Hourly Batch]
    C --> D[Merkle Tree]
    D --> E[Polygon Blockchain]

    F[Auditor] --> G[Verification Tool]
    G --> E
    G --> H[✓ Independently Verified]

    style E fill:#10B981,stroke:#fff,color:#fff
    style H fill:#10B981,stroke:#fff,color:#fff
  • Blockchain-anchored — Hourly batches of events are hashed and anchored to Polygon
  • Tamper-proof — Once anchored, records cannot be altered without detection
  • Independently verifiable — Auditors can verify the chain without trusting Kiket
  • Explainable AI — Every AI decision includes reasoning traces and confidence scores

How It Works

1. Connect Your Repository

Link your GitHub, GitLab, or Bitbucket repository. Kiket watches for changes in the .kiket/ directory.

2. Define Your Workflows

Write YAML files describing your states, transitions, and automations:

workflow: approval-process
version: 1

states:
  - draft
  - pending_review:
      require_approval: 2
  - approved
  - rejected

transitions:
  - from: draft
    to: pending_review
    when: submitted
    actions:
      - notify_reviewers

  - from: pending_review
    to: approved
    when: all_approvals_received
    actions:
      - create_audit_record
      - trigger_downstream

3. Push and Sync

Push your changes. Kiket validates the configuration and applies it automatically:

$ git add .kiket/
$ git commit -m "Add approval workflow"
$ git push

# Kiket syncs within seconds
# Workflow is live

4. Extend with Integrations

Install marketplace extensions or build your own:

# .kiket/extension.yaml
extension:
  id: com.yourcompany.slack-approvals
  name: Slack Approval Requests

  triggers:
    - event: workflow.state.entered
      states: [pending_review]

  handlers:
    send_approval_request:
      endpoint: /webhooks/approval

Who Uses Kiket

Regulated Industries

  • Pharmaceutical — GxP-compliant change control with 21 CFR Part 11 audit trails
  • Financial Services — KYC/AML workflows with immutable evidence chains
  • Healthcare — HIPAA-compliant patient intake and case management
  • Government — Transparent approval processes with public verification

Development Teams

  • Engineering — Sprint management, incident response, release workflows
  • DevOps — Change management, deployment approvals, runbook automation
  • Support — Ticket routing, escalation paths, SLA monitoring

Operations

  • Legal — Contract review workflows, approval chains
  • HR — Onboarding processes, performance review cycles
  • Compliance — Policy management, audit preparation

Comparison with Alternatives

Feature Kiket Jira ServiceNow Zapier/n8n
Configuration as code Yes No Limited No
Git-native workflows Yes No No No
Blockchain audit trails Yes No Add-on No
Explainable AI Yes Limited Limited No
Run extensions anywhere Yes No No Limited
21 CFR Part 11 ready Yes Manual Add-on No
Time to first workflow Minutes Hours Weeks Minutes
Data portability Full Export Complex Varies

Getting Started

Learn More