Getting started
Matched queue
Customize ▾
| Title | Company | Location | Track | Exp | Comp | Security | Link |
|---|---|---|---|---|---|---|---|
| Loading… | |||||||
Scan activity — jobs discovered per recent cycle
Intake — new jobs scraped per day (14d)
Job analysis coverage — shared details for active postings
Matches per account — delivered to each Discover user
AI analysis queue — analysis task status
Jobs by track — active US corpus
Jobs by source — top crawlers
Top companies by live jobs
ATS distribution — registry
Registry health — board reachability
Discovery ROI — jobs yielded per source
| Title | Company | Location | Comp | Exp | Security | Posted | Source | AI | Flags | Last seen | Apply |
|---|
| Company | ATS | Domain | Careers | Health | Prio | Enabled | Jobs |
|---|
▚ Active Workers
▚ In-Flight Leases & Tasks
| Task ID | Status | Worker | Companies | Attempts | Lease Expires |
|---|
▚ Crawler Performance & Network
Daily Bandwidth History (Wire Transmitted / Saved)
Optimization Savings & Compression Breakdown
Per-ATS Efficiency Breakdown (Lifetime)
Company Crawl Cost Analysis
Discovery ROI (Candidates → Employers → Jobs)
Pipeline Health — versions · enrichment · inventory · repair · discovery
Settings · operator console
Admin-only tools for this Discover deployment. Per-account search settings live in My Search; this tab is for operating the shared system — snapshots, data export, and (in single-user mode) the global scanner gates.
Scanner filters · deterministic
data/filter_config.json
and apply on the next cycle (no restart).
Company registry export · admin
Download the current crawl registry (company list) as JSON. This is
admin-gated on the server; the token is sent once in an
Authorization: Bearer header — never in the URL — and is
not stored (it clears on reload).
Where does this token come from?
- A local admin token — set
REGISTRY_ADMIN_TOKENin the webui server’s environment (.env). Generate one with:python3 -c "import secrets; print(secrets.token_urlsafe(32))"
then paste that same value here. (Empty by default = disabled.) - A jobtrack.dev admin token — the bearer token of a
jobtrack.dev admin account; the server verifies it against
jobtrack.dev (
JOBTRACK_ADMIN_VERIFY_PATH).
Database backups · admin
Compressed snapshots of the jobs / registry database. Take one before any
risky change; the maintenance container also takes them on a schedule.
Backups are written on the server (data/backups/) and pruned
by retention — this only creates and lists them, it never deletes.
Resume → Job Search Profile
This is the only place you enter a resume: it is stored on your account and reused by the search assistant and per-job match scores. Paste it as plain text, Markdown, or LaTeX. The analyzer extracts deterministic facts (skills, certs, education, experience — each with evidence), proposes job-search profiles, and shows exactly how each would map onto the existing filters. Nothing changes until you review and explicitly Apply.
Saved search profiles
The active profile powers per-job match scores.
“Apply to filters” writes the profile's settings into the live filter config
(you'll see the exact diff). Fields you've edited by hand stay marked
manual and are never overwritten by a re-analyzed resume.