Does my data leave my machine?
+
Your queries, your data, your query results, and your credentials never reach our servers. DataIncisive is a desktop application — queries run entirely on your machine and go directly to your databases. We do operate servers for account login, licensing, and billing (e.g. verifying your subscription when you upgrade) — those never see your data. On Enterprise, a self-hosted control plane (for SSO, row-level security, or centralized credential management) runs on your own infrastructure, not ours, and sends us one lightweight, anonymous heartbeat a day — install ID, org name, and active user count, nothing else — so we have basic adoption visibility. It's non-blocking: login and queries work even if it fails. Separately, if you turn on Enterprise audit logging, the full text of each query is sent to that same self-hosted control plane (never to us) so your own team has a queryable record of who ran what.
Is there a free trial for Pro?
+
The Free plan is free forever — CSV, JSON, and Parquet files with full cross-source SQL joins. If you need live database or cloud storage connections, upgrade to Pro. For a limited time, Mac users can also
download a 14-day trial build with every database, cloud source, and warehouse connection unlocked, no card required. We offer a 30-day money-back guarantee on Pro, no questions asked.
What happens if I cancel?
+
You keep access until the end of your billing period. After that your account drops back to the Free plan — local file sources continue to work, database and cloud connections are paused until you resubscribe.
Which operating systems are supported?
+
macOS 11 and above (Apple Silicon) and Windows 10 and above. One license covers both platforms.
How are my database credentials stored?
+
Credentials are encrypted at rest on your device (AES-256-GCM) using a key generated and stored locally — they are never uploaded to any server. If you export a configuration file to share with a colleague, credentials are automatically stripped out first, so you never accidentally hand over a password.
Can I query across databases and files in the same SQL statement?
+
Yes — that is the core feature. You can JOIN a PostgreSQL table with a MongoDB collection, an S3 Parquet file, and a Snowflake table all in a single SQL query. DataIncisive handles the federation, predicate pushdown, and result merging automatically.
Can I INSERT, UPDATE, or DELETE data with DataIncisive?
+
No, and that's deliberate. DataIncisive is read-only against your sources by design, so it can never accidentally change or delete production data, even from a mistyped query. That's what makes it safe to roll out to every developer and analyst, and it's why security teams can approve it quickly. You can still write query results to a new destination (a table, a file, or a bucket). For editing existing rows, keep using your usual SQL client, such as DataGrip, DBeaver, or psql.
Is there a CLI for automation and scripting?
+
Yes. DataIncisive ships with di — a full command-line interface that shares the same query engine, source connections, and masking rules as the desktop app. Run queries, save results, manage sources, and refresh schemas all from the terminal or your CI pipeline.
Do you offer refunds?
+
Yes — 30-day money-back guarantee, no questions asked. Email us within 30 days of purchase and we will refund you in full.
Do you support data catalogs like Unity Catalog or AWS Glue?
+
Yes — on Team and Enterprise. Connect DataIncisive to an Iceberg REST catalog (Apache Polaris or Snowflake Horizon Catalog), Databricks Unity Catalog, AWS Glue Data Catalog, Hive Metastore, or Project Nessie, and it lists every table already registered there. Pick the ones you need and query and join them against your other sources immediately — no manual per-table setup.
How do you stop a compromised developer laptop from leaking a database password?
+
On Enterprise, an admin registers each source once on the control plane and sets its credential there — developers never see, type, or store the actual password, key, or connection string. When a query runs, DataIncisive fetches a short-lived credential directly from your control plane, uses it to connect, and never writes it to disk. Revoke someone from the roster (or via SCIM) and their access to every centrally-managed source is cut immediately — no credential rotation required.
