Public beta

Uptime monitoring
you can program.

Most monitors stop at “200 OK”. Fomkee runs your JavaScript against the response.

Join the public beta
Meet Kee Kee, Fomkee’s one-eyed night watcher
KeeKee is watching

Programmable checks

Your API responds...
But is your service working?

Go beyond status codes and keyword checks. Use JavaScript to define what healthy means for your service.

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”

Three ways to know it broke

Simple to start.
Powerful when it matters.

Start with the basics. Add logic when status codes aren’t enough.

02

Every 30 seconds

HTTP monitoring

Watch websites, APIs, and endpoints for availability, correct responses, and performance from multiple locations.

Fast setup, useful by default.

03

Never miss a beat

Heartbeat monitoring

Know when scheduled jobs, backups, workers, and cron tasks fail to check in on time.

Silence becomes a signal.

CLI + coding agents

Your monitors,
from the terminal.

Add a health endpoint, watch a scheduled job, or bring your coding agent along to write a custom check.

  • Works across personal and company workspaces
  • Built-in skills let agents manage monitors and checks
  • Incidents, maintenance, and alerts are scriptable
  • Native on Linux, macOS, and Windows

Try asking your agent

“Monitor https://example.com/health in my personal fomkee workspace.”
fomkeecli — zsh
# Connect a workspacefomkeecli workspace connect personal# Add your first monitorfomkeecli monitor create http https://example.com/health# See what Kee is watchingfomkeecli monitor list# Hand the skills to your coding agentfomkeecli skill export ./fomkee-skills

Everything around the check

Built for teams that ship.

Fewer false alerts

Checks run from servers in different locations. An outage needs confirmation before it becomes an alert.

Workspaces

Several projects and people, with role-based access in one place.

Status pages

Post updates during incidents and planned maintenance.

SLA reports

Track uptime, SLA targets, and error budgets on supported plans.

Recorded responses

Inspect what your endpoint actually returned when body capture is enabled.

Kee keeps watch

● Kee keeps watch

Ship while Kee watches the boring stuff.

For indie developers and small teams. Join the waitlist and tell us what’s missing.