5 apps Internet
Deadair screenshot thumbnail

Deadair

Somewhere in your house, a presenter is introducing the next record, and that presenter is a language model running on your own server. Deadair builds you a real radio station rather than another playlist: it picks records from your Navidrome, Jellyfin, Emby, or Plex library, or from Spotify, YouTube Music, Pandora, and Apple Music, writes what the host says between songs, speaks it in that host's own voice, and broadcasts the result as one shared live stream over Icecast, with no skip button and the same show for every listener. From the console you steer it in plain sentences: tell it "rap like Snoop Dogg" and the next hours programme themselves to that brief, or ask why the record on air was chosen and get an answer. The forward lineup runs several hours deep, visible and editable, and nothing reaches air until its audio is already on the machine, so the stream never stutters waiting on a download. Words and voice are separate choices, swapped live in Settings: break-writing can run on a hosted model while a local Kokoro or Chatterbox voice reads it, and a station with no model at all still talks. Twenty-seven bundled plugins cover music sources, metadata, news, weather, and speech, and third-party plugins install from the console. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Deploy
Whoogle screenshot thumbnail

Whoogle

Google's search results without Google's surveillance: Whoogle is a self-hosted proxy that strips the tracking and keeps the results. Your query goes from browser to your Whoogle instance, which fetches results from Google with a randomly generated User Agent and strips everything hostile before returning them: no ads or sponsored content, no third-party JavaScript or cookies, no AMP links, no URL tracking tags like utm_source, no referrer header - and Google sees your server's IP, never yours. Unlike metasearch engines that blend sources, Whoogle proxies Google exclusively, so result quality is exactly what you'd get logged out and incognito, minus the noise. A lightweight Flask app configured entirely through environment variables, it supports DuckDuckGo-style bang shortcuts, autocomplete suggestions, safe search, per-country and per-language filtering, site blocklists, and automatic rewriting of social links to privacy front-ends like Nitter and Invidious. Privacy hardening goes further: built-in Tor routing makes Google see an exit node instead of your server, HTTP/SOCKS proxy support covers other setups, and POST-based queries keep search terms out of logs. Light, dark, and fully custom CSS themes plus browser search-engine registration make it a drop-in default on desktop and mobile. Stateless, tiny, and trivial to run.

Deploy
Eclipse Ditto screenshot thumbnail

Eclipse Ditto

Every physical device on your network gets a living digital counterpart in Eclipse Ditto: a Thing whose Features hold its current state, desired state, and properties, readable and writable through APIs even while the device itself is offline. Your application talks to the twin over a REST-like HTTP API for CRUD and search, over WebSocket for real-time bidirectional streams, or over Server-Sent Events for change notifications, and Ditto routes commands down the live channel to the actual device when it is connected. Devices and backends connect through managed Connections to MQTT, AMQP 1.0 and 0.9.1, Apache Kafka, and HTTP endpoints, with payload mapping that translates between device formats and Ditto Protocol JSON. Fine-grained Policies decide per subject and resource who may read a temperature, change a setpoint, or receive an event, including namespace-scoped entries and partial change notifications that only reveal fields a subscriber may see. Search across millions of twins uses an RQL query language with custom MongoDB indexes, and Web of Things integration generates Thing Descriptions scoped to each requester's permissions. The bundled Explorer UI lets operators browse Things, inspect Features, and time-travel a twin's state to any past revision or timestamp to see exactly what changed and when. OpenID Connect and basic authentication protect the gateway, and Prometheus metrics expose live entity counts per namespace. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. EPL-2.0 licensed.

Deploy
Lingva Translate screenshot thumbnail

Lingva Translate

What Nitter was to Twitter and Invidious is to YouTube, Lingva Translate is to Google Translate: a privacy front-end delivering the service's full capability while cutting Google out of the loop between you and your text. Built on Next.js with TypeScript and Chakra UI, it uses the purpose-built Lingva Scraper to fetch translations from Google Translate without your browser ever touching a Google-related service - no cookies, no tracking, no account, while retaining what makes Google Translate hard to give up: 100+ languages with the translation quality of Google's production models, unlike offline engines that trade privacy for accuracy. The clean interface covers automatic source-language detection, text-to-speech audio playback for pronunciations, definitions and examples, and light/dark themes. For developers, every instance doubles as a translation API: a RESTful endpoint at /api/v1/:source/:target/:query returns JSON translations, an audio endpoint serves TTS buffers, and a full GraphQL API at /api/graphql exposes translations, audio, and language lists for richer integrations - all unmetered on your own instance. Deployment is a single stateless container with one environment variable for the site domain; defaults for theme and language pair are configurable. GPL-licensed, and popular as the translation backend for privacy-respecting apps.

Deploy
SearXNG screenshot thumbnail

SearXNG

Up to 280 search services - Google, Bing, DuckDuckGo, Brave, Qwant, Startpage - aggregated without tracking or profiling: SearXNG is a privacy-respecting metasearch engine (AGPL-3.0, successor to Searx). Your instance queries the upstream engines on your behalf: your IP address, cookies, and search history never reach them, tracker parameters are stripped from result URLs, and an optional image proxy fetches thumbnails server-side so result pages leak nothing. It can even route outbound queries through Tor for full anonymity. Search is organized into categories - general, images, videos, news, maps, music, IT, science, files - with bang shortcuts for targeting specific engines, and every source can be enabled, disabled, or weighted per category in settings.yml. A plugin system adds calculators, hash tools, tracker removal, and unit conversions inline, and preferences (themes, safe search, languages, engine selection) persist in cookies rather than server-side accounts. The real argument for running your own instance rather than trusting a public one is control: you decide the logging policy (none), the engine mix, rate limiting, and who gets access - making it the default search backend for browsers, families, and teams that want Google-quality results without the profile.

Deploy