Know when the quiet things break.
Heartbeat checks for cron jobs, SSL expiry tracking and API monitoring in Uptime. Mail you can send from code. Scriptable with API keys and webhooks.
Get started → Read the API docs
The problem
- A nightly job stops running and nobody notices for a week.
- A certificate expires on a Sunday.
- Your app needs to send mail, but you don't want a separate vendor for it.
How vizsu helps
Heartbeats and SSL tracking
Your job pings a URL when it runs. No ping in time, you get an alert. Uptime also warns you before certificates expire.
API checks from several regions
Confirmed by every region before it pages anyone.
API keys and webhooks
Manage Uptime with vgl_* API keys. Send alerts to your own webhook.
Send mail from code
Stored messages stay in India. Mail has a REST send API with Idempotency-Key support, plus standard SMTP submission.
How it works
- Create an API key in your vizsu workspace.
- Add a heartbeat or check. Put the ping URL at the end of your cron job.
- Wire alerts to Slack, Discord, Telegram, email or your webhook.
Said plainly
We're a new company with no logos to show. The limits are real and we'd rather say them now: Mail sends to up to 250 recipients per mailbox per 24 hours. It's built for app and team mail, not bulk or marketing sends.
Questions
Is there an API?+
Yes. Uptime has a REST API under /v1 with API keys. Mail has a REST send API.
What's the Idempotency-Key for?+
Retry a send safely. The same key won't send the same message twice.
What are the sending limits?+
250 recipients per mailbox in a rolling 24 hours.
Can I use SMTP instead of the API?+
Yes. Standard SMTP submission works.
Can alerts go to my own system?+
Yes. Use a webhook channel.
Add your first heartbeat in a minute.
Get started → Questions? support@vizsu.com
Related
Cron and heartbeat checks · IT and ops
Pricing: Uptime pricing · Mail pricing