Supplier summary for quality assurance
A one-page summary your QA can attach to a supplier assessment. It describes Kaloko as it is today; the details are in Quality evidence for your QMS and on the trust page.
| Product | Kaloko: a CLI (kaloko on npm) that walks the screens of an application against written criteria, and the service at kaloko.app that stores the runs, collects people's decisions and signs records |
| Supplier | Sinfin, contact on the trust page |
| Intended use in quality-managed and regulated work | Executing and recording UI checks, collecting review decisions, producing verifiable records and evidence for the customer's own quality system |
| Not intended for | Document control, deviations, CAPA, training records or releasing a product by itself |
| Validation status | Not validated or certified by anyone; no claim of compliance with ISO 9001, ISO 13485, IEC 62304, ISO 27001, 21 CFR Part 11 or EU GMP Annex 11. The customer validates its own use |
| Hosting and data | Cloud service; where data is stored and which subprocessors handle it is on the trust page |
| Security assurance | SOC 2 being prepared, no report yet |
| Access control | Roles per organization and project; required two-step verification and session limits (Business); company sign-in over SAML or OIDC, SCIM and an IP allowlist (Enterprise); scoped, expiring API tokens |
| Audit trail | Append-only log with who, when, from where and through which client; a run's audit trail is part of its evidence package |
| Records | Signed with Ed25519 over canonical JSON; SHA-256 of every screenshot and of the run manifest; verifiable offline with kaloko signoff --verify against the published public key |
| Electronic signatures | Optional, off by default: meaning from the customer's list, a fresh second step, printed name, e-mail, time with time zone, bound to the run; changes need a reason and stay recorded. Tokens and agents never sign |
| AI | AI evaluators can suggest results; their verdicts are advisory and named with the model; people decide |
| Evidence | Per run and release, as JSON (qawalk.evidence.v1) and CSV, and as a signed zip package |
| Retention | Accepted runs stay while a Business or Enterprise plan lasts; other runs expire after the plan's retention. Database restorable to any minute of the last 30 days |
| Change control | Semantic versions and a public changelog for the CLI; versioned data formats that only gain fields within a version; the service is updated continuously and every record names the service version |
| Known gaps | No certification; no SOC 2 report; no passwords (signatures rely on the sign-in plus a second step); the service cannot be held at a version; time source not validated; no legal hold |