🚀 Try Schedify: schedify.dev
No auth required. No infrastructure to manage. Just simple, reliable task scheduling for developers.
A self-hostable, ultra-lightweight HTTP task scheduler for the weird and wonderful automation you want.
Schedy lets you schedule HTTP POST requests to any endpoint at any time, with custom headers and payloads. Perfect for webhooks, bots, reminders, integrations, and all sorts of automation—without the bloat.
You can run Schedy instantly using Docker from either GitHub Container Registry or Docker Hub:
From GitHub Container Registry:
docker run -p 8080:8080 ghcr.io/ksamirdev/schedy:latest
From Docker Hub:
docker run -p 8080:8080 ksamirdev/schedy:latest
You can also use a specific version tag (e.g., v0.0.1
):
docker run -p 8080:8080 ghcr.io/ksamirdev/schedy:v0.0.1
# or
docker run -p 8080:8080 ksamirdev/schedy:v0.0.1
Set an API key for security (optional but recommended):
docker run -p 8080:8080 -e SCHEDY_API_KEY=your-secret ghcr.io/ksamirdev/schedy:latest
- 🕒 Schedule HTTP tasks for any time in the future
- 🪶 Ultra-lightweight: single binary, no external dependencies except BadgerDB
- 🏠 Self-hostable: run anywhere Go runs (Linux, macOS, Windows, ARM, x86)
- 🔒 Custom headers: add auth, content-type, or anything else
- 🧬 Flexible payloads: send JSON, form data, or plain text
- 🦄 Weirdly simple: no UI, no cron, just HTTP
Head to Releases and grab the latest schedy
binary for your OS/architecture. No build required!
SCHEDY_API_KEY=your-secret ./schedy --port 8081
Schedy will listen on the port you specify with --port
(default: 8080
).
If you set the SCHEDY_API_KEY
environment variable, all API endpoints require the X-API-Key
header.
Send a POST to /tasks
(requires X-API-Key
header if enabled):
curl -X POST http://localhost:8080/tasks \
-H "Content-Type: application/json" \
-H "X-API-Key: your-secret" \
-d '{
"execute_at": "2025-05-26T15:00:00Z",
"url": "https://webhook.site/your-endpoint",
"headers": {"Content-Type": "application/x-www-form-urlencoded", "Authorization": "Bearer TOKEN"},
"payload": "foo=bar&baz=qux"
}'
execute_at
: When to run (RFC3339, UTC)url
: Where to POSTheaders
: (optional) Map of HTTP headerspayload
: (optional) Anything: JSON, string, bytes, form data, etc.retries
: (optional) Number of retries.retry_interval
: (optional) Wait time between retries in milliseconds (default: 2000).
JSON payload (default):
curl -X POST http://localhost:8080/tasks \
-H "Content-Type: application/json" \
-H "X-API-Key: your-secret" \
-d '{
"execute_at": "2025-05-26T15:00:00Z",
"url": "https://example.com/webhook",
"payload": {"hello": "world"}
}'
Form data:
curl -X POST http://localhost:8080/tasks \
-H "Content-Type: application/json" \
-H "X-API-Key: your-secret" \
-d '{
"execute_at": "2025-05-26T15:00:00Z",
"url": "https://example.com/form",
"headers": {"Content-Type": "application/x-www-form-urlencoded"},
"payload": "foo=bar&baz=qux"
}'
Plain text:
curl -X POST http://localhost:8080/tasks \
-H "Content-Type: application/json" \
-H "X-API-Key: your-secret" \
-d '{
"execute_at": "2025-05-26T15:00:00Z",
"url": "https://example.com/text",
"headers": {"Content-Type": "text/plain"},
"payload": "hello world!"
}'
Send a GET to /tasks/list
(requires X-API-Key
header if enabled):
curl -X GET http://localhost:8080/tasks \
-H "X-API-Key: your-secret"
Returns a JSON array of all scheduled tasks.
- No cron, no YAML, no UI, no cloud lock-in
- Just HTTP, just works
- For hackers, tinkerers, and anyone who wants to automate the weird stuff
PRs, issues, and weird use-cases welcome! See CONTRIBUTING.md.
MIT. See LICENSE.