Quick Start
Go from zero to a live status page in five minutes. We'll create the page, connect it to one of your sites, and watch the first real health check land in the UI.
Before you start
You'll need three things:
- A Produl account with Status Pages enabled — the feature is in early access. You'll see a Status item in the sidebar once it's enabled on your account.
- At least one site already registered in Produl. Services on a status page are always tied to an existing site in your tenant.
- A public URL to probe. This is what Produl hits on a schedule — your homepage, an API health endpoint, a downloadable file, anything that returns a 2xx/3xx when your product is healthy.
Not sure what to probe?
/api/health returning200 when the database is reachable is all you need.Create the status page
- 1
Open Status in the sidebar
Click Status in the left nav. If you don't see it, contact Produl support to enable early access on your account.
- 2
Click New status page
The button is in the top-right of the page. It opens a small dialog.
- 3
Pick a site
Choose the site the status page represents. Produl auto-fills the page name and URL slug from the site — you can rename either later from Settings.
The slug becomes your public URL:
produl.tech/s/<slug>. - 4
Click Create
You land on the management view for the new page. It's already published at the slug URL — just empty because no services are monitored yet.
Add your first service
A service is one URL to probe. Most status pages have between one and ten services — marketing site, dashboard, API, tracker, docs, etc.
- 1
Click Add service
Opens the add-service dialog.
- 2
Pick a site from the dropdown
The site's domain becomes the fixed host for the probe URL. You can only monitor URLs on sites you own.
- 3
Set the path (optional)
Leave it blank to probe the site root, or enter something like
/api/healthto hit a specific endpoint. A blank path resolves tohttps://yourdomain.com/. - 4
Choose a check interval
1, 5, 10, 30, or 60 minutes. 5 minutes is a sensible default — frequent enough to catch real issues, light enough that you're not hammering your infrastructure.
Services on the same interval run at the same wall-clock minute (the
:00,:05,:10… boundaries), so intervals stay in lockstep across your whole platform. - 5
Click Add service
The service appears in the list. The first check fires within a minute.
Watch the first check
At the top of the services list is a live banner showing the countdown to the next wall-clock check boundary — for a 5-minute service, it counts down to the next :00, :05,:10… When the counter hits zero, Produl probes every due service in parallel.
Within about a second of the boundary:
- The row's checked X ago chip flashes emerald and reads
✓ just checked. - A new tick appears on the right edge of that service's strip — green if the probe succeeded, red if it didn't.
- The oldest tick falls off the left edge. The strip always shows the most recent 90 probes.
That's it — you're live
produl.tech/s/<your-slug> in a browser (incognito works, no login required) to see the public view your visitors will get.Share it
The slug URL is fine to share directly on Twitter/X, in support emails, or in docs. Most teams take the extra step of pointing a custom domain like status.yourdomain.com at Produl — it takes about two minutes and we handle the TLS certificate for you. Head to the custom domain guidenext if that's your plan.
Where to go next
- How monitoring works — exactly what the probe does, interval boundaries, the retention window.
- Incidents — auto-incidents from failed probes, and how to post manual updates during a real event.
- Custom domain — put the page on your own domain.
- Branding & visibility — name, logo, colours, and what to show the public.