This is a read-only mirror. Postulo is developed at source.tiagoagueda.com/postulo/postulo. Please open issues, suggestions and pull requests there.
Self-hosted job application manager, from the applicant's side of the table.
Every applicant tracking system is built for the company doing the hiring. Postulo is built for the person applying: your applications, your CVs, your cover letters, your data, on your server.
From the Latin postulō — "I apply for". First person, deliberately.
Status: pre-1.0. Usable and used, but not battle-tested: it has recorded real applications, by one person, for weeks rather than years. Releasing here is a deliberate act rather than something that happens on a schedule, so
mainmay be ahead of the last tag — the changelog says by how much.
![]() |
![]() |
![]() |
![]() |
These pictures are of a demo instance filled with a fictional job search, and are retaken by
scripts/screenshots.py rather than by hand. There is no public demo to try: it would be
something to host, reset and secure, and nobody's data belongs on it. Run your own with
manage.py seed_demo <email>; the wiki
shows every page.
No feature of Postulo is, or ever will be, behind a paywall. People looking for work are, more often than not, people who cannot afford to pay for the tools to find it. Everything this software does is available in full to everyone who runs it: no paid tier, no "pro" edition, no licence key, no feature that unlocks later. The licence guarantees that for the code; this paragraph guarantees it for the project's intentions.
Voluntary support is this project's only income. Not its main one — its only one. There is no company behind Postulo, no funding round, no paid tier waiting to appear once enough people depend on it. One person writes it, and what it costs to keep going comes from people who decided it was worth something.
Nothing is owed. Nothing is unlocked by it, now or later — that is what the paragraph above promises and it is not negotiable. And nothing a person is shown while using Postulo to look for work will ever ask for money: no banner in the interface, no prompt, no reminder on the dashboard. The one place inside the application that mentions support at all is Server settings → Overview, the page addressed to whoever runs the instance, where it is said once and in these words. Otherwise this is where the question is put, which is why it is put plainly here.
If money is the wrong thing to give — and for a lot of people looking for work, it is — then a bug report, a translation reviewed by somebody who actually speaks the language, or telling one person who needs this that it exists are all worth as much.
FUNDING.md is the long version: what support pays for, what it will never buy, and why money does not move an issue up the list.
Postulo holds the most personal documents a person has while looking for work, and it is built as if that were the only thing that mattered. A CV carries a home address, a phone number and a full employment history; a timeline says who has and has not replied. So the code and the data are kept as secure as the project knows how to make them: every record is owned and every query is scoped -- No one sees another person's data unless that person granted it -- explicitly, for a stated scope, revocably, and visibly to them at any time. Superusers can see and change any company, contact or listing, including private ones, but never anyone's notes, applications or documents. Files are never served without a permission check, the browser is held to a strict content security policy, nothing is fetched from the network without a deliberate decision, and the test suite includes security tests — ownership sweeps, policy checks, the things an attacker would try — that fail the build. Dependencies are checked for known vulnerabilities on every run and on a schedule, so a fresh disclosure is noticed without anyone having to remember to look. A security report is handled before any feature is; see SECURITY.md.
Postulo is meant to be usable by everyone, at its fullest, including people with disabilities. Looking for work is hard enough without the tool getting in the way. So the interface is server-rendered HTML that works with scripts off, every control can be reached and operated from the keyboard, images and icons carry names or are marked as decorative, colour never carries a meaning on its own, changes on the page are announced to screen readers, and the pages are checked against the accessibility guidelines (WCAG 2.2, level AA) as part of the browser tests rather than as an afterthought. When a feature cannot be made to work for someone, that is a bug, and it is filed as one. ACCESSIBILITY.md is the accessibility statement: what is checked and how, what is known not to work yet, and how to report a barrier.
- Track applications end to end — from a posting you spotted to an offer, with an append-only timeline that records what actually happened and when.
- Manage CVs as structured, reusable career content: write an experience once, then compose targeted CV variants from it without copy-pasting between documents.
- Manage cover letters from reusable templates with per-application placeholders.
- Keep what you actually sent. Every document is snapshotted to PDF at send time, so six months later you know exactly which version that employer read.
- Bring your own files. Externally authored PDFs and DOCX files are stored and versioned alongside generated ones.
- Capture postings from a URL — Postulo reads the page and asks you to confirm it before recording anything. Extensible through plugins, and reachable through a small API for scripts and browser extensions.
- See what is working — how far applications get, what share are answered, how long employers take, and which sources convert. Read from the timeline, so an interview that ended in a rejection still counts as an interview.
- Take everything with you — one zip holding a readable JSON document of every record and every file, which imports back.
- Your data is yours. Full JSON + media export, always one command away.
- No telemetry. Outbound requests only for the features listed in the wiki's Hardening page.
- Private by default. Uploaded documents are never publicly served.
- Secure by obligation. Ownership-scoped queries, permission-checked files, a strict content security policy, security tests in the suite, and dependency vulnerability checks in CI. See SECURITY.md.
- Accessible to everyone. Keyboard-operable, screen-reader-announced, usable with scripts off, and checked against WCAG 2.2 AA in the browser tests.
- Boring, durable stack. Django, SQLite or PostgreSQL, server-rendered HTML.
- Modular by design. Anything that could reasonably vary — where a posting is read from, how you are told about things, how a PDF is produced — sits behind an interface that a separately installed package can implement. Postulo's own implementations are plugins that happen to ship in the box. See Writing a plugin.
Much of Postulo is written with an AI assistant, and contributions made the same way are welcome. The rule is simple: a person proposes the change, has read it, can explain it, and answers for it. The assistant is a tool; the contributor is accountable. See CONTRIBUTING.md and AGENTS.md.
The interface is a setting per person; the documentation is in English, and the table below says what Postulo is in each language so nobody has to guess. Translations are made, corrected and reviewed at translate.tiagoagueda.com (docs/TRANSLATING.md), where the live progress of every language is.
Postulo speaks 57 languages, each named here as its speakers write it.
- The wiki — installing, configuring and using Postulo. Its pages are their own repository, postulo.wiki.
- Implementation plan — architecture, data model, and milestones
- Writing a plugin — the plugin contract, and every name a plugin may import
git clone https://source.tiagoagueda.com/postulo/postulo.git
cd postulo
git checkout vX.Y.Z # the latest release tag, see the releases page
cp .env.example .env # set POSTULO_SECRET_KEY and POSTULO_ALLOWED_HOSTS
docker compose -f docker/compose.yml up -d
docker compose -f docker/compose.yml exec postulo python manage.py createsuperuserThat pulls the published image. To build it from the checkout instead, add the build
override: docker compose -f docker/compose.yml -f docker/compose.build.yml up -d --build.
Then put a reverse proxy in front of it for TLS. See Installing Postulo for the full instructions, including installing without a container.
Requires Python 3.12.4 or newer and uv.
uv sync # install dependencies
cp .env.example .env # configure (a dev SECRET_KEY is generated if unset)
uv run manage.py migrate
uv run manage.py createsuperuser
uv run manage.py runserverPDF export uses WeasyPrint, which is installed with Postulo. On Linux it needs Pango:
sudo apt install libpango-1.0-0 libpangoft2-1.0-0 libharfbuzz-subset0 # Debian and UbuntuThose libraries are awkward to obtain on Windows, so a fallback renderer exists there:
uv sync --extra chromium
uv run playwright install chromiumPostulo uses whichever works, preferring WeasyPrint. Export is optional: tracking applications and writing letters need no renderer at all.
Node is not required to run Postulo: the compiled stylesheet and the page script the browser is served are committed. It is only needed to change the CSS, to add a Tailwind class a template did not use before, or to change the page script, in which case:
npm install
npm run watch:css # or `npm run build:css` for a one-off
npm run build:js # after a change to assets/js/app.jsTo see it with data rather than an empty screen, fill an account with a fictional search — thirty applications over six months, with documents:
uv run manage.py seed_demo you@example.orgTests and linting:
uv run pytest
uv run ruff check .
uv run ruff format .Copyright (C) 2026 Postulo contributors. AGPL-3.0-or-later. If you run a modified Postulo as a network service, your users are entitled to its source.
Some of what ships in the repository is somebody else's work under a licence of its own: the Lucide icons, the flag-icons country flags, Tailwind CSS and basecoat-css compiled into the stylesheet, htmx and zxcvbn served as scripts. All of it is copied into the repository, so nothing is fetched from anybody else's server at runtime, and each carries its notice beside it. THIRD-PARTY.md is the register.
The name and the logo are not covered by that licence. TRADEMARKS.md
says what you may do without asking — which is nearly everything, including naming a plugin
postulo-something and calling your instance whatever you like — and the one case where a
fork should use another name. It also names the marks belonging to other people that appear
here, and none of their owners is involved with this project.
Developed on Forgejo and mirrored to GitHub. Issues and pull requests belong on the Forgejo repository; the GitHub copy is a read-only mirror. A bug or a request has a form there (see CONTRIBUTING.md); a security problem does not go in an issue, see SECURITY.md. Everyone taking part is held to the code of conduct.






