MySQL workspace
Accepts .txt, up to 16 files. Report ready in about 5 min.
MySQL / PostgreSQL / KingbaseES · Oracle roadmap
Upload a collector bundle, dbcheck scores health, ranks risks, draws charts, and ships a polished Word report. MySQL, PostgreSQL and KingbaseES ship today; Oracle is on the roadmap behind the same contract.
Engines
Each engine keeps its own collector and report model, but shares one upload, queue, history and download experience.
Accepts .txt, up to 16 files. Report ready in about 5 min.
Accepts .log / .txt, up to 10 files. Report ready in about 15 sec.
Accepts .txt / .log, up to 10 files. Report ready in about 20 sec.
Planned: AWR/ASH, tablespaces, wait events, backup & recovery, security, parameter audit.
Workflow
Drag in MySQLHealthCheck, pg_check or kes_check output; anonymous sessions stay isolated.
Portal creates the job, dispatches to the right engine, the UI polls for status.
SQLite records score, host, risk counts, AI summary, and delivery path.
Out comes a deliverable Word doc: cover, TOC, charts, risk inventory, remediation plan.
Platform
Not raw log translation. Every finding ships with Evidence → Impact → Action, plus copy-paste SQL where useful.
One `docker run` and it lives in your own DC. Your inspection data never leaves the network.
Plug OpenAI / DeepSeek / Ollama in to render a 300-word executive summary your CXO actually reads. Off by default.
First-class API. `curl -F` to submit, poll for results. Every inspection is a CI artifact.
Inspection files can contain DB parameters, account names, and sample table data. On the public SaaS at dbcheck.org, anonymous uploads are physically deleted after 24 hours; signed-in history is retained until you delete it. If even 24 hours is too long, self-host and disable the AI summary to stay fully offline.