Pilot intake
Start with the safest database we can prove value on.
A strong pilot does not begin with blind production access. It begins with the right target, least-privilege credentials, clear success criteria, and a decision date.
Intake checklist
What we need before touching a real workload.
These fields keep the pilot scoped, defensible, and safe enough for security review.
Company and workload
- Company name
- Primary contact
- Postgres version
- Cloud or self-hosted database provider
Pilot target
- Staging database or read-only production replica
- Approximate database size
- Top performance pain
- Current monitoring tools
Access posture
- Least-privilege database role
- VPN or allowlisted ingress needs
- Security review owner
- Approval owner for any change
Success criteria
- Queries or workflows to improve
- Acceptable proof evidence
- Rollback requirements
- Conversion decision date
01
Reply with the intake details
We confirm target scope and whether the safest first path is sandbox, staging, replica, or assisted access.
02
Security and access review
We share the security packet, least-privilege role, AI boundary, and deployment posture before credentials move.
03
First evidence run
QueryRook captures workload metadata, produces proof packets, and reports what is safe to recommend.