Automation runs on its configured host; this page is a read-only Cloudflare Pages mirror of it. The page is rendered locally from machine-only data, pushed as a sanitized single-snapshot commit to a dedicated mirror repository, and then deployed by Cloudflare Pages Git integration. The sync state above is a fact about that checkout at the moment of the build, not about this page — how current the PAGE is is what the badge at the top of it measures.

The Application Center is the review-first lane for marketplaces without a supported submit API. Freelancer.com may use its separate opt-in official API lane when configured; it remains capped, duplicate-safe, and globally pause-aware. Public counts never include proposal text, bid details, account identifiers, tokens, client messages, or raw errors.

Live = open when last scraped, counting freelance/contract engagements only. On the board sources it also excludes the AI-labeling gigs, which are listed on the AI labeling page and counted beside the platform name as “+N labeling” — with “(M shown)” added where that page’s language gate holds some of them back. Upwork is the exception: its open leads are not published as individual rows anywhere, so its labeling gigs stay counted inside its Live and are tagged “incl. N labeling” rather than subtracted (Upwork rows are not re-checked for closure: 860 of its 860 Live rows were last sighted over 7 days ago, median 114d, so verify a post is still open before bidding; board rows are kept for a few days after they stop appearing in the source’s feed, because many sources publish only a rolling newest-N page where absence means “scrolled off” rather than “closed” — the rows that have actually stopped appearing are tagged “unseen Nd”. A source whose crawl re-reaches fewer than half of its own open rows cannot support that number at all, and neither can one we have not managed to re-read for days — an outage freezes the crawl every row is compared against, so its leads would otherwise keep reporting as confirmed-present for as long as it lasts. Rows of either are tagged “freshness unknown” instead, which means we cannot vouch for them either way, not that they are fresh) · When = the earliest date we can prove, which is the posting date unless a recruiter re-activated the listing after we had already seen it — a bumped date is never shown as the posting date, and those rows are tagged “re-listed Nd” instead. A source that published no posting date at all reads “first seen Nd ago”: that is our discovery date, an upper bound on the posting’s age and not the age itself · Drafted = proposal written & priced, which INCLUDES drafts whose posting date was never confirmed (the “date unproven” count above) — those are deliberately not send-ready, because only the attended browser can prove a posting is still open and a bid on a closed posting still costs Connects · Submitted = confirmed recorded outcomes · Tracked = all listings ever seen. Most Upwork drafts are NOT send-ready — only a minority are clean & fresh (see the “clean & fresh” count above); the rest carry rewrite flags. Columns overlap. Upwork and Freelancer.com each have separate opt-in, quality-gated, capped submission lanes. All other platforms remain review-first manual or external applications.

Discovery → scoring → drafting run automatically. Most applications remain review-first; the separately armed Upwork and Freelancer.com lanes may submit only after their quality, identity, pause, duplicate, and spend-cap gates pass. Below are real listings, scored and (where shown) drafted — proposal text, client messages and pricing notes are intentionally not published here. Historical submissions live on the Apply tab.