Screen by screen Local-first Audit-ready

A guided tour of QueryWell

QueryWell Studio combines scheduled Fusion replication with a desktop SQL and reporting workbench. Data Loader creates reporting copies of selected, supported tables in your Oracle Autonomous Database. Query Studio stores results on your device; optional AI runs connect directly to the model provider you select. Explore the screens below, or jump to Data Loader.

Three steps to your first report

  1. Add and test your pod in Connections — enter the URL and pod credentials, set the BI Publisher data-source pool, and click Test.
  2. Run SQL or reports in Query Studio, or open a curated script from Toolkits. Fill any parameters and click Run.
  3. Review the grid, then export to CSV / JSON / XLSX / PDF. History and Exports keep a full audit trail automatically.

The workspace at a glance

A calm, enterprise layout: a navigation rail on the left, the active workbench in the centre, and context panels — parameters, inspector, logs — on the right. Colour-coded status badges tell you what's safe to run at a glance.

No Oracle credentials yet? A built-in Demo (Mock) connection lets you explore every feature offline.

QueryWell Dashboard showing workspace status, active connection, and recent run and export activity.
01 · Dashboard

A quick read on status & recent activity

Your landing overview: the active connection, today's run and row counts, and a recent-activity list you can use as a jump-off point to repeat or review a run. Green means the active pod is connected and ready; amber means a profile still needs testing.

For recurring reporting data in your own ADB, evaluate Data Loader with the tables, permissions and refresh cadence you need. Review source workload and coverage before scheduling a replica.

02 · Connections

Create and test a profile for each pod

Add a profile, enter the pod URL, choose an auth type, and set the BI Publisher pool (e.g. ApplicationDB_FSCM). Click Test to verify, then select the profile to make it active.

Credentials live in the OS keychain — never in plain text, never in the app's database — and are only ever sent over HTTPS. A failed test is a real failure — 401/403 are reported as failures, so a green test genuinely means you can run reports.

Before connecting a live pod, review the Oracle Fusion API authentication requirements for your account and reporting setup.

QueryWell Query Studio worksheet with a SQL editor, parameter inspector, and a fast results grid.
03 · Query Studio

Free-form SQL, straight through BI Publisher

The worksheet takes read-only SQL and runs it through BI Publisher against your pod — including wildcard SELECT *. Pick a connection, type your query, fill any parameters in the right-hand inspector, and click Run. Your existing catalog reports run from the separate Reports screen.

Reporting-only is enforced in code, not offered as a setting: an allow-list SQL guard runs on every worksheet run and every Save As — single-statement SELECT/WITH only, no DML, no DDL, no PL/SQL — and your row limit is applied as a hard cap on the query itself. There is no switch to turn any of it off.

04 · AI Workbench

Describe, inspect, refine

The Studio + AI tier adds a separate workbench inside the same app. Ask for a report in business terms, then inspect the SQL, parameters, tool run and returned columns before saving or distributing the result.

Start from a question or report pack

Generate an ad-hoc report or begin with Finance, AP, AR, Cash, Fixed Assets, Workforce, or Operations & Job Health. Follow-up messages refine the current report rather than discarding it.

Connect your approved model provider

Add Anthropic, OpenAI, OpenRouter or a compatible Ollama endpoint. Provider keys stay in the OS keychain; the built-in sample report works without a pod or provider key.

Review before relying

Read-only guards and row limits run in code. Report fields must match actual result columns, and KPI deltas are calculated from returned values rather than invented by the model.

Save, export, deploy or schedule

Keep reports in Collections, export tabular data or PDF, deploy a report individually to BI Publisher, or arm a recurring pod-side run with optional completion email.

QueryWell Toolkits showing curated DBA and Audit SQL alongside saved personal snippets.
05 · Toolkits

DBA, Audit & My Snippets

Curated ITGC/ITAC and DBA SQL, mapped to controls and ready to open straight into a worksheet — set your bind values and run. Save your own go-to queries, or upload existing .sql scripts into My Snippets and reuse them across connections.

Use Toolkits as your repeatable starting point for standard audit, DBA, finance, HCM and SCM queries.

QueryWell Results view with a virtualized data grid, an instant chart, and column profiling.
06 · Results

Grid, charts & column profiling

Explore big result sets in a fast virtualized grid, turn any result into an instant chart, and profile a column to see distributions, ranges and outliers — so trends jump out before you export.

QueryWell History log listing every execution with timestamps and masked sensitive parameters.
07 · History

Every execution, traceable

Search recorded query and report executions by time, connection and masked parameters. Re-open a past run to repeat it or review what was executed. Data Loader has its own run view and per-table outcomes.

Sensitive parameter names — token, key, IBAN, account and the like — are masked in the log automatically.

QueryWell Exports log showing CSV, JSON, XLSX and PDF files each with a SHA-256 hash recorded as evidence.
08 · Exports

Hashed export evidence you can re-verify

Send results to CSV, JSON, XLSX, or a polished PDF report. Every export is SHA-256 hashed and recorded in the export log, and Verify re-hashes any file you point at and compares it to the logged value — so you, or an auditor, can confirm the file is still the one QueryWell wrote.

QueryWell Data Loader mid-mirror: the live run header with elapsed time, throughput and ETA range, milestone markers, and per-table progress across loading, pending and done states.
09 · Data Loader

Create a Fusion reporting replica in your own ADB

Data Loader is included in Studio. With approved BI Publisher access and an Oracle Autonomous Database target using ORDS REST-enabled SQL, discover accessible tables, recreate supported columns and plan incremental or full loads according to each table's usable keys and watermark. The run view shows progress and loaded, failed or skipped table outcomes.

Schedules run while QueryWell is open, including in the system tray or menu bar. Durable checkpoints support recovery of interrupted incremental loads. Scheduled runs resume unfinished work when the app is running again and the schedule is due; full-refresh tables restart safely.

QueryWell applies pod-stored policy in the client and keeps local run records; publishing the per-user pod ledger is best-effort. Optional delete reconciliation can remove target rows absent from a full source-key scan after policy and safety checks, and is disabled by default. Review coverage and deployment requirements before loading.

10 · Settings

Security, licence & your data

Manage your licence, review security options, and stay in control of local data. QueryWell stores connection metadata, history, audit logs and saved queries on your device. Update checks send limited product and install metadata; AI runs connect directly to the model provider you configure.

Ready to put it to work?

Evaluate Data Loader, Query Studio and the optional AI Workbench for 14 days, then choose the perpetual capability tier that fits your work.

Own it outright, optional support Audit-ready exports out of the box No QueryWell reporting cloud