Pick a rollout model that matches your data and operations workflow. Pilots are bounded by design so you can prove the operating model before expanding.
Pilots start with one ticket queue for Pumpkin or one recurring investigation pattern for QuietLens BI.
$1,500/mo
Launch one product against one bounded workflow.
$5,000/mo
Run both products across data and operations teams.
Custom
Multi-team rollout with tailored controls, retention, and support.
All plans run through your existing PR workflow and approved data sources.
Pilot scope, access boundaries, and approval workflow are defined before any execution or investigation begins.
Every plan runs the same operating model — scope, approval gates, audit evidence. The stages differ in how much work runs under it.
Validate QuietNode inside a bounded data or operations workflow before expanding access.
One queue or one investigation pattern in scope. Access boundaries and the approval workflow are bound before anything runs.
Scoped, short-lived credentials per run. Reviewer approval gates sit before any production change or business action.
Review accuracy and the audit pack — evidence from every run, attached to the ticket or answer.
Decide on what the evidence shows: widen scope to more workflows, or stop with nothing left running in your environment.
The pilot stays bounded by design — you expand on evidence, not on a promise.
Request a pilotOperational details for teams evaluating QuietNode, Pumpkin, and QuietLens BI.
Pumpkin executes data engineering work — it produces pull requests, runs validators, and applies controlled changes. QuietLens BI investigates business questions about reports, dashboards, and KPIs — it returns plain-language answers with lineage, ownership, and evidence. Both run under the same scope, approval, and audit controls.
Get started
Scope a bounded pilot, run it under approval gates and audit evidence, and expand only when the evidence supports it. No platform commitment before the operating model is proven.