TECHPARTNER CONSULTING

Codester demo · Business software

DataDeck — Business Dashboards

A dashboard program you run on your own server: connect a CSV, a Google Sheet, or a database, and read revenue, spend, and traffic as charts instead of raw exports.

$79 on CodesterBoot test: full stack up, queries run for real3 starter dashboards included

The Sales Overview, built from the starter pack

During packaging, the whole stack was booted and the Sales Overview starter dashboard was actually built in it — on the fictional sample sales file that ships in the package (January–June). Revenue by month up top, orders and top products below. The buyer builds the same dashboard by following the printed guide.

The finished Sales Overview dashboard on the package's sample data — real totals from the sample file (top product: Coffee Beans 1kg, 4320). Sample data, labelled as such here and in the guides.

One chart, full page

The Revenue by month query with its chart: 1281 in January rising to 2709 in June — the same totals the starter guide prints, so a buyer can check their own build number for number.

Revenue by month chart on the sample data, from the packaging test run.

First run

The first screen creates the admin account. Everything after that — connecting data, writing the first query, pinning the first chart — is walked through in the starter guides.

First-run setup screen from the packaged program. Its built-in screens keep the program's original name and logo; DataDeck is the package — install kit, starter dashboards, query library, and docs — around that pinned program.

Booted and queried during packaging

Real lines from the packaging boot test: the setup step completed (exit 0), the web app answered and sent the browser to the login page, the admin signed in (200), and the starter-pack queries were executed by the app's own worker against the sample data.

=== DataDeck boot test — Thu Nov 12 16:28:37 UTC 2026 ===
=== create_db (the install script's setup step) ===
create_db exit: 0
302 -> http://localhost:5000/login?next=http://localhost:5000/
=== Route A validation: create business DB, load all 3 sample CSVs ===
=== queries-postgres.sql: Sales Overview ===
=== queries-postgres.sql: Website KPIs ===
=== queries-postgres.sql: Expense Tracker ===
=== All five services during the test ===
=== Worker log (query jobs run by the worker service) ===
=== API build of the Sales Overview dashboard (via the app API) ===
login 200; data source 'Business data' (Postgres -> business DB) created id=1

What it does