How we think about solution packs, Sigma AI behind approval gates, tenant isolation, versioned application models and the path from a government pilot to a certified module.
Peek began as a tool for turning spreadsheets into charts. Working alongside public sector teams changed what we thought the product should be. This is the reasoning behind the pivot to Peek Platform.
A pilot proves a process works for one team. A pack makes it available to every team with the same problem. This is the pipeline we use to turn a government pilot into a certified, versioned solution pack without losing the details that made it work.
Isolation claims are easy to make and hard to verify. Peek Platform enforces row-level tenant isolation and ships a test suite that tries to break it on every change. This is how the enforcement and the suite are built.
Templates give you a starting point and then abandon you. Solution packs are versioned, certified application models that stay upgradeable after you adapt them. This post explains what a pack contains and how versioning changes the economics.
Sigma AI drafts blueprints, summaries and insights across Peek Platform, but none of it becomes state until a person approves it. Here is how the approval gate is designed, what it records, and why we think it is the right default.