❤️ Fredy - [F]ind [R]eal [E]state [D]amn Eas[y] - Fredy keeps searching for new apartments, houses, and flats in Germany on platforms like ImmoScout24, Immowelt
❤️ Fredy - [F]ind [R]eal [E]state [D]amn Eas[y] - Fredy keeps searching for new apartments, houses, and flats in Germany on platforms like ImmoScout24, Immowelt
Website | Demo | Quick Start | Docs
Fredy watches 24 real estate portals across for you (e.g. Immoscout, Kleinanzeigen etc), drops duplicates across platforms, and notifies you via Slack, Telegram, Email, ntfy, Discord and more the moment a new listing appears. Searches are managed from a Web UI, and you never see the same listing twice.
On top of the listing itself, Fredy answers the three questions a portal will not:
| Fredy Maps View | Dashboard | Found Listings |
|---|---|---|
docker run -d --name fredy \
-v fredy_conf:/conf \
-v fredy_db:/db \
-p 9998:9998 \
ghcr.io/orangecoding/fredy:master Open http://localhost:9998 and sign in with admin / admin.
[!NOTE] No configuration file is needed to start. Fredy creates
/conf/config.jsonon first run if it is missing. That file only holds the database path, everything else is configured in the Web UI and stored in the database. Documents you upload live in the database too, so the/dbvolume above is all you need to keep them, and every backup already contains them.
:master follows the master branch; pin a release with its version tag instead, e.g.
ghcr.io/orangecoding/fredy:28.0.0. Images are built for linux/amd64 and linux/arm64. Logs:
docker logs fredy -f.
There is also a pre-release channel following the develop branch,
ghcr.io/orangecoding/fredy-pre-release:latest. It is built from the same pipeline (lint, format
check and the offline test suite all have to pass first), but the changes in it have not been through
master yet. Use it to try upcoming features or to verify a fix, not for an instance you rely on.
Requires Node.js 22.22.0 or higher.
yarn
yarn run build:frontend # builds the Web UI into ui/public
yarn run start:backend # serves the UI and the API on port 9998Fredy is in the Unraid community store.
willhaben, Flatfox, idealista, Subito and [16 more](doc/providers.md)
Kleinanzeigen reaches you once, matched on living space, rooms and location rather than on the
headline, no two portals write that the same way
with your verdict always outranking Fredy's
for buying
or on foot, plus a filter to match, and the transport network with live departures on the map
expensive are facts rather than a feeling
the portal taking the ad down. A listing with documents is never cleaned up automatically
**ImmoScout Mobile API**| Concept | What it is |
|---|---|
| Provider | A real-estate platform. You paste a search URL from the portal into Fredy, sorted by date. |
| Adapter | A kind of connection Fredy can send through (Slack, Telegram, Email, ntfy, Discord ...). You never configure one on its own. |
| Channel | One filled-in adapter, e.g. "Telegram → family chat", saved once under Settings → Notification channels and reused in as many jobs as you like. |
| Job | Providers + channels: "search ImmoScout24 and Immowelt, send to Slack and Telegram". Runs at the interval set under Administration → Execution. |
A job can hold as many channels as you want, including several of the same type, and every new listing goes out through all of them at once. Rotating a token means editing one channel instead of every job that used it. Channels belong to whoever created them; an admin can share one with all users or with admins only, which lets others send through it without ever revealing its credentials. A channel still used by a job cannot be deleted.
…| Topic | What is in there |
|---|---|
| Providers & scraping | All 24 providers, the Immoscout / idealista / Casa.it specifics, and residential proxies for when a VPS gets blocked |
| Scam detection | The signals, their weights, the languages, and how to overrule Fredy |
| Financing calculator | Rent and Annuitätendarlehen, Kaufnebenkosten, Restschuld, the 35 % rule |
| Travel time & public transport | Addresses and place types, estimated vs exact, route drawing, departure boards, operator settings |
| MCP server | Connecting Claude, ChatGPT or a local LLM to your listings |
| Reverse proxy sign-in | Forward auth with Authelia, Authentik, oauth2-proxy, Traefik, Pangolin |
| Debug bundles | Capturing logs for a bug report |
| Development | Dev mode, tests, fixtures, adding a language |
| Contributing | Writing a provider or a notification adapter |
Since V20, Fredy ships a built-in MCP Server, so you can connect it to Claude, ChatGPT or a local model (LM Studio) and query your real estate data in natural language. A local LLM can even enrich existing listings by checking them online. Setup: MCP Readme.
To connect Claude.ai or ChatGPT over OAuth, set Fredy's baseUrl to its public HTTPS URL and add
<baseUrl>/api/mcp as a custom MCP server. Fredy advertises OAuth discovery metadata, dynamically
registers the client, and asks you to sign in and approve read access. Access tokens expire after one
hour and refresh automatically; existing MCP tokens keep working for local clients. Connected apps
are listed under Settings → Connections, where access can be revoked at any time.
Fredy is completely free (and will always remain free). However, it would be a huge help if you would
allow me to collect some analytical data. Before you freak out, let me explain: if you agree, Fredy
sends a ping every 6 hours to my internal tracking project (will be open sourced soon). The data
includes which notification adapters and providers are in use (the type only, for example slack,
never your channels, their names or their credentials), OS, architecture, Node version and language.
It is entirely anonymous and helps me understand which adapters and providers matter most.
Thanks
I build and maintain Fredy in my free time. If it saves you some, consider chipping in ❤️
Fredy is backed by the JetBrains Open Source Support Program.
Thanks to everyone who has contributed!
Start with the Contributing Guide; it also covers where AI-assisted contributions help, and where they do not.
Timetables, journey planning and travel times come from Transitous, a community-run MOTIS instance. It is free, needs no API key, and is maintained by volunteers, so please be considerate with the load you put on it and read their usage policy before pointing a large instance at it. Street and map data come from OpenStreetMap contributors.
Every listing with coordinates links out to Lagecheck, which rates the address on noise, air quality, green space and flood risk. Fredy only builds the link and stores nothing from it; the underlying data is by geosci.de.
Apache-2.0 with two additional conditions:
No open issues yet, or sync has not completed.