Dashboard guide

Build a dashboardwith AI.

Real-time charts, KPIs, role-based access, downloadable reports. The tedious parts of every dashboard, logins, layouts, charts and pulling in your data, built and connected for you.

northpeak.webtwizz.app

Built for you

  • ✓Supabase · Your data
  • ✓Stripe · For revenue dashboards
  • ✓PostHog · Behavioral analytics
  • ✓OpenAI · AI summaries of dashboard data ("explain this spike")
  • ✓Hosting · Live at northpeak.webtwizz.app

5 steps

From a sentence to a live app.

Step 01

Define what you want to see

Tell WebTwizz "A dashboard showing daily signups, MRR, and churn, with a date range picker and a chart for each metric." WebTwizz builds the layout, the charts, and the data behind them.

Step 02

Connect your data

Supabase for your app's own data. Or pull data from outside services like Stripe, PostHog or your data warehouse, and WebTwizz writes the code for you. Both work.

Step 03

Add filters and date ranges

Use AI to add common filters: date range, segment, time bucket. Your filters are saved in the page link automatically, so you can share filtered views.

Step 04

Add real-time updates if needed

For live dashboards, Supabase pushes updates as data changes. Otherwise the dashboard checks for new data every few seconds. WebTwizz sets up either one automatically.

Step 05

Polish layouts visually

Dashboards are visual products. Use the visual editor for spacing, card sizing, color schemes, and chart styling. Way faster than prompting for every tweak.

What you can build

Steal a prompt.

Each one opens the builder with the prompt filled in.

Why it works

The parts other AI builders skip.

Charts built in
Line, bar, area, donut and sankey charts all work out of the box, with more chart types ready when you need them. Pick whichever fits your data.
Real code, not a black box
Dashboards have a way of becoming critical. The generated code is standard, fully visible and editable in the built-in code editor.
For your customers or your team
Customer-facing dashboards where each customer sees only their own data, and internal dashboards with access by role. WebTwizz sets up both.
Works on phones by default
Dashboards built elsewhere often look bad on phones. In WebTwizz, layouts adapt to phones by default, so charts and tables stay readable.

Integrations

Wired up. One click each.

Real-time vs batched dashboards: when each one is the right call

Most "real-time" dashboards don't need to be. The question to ask before you build: how stale can the data be before a decision-maker notices? If the answer is "minutes," batch it. If the answer is "seconds," go real-time.

Batched (refreshed every 5 minutes or hourly). Right for SaaS revenue dashboards, marketing funnel reports, weekly business reviews. The numbers are calculated on the server and saved, and the page refreshes on a timer. Simple to build, cheap to run, and it handles thousands of users.

Real-time (under a second). Right for ops dashboards watching live traffic, on-call alert views, live event monitoring. Supabase pushes each change to the screen as it happens, or the page checks for new data every second. It puts more load on your database, so it costs more to run. WebTwizz can set up either one; tell it which.

Hybrid. Most production dashboards. Top-line KPIs refresh every 5 minutes. A single "live now" widget updates in real time. Cheap on the database, fast on the metric that matters.

The trap: defaulting to real-time everywhere. It's expensive and most users won't notice.

Charts that work in production: which chart to use and when

Charts are built in. Bar, line, area, pie and combined charts cover everything most business dashboards show, and they are the right pick for 90% of cases.

When you need more, ask for it. Radar charts, polar area charts, mixed charts with more than one scale, or data over time with millions of points can all be added, and large amounts of data stay fast.

For genuinely advanced visuals, like sankey diagrams, treemaps, calendar heatmaps and maps, there is a heavier charting option. It adds weight to the page, so only use it when you actually need that chart type.

Skip fully custom charts unless nothing else can show what you need. Building one from scratch takes far longer and almost never pays off.

Tell the AI "use a map for the regions view" or "make the time series handle a full year of data" and it changes that one chart without touching the rest.

The honest answers.

The questions founders actually ask before they commit to a tool.

Bar, line, area, pie and donut charts work out of the box. More chart types, and charts that stay fast with large amounts of data, are also set up if you need them.

Yes. For Supabase data, updates appear live as the data changes. For outside sources, the dashboard checks for new data every few seconds. WebTwizz handles both.

CSV export is a small addition WebTwizz builds when you ask. PDF reports can be generated too, with slightly more setup.

Yes. Supabase database rules make sure each customer only sees their own data. WebTwizz sets up the rules when you describe a dashboard used by many customers.

Different tools. Metabase and Looker are BI tools: connect to a warehouse, drag-and-drop charts, share with non-technical users. WebTwizz is for production-facing dashboards (customer-facing or internal apps) where you need real logins, real code, and real customization.

Keep reading

Start with one sentence.

Describe it, and watch the real app get built. Free to start, no credit card.