gitwtfhub

wtf is the-one?

killerfrost598/the-one — explained in plain English

Analysis updated 2026-05-18

0KotlinAudience · developerComplexity · 5/5Setup · hard

TL;DR

A self hosted, Tailscale-only system that lets you lock down your own devices with rules that are easy to strengthen instantly but slow and deliberate to weaken.

Mindmap

mindmap
  root((the-one))
    What it does
      Self hosted lock system
      Asymmetric change delay
      Multi device policy
    Tech stack
      Kotlin Android agent
      Python plane and Linux agent
      Tailscale networking
    Use cases
      Block distracting apps
      Personal commitment device
      Self imposed restrictions
    Audience
      Self hosters
      Privacy focused users
      Developers

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

Self host a personal system that blocks distracting apps on your own phone or laptop.

REASON 2

Enforce rules that only you, via a private network, can loosen after a cooldown period.

REASON 3

Run a Linux agent that blocks hosts and kills processes according to a shared policy.

REASON 4

Deploy a Device Owner Android agent for a hard, hard-to-remove app lock.

What's in the stack?

KotlinPythonFastAPIPostgresDockerTailscale

How it stacks up

killerfrost598/the-oneandroosio/thortuneazcomp2000/battery-sentinel
Stars000
LanguageKotlinKotlinKotlin
Setup difficultyhardeasymoderate
Complexity5/52/52/5
Audiencedevelopergeneraldeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · hard Time to first run · 1h+

Requires Docker and Tailscale for the plane, the Android agent can require a factory reset if misused, so test on a spare device first.

Wtf does this do

the-one is a self hosted personal commitment system that lets someone restrict their own devices in a way they cannot easily undo on the spot. It is built around a central control plane, hosted by the user themselves and reachable only over a private Tailscale network, which holds the rules for every enrolled device. Each device runs an agent that pulls its rules from the plane, applies them locally, enforces them, and reports back its status. The key idea is an asymmetry between making rules stricter and making them looser. Strengthening a rule takes effect immediately, but weakening or removing one is delayed by a default of 24 hours and must be done from the central plane, never from the restricted device itself. The README is explicit that this is personal infrastructure for one person's own use, not a parental control product or commercial device management tool, and it is upfront that different platforms offer very different levels of real enforcement. The project has four main parts sharing one shared policy format: a schema package defining the rules and how strength is compared, a FastAPI and Postgres control plane with a web interface for creating rules, a Linux agent built in Python that can block hosts and stop processes, and an Android agent that provisions itself as a Device Owner using Android's kiosk style Lock Task mode. The README repeatedly and strongly warns that the Android agent is difficult to remove: a release build has no in app way out, and if a user gets locked out and cannot reach the device over adb, the only recovery is a full factory reset that erases everything. It urges practicing on a spare device or emulator with a debug build first. Setting up the control plane requires Docker and Tailscale, copying an example environment file, filling in a database password and Tailscale IP address, and running docker compose up. The plane only listens on the private Tailscale address, never on the public internet, and pairing a new device requires the operator to approve a one time pairing code before the device receives any access token. The project is explicitly marked as alpha status, incomplete, and unsupported.

Yoink these prompts

Prompt 1
Walk me through setting up the control plane with Docker Compose and Tailscale for this project.
Prompt 2
Explain the asymmetric change delay design principle and why weakening a rule is delayed.
Prompt 3
Before I install the Android agent, summarize the safety risks described in docs/SAFETY.md.
Prompt 4
Show me how the pairing flow works between a new agent device and the control plane.

Frequently asked questions

wtf is the-one?

A self hosted, Tailscale-only system that lets you lock down your own devices with rules that are easy to strengthen instantly but slow and deliberate to weaken.

What language is the-one written in?

Mainly Kotlin. The stack also includes Kotlin, Python, FastAPI.

How hard is the-one to set up?

Setup difficulty is rated hard, with roughly 1h+ to a first successful run.

Who is the-one for?

Mainly developer.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.