How many URLs can I monitor on the free plan? What's the check frequency?

The Free plan supports up to 10 monitors with a minimum 5-minute check interval. It includes HTTP(S) and Keyword monitor types, 2 custom alert channels plus free 1-click Telegram / Discord (no setup, uncounted), and 7-day log retention.

What do paid plans include beyond the free tier?

Pro ($5/year): 50 monitors, 1-minute intervals, all monitor types (Ping/TCP/SSL and chained monitors included), 10 custom alert channels, 90-day history. Plus ($20/year): 200 monitors, 30-second intervals, unlimited custom channels and status pages, 365-day history. Free 1-click Telegram / Discord is available on every plan and doesn't count toward the limit. Chained monitors let you link multiple API calls, pass variables between steps, and loop-poll — ideal for multi-step business flows.

Which alert channels are supported?

The recommended way is free 1-click connect: bind Telegram or Discord in a single click — no bot to set up, zero config, and it doesn't count toward your limit. Self-hosted channels are also supported: Telegram (Bot Token + Chat ID), Discord (Webhook URL), generic Webhook (any URL), and Email. Each channel can be independently enabled/disabled and tested.

How long is monitoring data retained?

Free plan retains 7 days of check logs, Pro retains 90 days, and Plus retains 365 days. Data includes status codes, response times, and error messages for each check.

Where are the check nodes located?

Check nodes are currently deployed on GCP servers, routing requests through Cloudflare's network. Multi-region nodes covering North America, Europe, and Asia-Pacific are planned for future releases.

Can I use a custom domain for my public status page?

Status pages are currently hosted at status.shuttlelab.org/status/{slug}. Custom domains are not yet supported. You can customize the slug path (e.g. /status/my-company), title, and description.

Can I monitor APIs with custom headers or request body?

Yes. Both HTTP(S) and Keyword monitor types support custom request headers (JSON format) and POST request body — useful for authenticated APIs like OpenAI-compatible /v1/models endpoints. Pro plans also support AES encryption/decryption of request fields and response content (keys managed locally), plus chained monitors that feed one step's response field into the next.

How does Status Shuttle compare to UptimeRobot or Better Stack?

Status Shuttle is designed for indie developers — Pro is just $5/year vs UptimeRobot's $7/month starting price (competitor prices as of May 2026; verify on their official site). Free plan offers 10 monitors with 5-minute intervals and full Chinese UI. Our biggest differentiator is chained monitors: link multi-step API calls, pass variables, loop-poll, and encrypt fields — so you can monitor a full business flow like 'login → order → query', not just whether a single URL is alive. Most comparable tools don't offer this.

Does Status Shuttle support SSL certificate expiry alerts?

Yes. SSL certificate monitoring is available on Pro plans and above. After creating an SSL monitor, the system automatically checks certificate expiry and triggers alerts when the certificate expires within 30 days.

Can I export my monitoring data?

One-click export of monitoring data isn't available yet; check logs can be retrieved via the API endpoint /api/monitors/{id}/logs. However, when testing a request you can copy the exact outgoing request as a curl command or Python snippet to reproduce it elsewhere. The database uses SQLite, so technical users can copy the file directly for backup.

What are chained monitors and what can they do?

Chained monitors (Pro+) let you run multiple API calls in sequence, passing fields from one step's response (like a token) into the next via {{stepN.field}} syntax. They support loop polling (poll until a job completes), step-by-step testing, and field-level encryption. Ideal for monitoring multi-step flows like 'login for token → place order with token → check order status', rather than just whether a single endpoint is alive. Every step's request/response is inspectable and exportable as curl.

Back to Home

Your Reliable Uptime Companion

StatusShuttle — Lightweight uptime monitoring for indie developers

What does it do?

StatusShuttle continuously monitors your websites, APIs, and services, notifying you instantly via Telegram, Discord, Webhook, and more when they go down. No agents to install — just enter a URL and start monitoring. Supports HTTP(S), keyword detection, Ping, TCP port, and SSL certificate expiry checks. Pro plans add chained monitors — link multi-step API calls, pass variables between steps, and loop-poll, so you monitor a whole business flow rather than just whether a single URL is alive.

Chained Monitors

Link multi-step API calls with variable passing and loop polling — monitor full flows like login→order→query (Pro+)

Multi-Channel Alerts

Free 1-click Telegram & Discord (no bot setup), plus Webhook and email — get notified the moment something goes wrong

SSL Certificate Guard

Automatically detects certificate expiry and alerts you in advance to prevent service disruptions

Dead Simple

No agents, no complex rules. Just enter a URL. Designed for indie developers, not enterprises

Use Cases

• Indie developers: Monitor your SaaS products, API endpoints, and landing pages
• Small teams: Provide public status pages for customers to build trust
• DevOps: SSL expiry alerts, port connectivity checks — avoid 3am wake-up calls
• Open source maintainers: Free monitoring for docs sites, demos, and CI/CD services
• API developers: Use chained monitors to run a full 'login for token → call business API → verify result' path and ensure critical flows stay healthy

Start Monitoring Today

Free plan supports 10 monitors — if it's enough, it's free forever

Questions or suggestions?

support@shuttlelab.org

Who is Status Shuttle for?

Indie hackers monitoring their own SaaS products and API endpoints
Small teams monitoring critical business APIs for service availability
Product managers providing public status pages to demonstrate service SLAs
SMB teams that don't want to pay for UptimeRobot or Pingdom premium subscriptions

When should I use Status Shuttle?

