StillOnline.tech Reviews and Details

Questions & Answers

1. Why should a person choose StillOnline.tech over its competitors?

   Choose StillOnline if you want to answer "are we up?" in minutes—without Datadog-scale complexity or cost.

   You get:

   • HTTP and SSL uptime checks with a shareable status page
   • Owner alerts via email, Slack, and Telegram
   • Page Speed on paid plans: Core Web Vitals / Lighthouse on landing URLs (up to 3 URLs per project on Pro)—separate from uptime /health checks
   • Subscribers follow incidents via Google Sign-In

   Pro ($9/mo): up to 10 projects, 100 monitored URLs, private pages, API/MCP, and Page Speed.

   Not a fit if you need logs, APM, on-call rotations, or custom status-page domains.

2. What makes StillOnline.tech unique?

   StillOnline is status-page-first uptime monitoring for indie SaaS and production AI agents—not a full observability suite.

   • Automatic public status page for every project (/s/{slug})
   • Monitor app URLs and agent health endpoints (OpenClaw, agent APIs, MCP backends) in one place
   • Page Speed (Pro/Ultimate): scheduled Google PageSpeed Insights runs (mobile + desktop) on marketing URLs—separate from uptime /health checks
   • Pro: private pages, incidents, REST API v1, and MCP for Cursor and Claude Code

3. How would you describe the primary audience of StillOnline.tech?

   • Solo founders and indie/micro-SaaS who need uptime + a public status page without self-hosting
   • Teams who track marketing page performance with Page Speed while uptime probes /health
   • AI agent operators (OpenClaw, bots, agent APIs) monitoring production agents
   • Small dev teams using REST API and MCP from Cursor or Claude Code

4. What's the story behind StillOnline.tech?

   StillOnline started from a simple pain: a small SaaS should not need a heavy observability stack to answer "is it up?" and "what should customers see?"

   We built HTTP/SSL checks, an automatic status page, and owner alerts. Teams wanted availability and speed separated—so Page Speed (Google PSI) on Pro/Ultimate covers landing and marketing URLs, while uptime keeps probing your health route.

   We also cover AI agent health URLs next to the main app. We dogfood on stillonline.tech.

5. Which are the primary technologies used for building StillOnline.tech?

   Application

   • TypeScript, Next.js (App Router), React, Prisma, PostgreSQL
   • Auth.js + Google Sign-In

   Monitoring

   • Workers for scheduled HTTP/SSL probes
   • Google PageSpeed Insights API for Page Speed (Lighthouse + CrUX where available)

   Alerts & billing

   • Email (Postfix), Slack webhooks, Telegram bot

   Integrations

   • REST API at api.stillonline.tech/v1
   • stillonline-mcp on npm

6. Who are some of the biggest customers of StillOnline.tech?

   StillOnline is built for indie builders, micro-SaaS teams, and small product teams who want uptime and status pages without a full observability platform.

   Typical users:

   • Solo founders and micro-SaaS teams (public status page + uptime alerts)
   • Marketing and growth teams tracking landing page quality with Page Speed (Core Web Vitals / Lighthouse trends)—separate from engineering uptime on /health
   • Pro product teams monitoring uptime and Page Speed on different URLs (e.g. /health vs homepage or pricing)
   • Developers running side projects and staging on private status pages
   • Operators monitoring AI agents or agent APIs alongside their main application

Is StillOnline.tech good?