Skip to content

Uptime Monitoring with UptimeFor.me

Appliku integrates with UptimeFor.me, an uptime monitoring service. Once your team is connected:

  • Every non-wildcard custom domain of every application automatically gets an HTTP monitor and an SSL certificate monitor.
  • After every successful deployment, Appliku starts an immediate post-deployment health check of the application's active HTTP monitors and shows the results on the application dashboard.
  • Each application gets a Monitors tab where you can manage its monitors without leaving Appliku.

Availability

The integration requires a paid Appliku plan and is currently being rolled out gradually. If you do not see the Integrations tab in your team settings, the feature is not enabled for your team yet.

Connecting your team

The connection links one Appliku team with one UptimeFor.me team. You need to be an owner of both teams.

  1. Open Team Settings > Integrations in Appliku.
  2. Click Connect Uptimefor.me. You are redirected to UptimeFor.me to approve access.
  3. After approving, pick the UptimeFor.me team to link and click Link team.

The first domain sync is queued immediately, so your custom domains typically appear as monitors in UptimeFor.me within a minute or two. After that, a periodic sync runs every 15 minutes and keeps everything converged.

A UptimeFor.me team can be linked to only one Appliku team. If you need to monitor several Appliku teams, create a separate UptimeFor.me team for each.

Automatic monitors for custom domains

Appliku keeps monitors in sync with your custom domains (see Custom Domains & SSL):

  • Adding a custom domain creates an HTTP monitor (https://yourdomain/) and an SSL certificate monitor for it, usually within a minute (the periodic sync runs every 15 minutes and picks up anything a change notification missed).
  • If you already had a monitor for that domain in UptimeFor.me, Appliku adopts it instead of creating a duplicate. Your existing settings (check interval, alerting thresholds, regions) are kept.
  • Removing the custom domain (or deleting the application) removes its automatic monitors.
  • Wildcard domains are not monitored automatically.

Monitors that back a custom domain are labeled Custom domain in the Monitors tab. They cannot be deleted directly and their target URL or hostname cannot be changed: the monitor follows the domain. Remove the custom domain in Appliku to remove the monitor. Everything else stays editable: the common settings (name, check interval, expected status codes, pause state) right in Appliku, and the full range of settings in UptimeFor.me.

Monitor quotas

Automatic monitors count toward your UptimeFor.me plan's monitor limit like any other monitor (two per domain: HTTP + SSL). If the limit is reached, the remaining domains are skipped and the team owners are notified when the problem first appears (repeated sync cycles do not re-send the same notification). Skipped domains are retried automatically, so upgrading your UptimeFor.me plan heals them without any manual steps.

The Monitors tab

Each application has a Monitors tab in its settings, listing the HTTP and SSL monitors that belong to it, with current status and last check time. From there you can:

  • Add monitors manually, for example an HTTP monitor for a health-check endpoint like https://yourdomain/health/. Manually added monitors are fully yours: you can edit and delete them freely.
  • Edit the name, check interval, and expected status codes. For alerting rules, check regions, and other advanced settings, open the monitor in UptimeFor.me.
  • Pause and resume monitors.
  • Run checks now to execute the application's active HTTP monitors immediately and see the results inline.

Team owners and admins can manage monitors; members with the developer role get a read-only view.

The same monitors remain fully visible in the UptimeFor.me dashboard, where you can also configure alerting, status pages, and everything else UptimeFor.me offers.

Post-deployment checks

After every successful deployment, Appliku starts one immediate run of the application's active, unpaused HTTP monitors. The results appear in the Monitoring block on the application dashboard: an overall verdict (all passed, or how many checks failed) plus a per-monitor breakdown with response times. Check runs share the UptimeFor.me rate limits (one run per application per minute, 30 per team per hour), which everyday deploying stays well within.

This gives you a fast answer to the question that matters right after a deploy: is the application actually up?

Post-deployment checks are a verification snapshot. They do not affect the monitors' regular schedules, statuses, or incident alerting in UptimeFor.me.

Disconnecting

A team owner can disconnect the integration at any time from Team Settings > Integrations:

  • Your monitors are not deleted. They keep running in UptimeFor.me, and Appliku releases the automatically created ones so they become fully editable there. (If UptimeFor.me cannot be reached during the disconnect, that release is skipped; the UptimeFor.me support or admin can lift the lock.)
  • Domain syncing and post-deployment checks stop.
  • Reconnecting later re-adopts the existing monitors, so nothing is duplicated.

If your Appliku plan lapses, the integration pauses (no syncing, no post-deployment checks) but the link is kept, and everything resumes automatically after upgrading. Disconnecting stays available in any plan state.

Troubleshooting

Symptom Cause and fix
"Needs reconnect" on the Integrations card The UptimeFor.me authorization was revoked or expired. A team owner clicks Reconnect and approves access again. Syncing resumes automatically.
A custom domain has no monitors Most likely the UptimeFor.me plan's monitor limit was reached. Upgrade the UptimeFor.me plan; skipped domains are picked up automatically on the next sync cycle.
Cannot delete a monitor Monitors labeled Custom domain follow the domain's lifecycle. Remove the custom domain in Appliku instead.
Monitors tab shows an upgrade prompt The integration requires a paid Appliku plan.
"Run checks now" is rejected Checks are rate limited: one run per application per minute and 30 per team per hour. Wait a moment and try again.