After launching a new API that needs 24/7 availability monitoring
When your service goes down at 3am and you need instant alerts
When clients ask about SLA and you need public uptime data to show
When monitoring service response times across multiple regions
When SSL certificates are expiring and you need advance renewal reminders

How to create a monitor

Log in to StatusShuttle dashboard and click 'Add Monitor'
Enter monitor name and target URL (e.g. https://api.example.com/health)
Choose monitor type: HTTP(S), Keyword, Ping, TCP, SSL, or Chained (Pro+, links multi-step APIs)
Set check interval (Free: 5min minimum, Pro: 1min, Plus: 30s)
Click 'Create' — the monitor starts working on the next check cycle

How to set up alert channels

Easiest: in 'Alert Channels', click 'Connect Telegram / Discord' to bind in one click — no bot to set up, free, and it doesn't use your channel quota
Prefer your own bot / Webhook / email? Click 'Add Channel' and pick a type
For self-hosted, fill in config (e.g. Bot Token and Chat ID — send /get_chat_id to the bot to get the Chat ID)
Click 'Test' to verify the channel works correctly
Once enabled, alerts are sent automatically when monitors detect issues

How to publish a public status page

In dashboard, click 'Status Pages' → 'Create Status Page'
Enter page title, description, and custom slug (e.g. my-company)
Select which monitors to display
After publishing, visit https://status.shuttlelab.org/status/my-company

Status Shuttle vs alternatives (competitor pricing as of May 2026)

Tool	Check Interval	Multi-Channel Alerts	Public Status Page	Free Monitors	Paid Starting At	Chinese Support
Status Shuttle	30s min	✓ 1-click, no setup	✓	10	$5/year	✓ Native
UptimeRobot	5min min	✓ Multiple	✓	50	$7/month	—
Better Stack	3min min	✓ Multiple	✓	10	$24/month	—
Uptime Kuma	Custom	✓ Multiple	✓	Unlimited	Free (self-host)	✓
Pingdom	1min min	✓ Multiple	✓	—	$15/month	—

Frequently Asked Questions

How many URLs can I monitor on the free plan? What's the check frequency?: The Free plan supports up to 10 monitors with a minimum 5-minute check interval. It includes HTTP(S) and Keyword monitor types, 2 custom alert channels plus free 1-click Telegram / Discord (no setup, uncounted), and 7-day log retention.
What do paid plans include beyond the free tier?: Pro ($5/year): 50 monitors, 1-minute intervals, all monitor types (Ping/TCP/SSL and chained monitors included), 10 custom alert channels, 90-day history. Plus ($20/year): 200 monitors, 30-second intervals, unlimited custom channels and status pages, 365-day history. Free 1-click Telegram / Discord is available on every plan and doesn't count toward the limit. Chained monitors let you link multiple API calls, pass variables between steps, and loop-poll — ideal for multi-step business flows.
Which alert channels are supported?: The recommended way is free 1-click connect: bind Telegram or Discord in a single click — no bot to set up, zero config, and it doesn't count toward your limit. Self-hosted channels are also supported: Telegram (Bot Token + Chat ID), Discord (Webhook URL), generic Webhook (any URL), and Email. Each channel can be independently enabled/disabled and tested.
How long is monitoring data retained?: Free plan retains 7 days of check logs, Pro retains 90 days, and Plus retains 365 days. Data includes status codes, response times, and error messages for each check.
Where are the check nodes located?: Check nodes are currently deployed on GCP servers, routing requests through Cloudflare's network. Multi-region nodes covering North America, Europe, and Asia-Pacific are planned for future releases.
Can I use a custom domain for my public status page?: Status pages are currently hosted at status.shuttlelab.org/status/{slug}. Custom domains are not yet supported. You can customize the slug path (e.g. /status/my-company), title, and description.
Can I monitor APIs with custom headers or request body?: Yes. Both HTTP(S) and Keyword monitor types support custom request headers (JSON format) and POST request body — useful for authenticated APIs like OpenAI-compatible /v1/models endpoints. Pro plans also support AES encryption/decryption of request fields and response content (keys managed locally), plus chained monitors that feed one step's response field into the next.
How does Status Shuttle compare to UptimeRobot or Better Stack?: Status Shuttle is designed for indie developers — Pro is just $5/year vs UptimeRobot's $7/month starting price (competitor prices as of May 2026; verify on their official site). Free plan offers 10 monitors with 5-minute intervals and full Chinese UI. Our biggest differentiator is chained monitors: link multi-step API calls, pass variables, loop-poll, and encrypt fields — so you can monitor a full business flow like 'login → order → query', not just whether a single URL is alive. Most comparable tools don't offer this.
Does Status Shuttle support SSL certificate expiry alerts?: Yes. SSL certificate monitoring is available on Pro plans and above. After creating an SSL monitor, the system automatically checks certificate expiry and triggers alerts when the certificate expires within 30 days.
Can I export my monitoring data?: One-click export of monitoring data isn't available yet; check logs can be retrieved via the API endpoint /api/monitors/{id}/logs. However, when testing a request you can copy the exact outgoing request as a curl command or Python snippet to reproduce it elsewhere. The database uses SQLite, so technical users can copy the file directly for backup.
What are chained monitors and what can they do?: Chained monitors (Pro+) let you run multiple API calls in sequence, passing fields from one step's response (like a token) into the next via {{stepN.field}} syntax. They support loop polling (poll until a job completes), step-by-step testing, and field-level encryption. Ideal for monitoring multi-step flows like 'login for token → place order with token → check order status', rather than just whether a single endpoint is alive. Every step's request/response is inspectable and exportable as curl.