More than uptime monitoring

Define what healthy means.
Fomkee keeps watching.

Fomkee watches websites, APIs, scheduled jobs, and servers. It alerts you when something is unreachable, too slow, misses a check-in, or stops working as expected.

Try it on your endpoint
  • Websites & APIs
  • Application behavior
  • Scheduled jobs
  • Server health
Meet Kee Kee, Fomkee’s one-eyed night watcher
KeeKee is watching

Start with the question

What do you need to know?

Fomkee watches what your customers can reach, what your service returns, the jobs it should run, and the server underneath it. When something stops working as expected, it alerts you.

Website & API

Can customers reach your service?

Check whether your website or API responds, returns the expected HTTP status, and stays within your latency threshold.

Know when the service is unreachable.

Programmable checks

Is it actually working?

Use JavaScript to inspect the response body and verify the conditions that make your service healthy.

Catch a service that returns 200 but the wrong result.

Heartbeats

Did the job happen?

Expect a check-in from a backup, cron job, worker, import or scheduled report.

Know when a scheduled job stops checking in.

Server monitoring

Is my server healthy?

Evaluate memory, load, disks, services, containers, PostgreSQL and backups.

Watch a small server without another monitoring stack.

Release confidence

Did the deploy leave it healthy?

After a deploy, check that your customers can reach the service and it still returns the right result.

Catch a deploy that finished successfully but left the service broken.

Alerts & incidents

What happens when something goes wrong?

Fomkee alerts you, keeps the problem in one incident, and helps you update customers.

Everyone knows what is happening and what needs attention.

How Fomkee decides

A check provides evidence. Your rule decides.Fomkee responds.

Fomkee checks your endpoint, scheduled job, or server. Your JavaScript rule decides whether it is healthy. If it fails, Fomkee opens an incident and alerts you.

A concrete example

A 200 response can still be the wrong result.

Check the response itself and verify the result your service should produce.

GET /api/health● 200 OK
{  "payments_last_hour": {    "attempted": 100,    "failed": 12  }}
{}   JavaScript checkcheck.js
const { attempted, failed } =  JSON.parse(response.body).payments_last_hour;if (attempted > 0 && failed / attempted > 0.05) {  throw new Error("More than 5% of payments are failing");}
Check result● Check failed
Message

“More than 5% of payments are failing”

Why trust the answer?

Checked from three locations. Confirmed before you are alerted.

Fomkee checks from three locations, compares their results, opens one incident, and keeps the failed checks for investigation.

  1. 01
    Check

    Run the same monitor from three independent Fomkee locations.

  2. 02
    Confirm

    Confirm the problem before one bad network path wakes you up.

  3. 03
    Respond

    Fomkee opens one incident, keeps the failed results, and alerts you.

  4. 04
    Keep customers informed

    Publish status updates during an incident, then review uptime and SLA reports afterward.

See how Fomkee handles failure

Explore the tools

Go deeper with Fomkee.

Kee keeps watch

● Kee is ready

Give Kee an endpoint to inspect.

See the response, define what healthy means, and preview the alert.