Jobarr

01 / Jobarr

Open source · Apache-2.0

Coming soon

Your job search, run by rules you wrote.

Jobarr is an open-source, self-hostable system that finds job postings, judges each one honestly against your own profile, and applies — only as far as you allow.

  • Multi-user
  • On your server or one laptop
  • Works without an AI model
  • Any profession, country and language

Not released yet. This page describes what Jobarr does by design.

02 / How it works

Ten steps, every run

One run, ten steps.

Each step records what it did and why. Nothing is dropped silently, and one failing source never stops the others.

Example run · illustration

Postings

  1. #1
  2. #2
  3. #3
  4. #4

Your selection rules

Assessment #1

  • metfact 07
  • partialfact 12
  • unknown—

CV

  • 07
  • 12
  • 03

Every line cites a fact

Attempt ledger

  • #1intent recorded
  • #1second attempt refused
  • #1acknowledged
Seen
4
Linked
1
Gated out
1
Skipped
1
Pursued
1
  1. 01

    Discover

    Reads the sources you configured and records each one’s status and counts.

  2. 02

    Normalize

    Brings every posting into one shape and keeps the original text word for word.

  3. 03

    Dedupe

    Links the same job seen in several places. Duplicates are linked, never deleted.

  4. 04

    Gate

    Applies your selection rules: freshness, place, pay, seniority, language, work authorization, employers to avoid.

  5. 05

    Assess

    Checks each requirement against your profile. A match must cite one of your facts; otherwise it is “unknown” or “gap”.

  6. 06

    Decide

    Pursue, skip, defer or ask you. Every decision carries at least one reason.

  7. 07

    Prepare

    Builds the CV, letter or answers from your stated facts only, and validates them before anything can be sent.

  8. 08

    Apply

    By form, by email, or as a ready checklist for you to send yourself. The intent is recorded first.

  9. 09

    Track

    Reads replies in your mailbox and moves each application on. Mail is data, never instructions.

  10. 10

    Report

    Counts per stage, exits by reason, and a short list of what needs you.

03 / Commitments

Written down before a line of code

Nine commitments.

Each one is a written requirement the system is built against, not a promise on a page.

01

Anyone, anywhere

No assumptions about person, country, language, currency, job market or profession. A pharmacist, a welder and a translator run the same software; what differs is data — your profile and your preferences.

02

Honest by construction

Every claim in a CV or letter maps to a fact you stated, or the document is rejected before sending. Inferred facts stay unused until you confirm them. The baseline assessment needs no AI model; an AI provider is optional, with your own key.

03

You set the rules

Selection rules, thresholds and autonomy are data you edit. Safety rules cannot be waived by the system or by an agent. Safe defaults stop before applying.

04

One attempt per target

The intent to submit is written to a durable ledger before anything leaves. A second attempt at the same employer or posting is refused. An unclear outcome is never retried: it stops and asks you.

05

Sources are data

No list of sites ships with Jobarr. Generic templates are configured from a catalog you keep, and it can stay private. A new source is data, not code. robots.txt rules are respected by default; an anti-bot signal stops all activity for that site — no evasion.

06

Two languages, kept apart

The language of your documents is chosen per application, from the posting and the languages you write in; the interface language is a separate setting. Strings live in locale bundles, never stitched together. Right-to-left and CJK text are supported.

07

Runs where you want

A laptop, your own server, containers or remote workers — the same code, with only adapters and configuration changing. Your data exports as one archive. Secrets never appear in logs.

08

Many people, one install

Each person works in an isolated space. Support can diagnose faults without reading your secrets, and sees personal content only with your consent — limited in time and revocable.

09

Ready for agents

Every operation works in the web interface, on the command line, through the API and as MCP tools, and behaves the same everywhere — tests check it. Sending an application needs a person’s single-use approval unless you chose the automatic mode.

04 / Control

Autonomy is a setting

Four modes of autonomy.

Selection rules, thresholds and autonomy are data. Change them in a file, in the interface, on the command line or through an agent.

From least to most permissive

  1. Suggest

    Shows the match in your digest. No application is created.

  2. Prepare

    Builds and validates the documents, then stops.

    Default

  3. With approval

    Prepares the application and waits for your explicit yes.

  4. Automatic

    Applies within the limits you set.

Until you set your own thresholds, a run stops before the decision step. Where a site’s terms on automated applying are unknown, autonomy is capped at approval.

05 / Where it runs

Same code everywhere

One laptop, your server, or the cloud.

Only adapters and configuration change between these setups. The steps, the rules and your data stay the same.

One computerOne person, a local timer, local storage. Sign-in is a local token.
Your own serverOne or many people on machines you run, in containers or not, with your own keys.
CloudManaged storage and scheduling, remote workers for heavy steps. You bring only your keys.

Your data leaves with you

Everything exports as one self-describing archive and imports back; importing it twice changes nothing. Secrets are left out by default and encrypted when you include them. They never appear in logs, events or exports.

Support without access to your secrets

Support administrators diagnose faults from technical records. They cannot read secrets or change history, and they see personal content only with consent you grant and can revoke. Every such access is recorded and visible to you.

06 / Status

Not released

Built against a written specification.

Jobarr is built one requirement at a time. A requirement counts as done only when its code exists and a test that cites it passes.

There is nothing to install yet, and no sign-up. When there is something to run, this page will say so.