own project · public demo · open source

Website monitor
of my own

Boardly watches uptime, performance, SSL and SEO for several sites from a single dashboard. I wrote it all myself, from idea to deployment, and the public demo uses fictional data.

boardly-silk.vercel.app
Boardly dashboard showing the status of several websites, their scores and their alerts
138automated tests
5checks per site
MITopen source
What it is

A web dashboard to watch several sites at once

My role

Idea, design, code, tests and deployment, all by myself

Status

Public read-only demo, with fictional data

License

MIT, the code is on GitHub

// the problem

Five tools
for a single glance

When you maintain several sites, knowing whether they are fine means opening an uptime monitor, PageSpeed, an SSL checker, an SEO auditor and some report for the client. Each in its own tab and each with its own account.

Boardly brings it all into one screen, with alerts when something breaks and a monthly report that can be sent without touching it up by hand.

01

Uptime

A scheduled check that tells a site that is down from one that is throwing errors, and detects the WordPress version and plugins when the site exposes them.

02

Performance

LCP, CLS and TTFB from PageSpeed Insights, or from a local Lighthouse for sites behind a firewall or on a local domain.

03

SSL

Real validity of the chain, issuer and days until it expires, so no certificate catches anyone by surprise.

04

SEO

Title, description, H1 count, images without alt text and an accessibility score, measured on the rendered HTML.

// app walkthrough

From the overview
to the report

Four real screens from the public demo. Scroll down and go through them in order.

01 · dashboard

All the sites, one screen

The home page summarizes the status of each site: uptime, Lighthouse scores, SSL and open alerts. It is a server component that reads through src/lib/queries.ts and ships its own loading.tsx.

Server ComponentsNext.js 16
02 · site

Each site with its history

A site's page plots the Core Web Vitals over a 7 or 30 day range. The charts are custom SVG, no library, with good, needs-improvement and poor bands. The geometry lives in pure functions with tests.

SVG, no dependenciesVitest
03 · alerts

Alert only when it matters

An alert fires when a site goes down, when a certificate is close to expiring or when a score drops. It shows up in the app and, if configured, in a Slack webhook too.

Slack webhookCron
04 · reports

A report that can be sent

Every month a PDF is generated per site and one overall PDF with all of them. They are built on the server with pdfkit and pdf-lib, with no external services.

pdfkitpdf-lib
dashboard · overviewstep 1 / 4
Boardly home dashboard with the status of four fictional sites
site pagestep 2 / 4
Site page in Boardly with Core Web Vitals charts
alertsstep 3 / 4
Boardly alerts list
reportsstep 4 / 4
Boardly monthly PDF reports screen
// real problems

What came up
on review

Six fixes from my own history. I found them while reviewing my own code, and each card carries the commit that resolved it.

fix · f4acc5f

A preview with unescaped HTML

A site's name and URL reached the report previews unescaped, a stored XSS. They now go through escapeHtml before being output.

fix · f4acc5f

Lighthouse launched with a shell string

The local runner built a command as text. It now uses execFile with an argument list and nothing goes through a shell.

fix · 2d4b4cb

A failing site must not stop the others

An exception on one site halted the collection for all the following ones. Now each site is collected separately and the PageSpeed request has a timeout.

fix · 2d4b4cb

SSL alerts that never cleared

A renewed certificate kept alerting because old checks were being read. Now only the latest check of each active site counts.

fix · 49a3af5

A PDF that returned a 500 error

Helvetica cannot encode some characters and pdfkit threw an exception. The text is now sanitized and the report is always generated.

fix · 1fdaf97

A GET request that triggered a scan

In demo mode, a GET route could trigger an outbound scan. Demo mode now blocks it, just like any write.

// under the hood

How the data
moves

Where the data flows

who administersBrowserdashboard, alerts and reports; no login of its own, put it behind your proxy or VPN
external schedulerCroncalls /api/cron/collect and /api/cron/health with an optional secret
monitored sitesYour websitesHTTP response, certificate and rendered HTML
// application

Boardly · Next.js 16

src/lib/one module per checkmine
Server Actionscreate, edit and delete sitesmine
SVG chartsgeometry in pure functionsmine
src/proxy.tsblocks writes in demo modemine
Prisma + SQLitedata model and queriesthird-party
pdfkit + pdf-libmonthly reportsthird-party
quality and deployment
Vitest · Testing LibraryGitHub Actions: lint, test, buildVercel · build:demo
performancePageSpeed InsightsLCP, CLS and TTFB, with an optional key for more quota
internal sitesLocal Lighthousefor sites behind a firewall or on a local domain
alertsSlackwebhook when a site goes down, a certificate expires or a score drops
NewExisting
// method

Tested,
not assumed

The cycle of every change

Every change goes out on its own branch and enters dev through a pull request. Continuous integration has to pass before merging.

01LintESLint, no warnings
02Tests138 in 18 files
03Buildand demo deployment

Decisions I made

Read-only demo modea proxy blocks writes and cron routes when DEMO_MODE=1
Fictional datafour made-up sites with 30 days of metrics, no real names
Charts without a librarycustom SVG with pure functions that can be tested
Contrast as a rulean AA contrast gate that fails if a color falls short
No secrets leaking outresponses hide the application password and the webhook
// by the numbers

Numbers
from the project

138automated tests in 18 files
27merged pull requests
5checks per site: health, SSL, SEO, performance and accessibility
MITopen license, the full code is on GitHub

Boardly is a personal project, not client work: there are no business results to report. The public demo is read-only and all its data is fictional. The figures come from the repository.

Next.js 16React 19TypeScriptTailwind CSS 4Prisma 5SQLiteLighthousepdfkitpdf-libVitestGitHub ActionsVercel
// your project

Got a project in mind?

Tell me what you need. I reply within 24 hours and, if it is a fit, you get a fixed written proposal.