GigWatch
A self-hosted freelance-gig watcher. GigWatch monitors live job/gig feeds, filters them against your skills, remembers what it has already shown you, and alerts you (console, email, or Slack) only when a new matching gig appears.
Stop refreshing Upwork/Remotive/LinkedIn every 20 minutes. Point GigWatch at the feeds you care about, tell it what you do, and let it ping you when something relevant lands.
$ gigwatch scan
scanned 17 job(s) from 1 source(s); 4 match filter; 2 new
GigWatch: 2 new matching gig(s)
1. Senior Python Backend Engineer
company: Acme Digital
salary: $120k-$150k
where: Remote (Worldwide)
matched: python, backend
score: 9.0
https://remotive.com/remote-jobs/...
Why this exists
Freelancers lose real money to latency — the best gigs get filled in the first hours. Existing monitors (Distill, PageCrawl, Apify's Upwork monitor) are hosted SaaS that scrape your sessions and cost monthly. GigWatch is:
- Self-hosted & private — your skills, your feeds, your machine. No account, no session scraping, no data leaving your box.
- Free & open (MIT) — the core is a small, readable Python CLI.
- Portable — run it on a laptop, a $5 VPS, or in a cron job.
Features
- Multiple feed sources — Remotive, We Work Remotely, and RemoteOK (built-in, no auth), any RSS/Atom feed, or any JSON endpoint returning a list of job objects.
- Output formats —
scanandlisttake--format text|markdown|json(a Markdown table or a JSON array of job objects for piping elsewhere). - Skill-based filtering — keyword matching (any/all), category and location filters, exclude-list, and a relevance score (title hits weigh more than body hits).
- Dedupe by state — a local JSON state file tracks what you've already seen, so you're only ever alerted on new matches. State auto-prunes.
- Alerts — console (default), SMTP email, or Slack (webhook or chat API). Secrets come from environment variables, never the config file.
- Zero dependencies — pure Python standard library. If you can run
python3, you can run GigWatch.
Quick start
No install required — it's stdlib-only:
# 1. Get the code
git clone https://github.com/earnnova7/gigwatch
cd gigwatch
# 2. Create a starter config (or copy config.example.json to config.json)
python3 -m gigwatch init
# 3. Edit config.json: put YOUR skills in filters.keywords
# e.g. ["python", "backend", "api", "django"]
# 4. See what would match right now (dry run, no state touched)
python3 -m gigwatch list
# 5. Do a real scan: alerts on new matches, remembers them
python3 -m gigwatch scan
Or install it as a proper command:
pip install . # or: pipx install .
gigwatch init && gigwatch scan
Run it continuously
# Loop forever, re-scanning every poll_interval seconds (default 15 min):
gigwatch watch
# Or use cron on a VPS (once an hour):
0 * * * * cd /opt/gigwatch && /usr/bin/python3 -m gigwatch scan
Alerts
Console is on by default. To also get email/Slack, fill in the alerts
section of config.json and set the env vars it references:
export GIGWATCH_EMAIL_TO=you@yourdomain.com
export GIGWATCH_SMTP_USER=...
export GIGWATCH_SMTP_PASS=...
export GIGWATCH_SLACK_WEBHOOK=https://hooks.slack.com/services/...
The ${VAR} placeholders in the config are expanded from the environment at
load time, so secrets never live in the file (and the file is safe to commit
if you want).
Configuration
See config.example.json for a fully annotated
example. The top-level keys:
| Key | Meaning |
|---|---|
sources |
List of feeds to watch. {"type":"remotive"}, {"type":"wwr"}, {"type":"remoteok"}, {"type":"rss","url":...}, or {"type":"json","url":...}. |
filters.keywords |
Your skills. A job matches if it contains any of these (or all, with require_all_keywords). |
filters.categories / filters.locations |
Optional extra filters (empty = match anything). |
filters.exclude_keywords |
Words that disqualify a job (e.g. "intern", "junior"). |
filters.min_score |
Relevance floor. Title hits = 3 pts, body hits = 1 pt per keyword. |
alerts |
console, email, slack (see above) and max_per_alert. |
state_file |
Where seen-jobs are remembered (default gigwatch-state.json). |
poll_interval |
Seconds between scans in watch mode (default 900). |
Adding your own JSON source
Any endpoint that returns a JSON array of objects works. Each object should
have at least title and url; company/company_name, category,
location/country, salary, tags, and description are picked up if
present. Wrap in {"jobs":[...]}, {"data":[...]}, {"results":[...]}, or
{"items":[...]} and it still works.
Commands
| Command | What it does |
|---|---|
gigwatch init |
Write a starter config.json. |
gigwatch list |
Dry run — fetch + filter + print matches. Does not touch state. |
gigwatch scan |
Fetch, filter, alert on new matches, and record them as seen. |
gigwatch watch |
Loop scan every poll_interval seconds. |
gigwatch reset |
Clear the seen-state (next scan alerts on everything that matches). |
Useful flags: --config PATH (default config.json), -v/--verbose,
--max-age-days N (state pruning; 0 keeps everything), and
--format text|markdown|json on scan/list.
How it works
sources ──fetch──> [Job, Job, ...]
│
filter_jobs() (keywords / category / location / score)
│
[ScoredJob, ...]
│
compare against state file
│
┌──────┴──────┐
new jobs already seen
│ │
alert (console/ drop silently
email/slack)
│
mark seen in state file ──> gigwatch-state.json
The state file is plain JSON ({job_id: first_seen_utc}) so you can inspect
it, back it up, or move it between machines.
Roadmap / ideas
- More built-in sources (Hacker News "Who is hiring", LinkedIn via RSS, Upwork via a user-supplied export).
- AI ranking: summarize each match and rank by fit to a profile you write.
- Draft proposals / cover letters per match.
- A tiny hosted tier (the natural monetization path — see below).
Monetization
The core is free and MIT-licensed. The obvious paid tier is a hosted GigWatch: we run the scanner on our infra, you get email/Slack alerts without running anything, plus AI-ranked matches and proposal drafts. That's the plan — the open-source CLI is both the product's engine and the marketing.
License
MIT — see LICENSE.
Contributing
Issues and PRs welcome. The code is deliberately small and stdlib-only;
keep it that way. Run pytest (unit) and pytest -m live (hits the real
Remotive API) before sending a PR.
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file gigwatch-0.1.0.tar.gz.
File metadata
- Download URL: gigwatch-0.1.0.tar.gz
- Upload date:
- Size: 23.9 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via:
twine/7.0.0 CPython/3.12.14
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
92b23c6cde4dd85a2b4c320b39f6c9bda27a1d7e2182d0eec6127894ce1e8a9b
|
|
| MD5 |
eab294ccb58e9e01fc429ba919de42fa
|
|
| BLAKE2b-256 |
dd9a15167412c86884c9e378849981fca6717ea0af18ebb1c5b3f1cf219816f7
|
File details
Details for the file gigwatch-0.1.0-py3-none-any.whl.
File metadata
- Download URL: gigwatch-0.1.0-py3-none-any.whl
- Upload date:
- Size: 19.2 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via:
twine/7.0.0 CPython/3.12.14
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
1e7060d49e365355d2e3f923d60c508ead1ba78f91a7e20431e9f177429f479b
|
|
| MD5 |
ed3eeb3e1a610bef7e0479fa9add21e4
|
|
| BLAKE2b-256 |
760f25d1b39cc2439eaf78897cc6e1c9d63ecfcf40a14ae64a2486ccef0f6dad
|