DOKUMENTATION

PoC acceptance checklist

A copyable checklist for jointly defining deploy, integrate, prove, and operate targets.

How to use this checklist

Copy the items below into your architecture-review notes. Keep only what matters for the first PoC, then attach owners and dates. Targets are jointly agreed and proven in your environment.

Deploy

Confirm the control plane can run inside the agreed private boundary.

— Deploy the control plane into customer Kubernetes or the agreed private environment
— Confirm DNS, TLS, ingress/egress, and persistent storage owners
— Keep demo credentials out of any real environment

Integrate

Prove one representative path into your existing stack.

— Connect one representative data source or event stream
— Confirm identity source / RBAC mapping for the evaluation workspace
— Record which engines and stores are in scope for the first PoC

Prove

Run end-to-end scenarios that mirror the buying decision.

— Run one batch or streaming workload end to end
— Validate one approval, audit, or decision-replay path
— Capture screenshots or exports as acceptance evidence

Operate

Leave the PoC with an explicit day-2 boundary.

— Confirm ownership for permissions, backup, monitoring, and support
— List open risks for HA, SSO, migration, and response targets
— Decide go / no-go and the next scoped rollout step

This guide consolidates repository README files, deployment notes, security guidance, and anonymized engineering records. Validate environment-specific decisions during architecture review.

Open source repositories