Keep one operating layer
Analysts and operators do not need a second product just because execution happens near protected data. The same logic, history, and delivery workflow stay visible.
Product
Local execution for private-network data workflows.
Use DataPilot when teams need one shared control surface but execution must happen close to protected databases. Queries, reports, and workflow steps can run inside private networks while the team still works from one product experience.
Why this matters
- protected databases stay inside private network boundaries
- teams keep one shared authoring and run-history surface
- cloud and on-prem execution follow the same product model
- private execution matters when scheduled SQL reports and Excel exports must run close to protected databases instead of sending the data elsewhere first
Run recurring delivery privately
Scheduled reports, files, and downstream workflow steps can still run on cadence without pushing raw database access into every cloud tool.
Support governed agent execution
AI and automation workflows can reuse the same controlled execution path instead of creating a separate direct-database access pattern.
Protect delivery continuity
If the business depends on recurring files, KPI refreshes, or alerts, execution needs to stay stable even when the data cannot move freely.
Teams that start with public diagramming can use the ERD site for exploration, then keep sensitive work inside DataPilot when they need private execution for protected databases.