obacht documentation

obacht is a parental control system for families: limits, not surveillance. Parents set daily time, bedtimes and app rules once; every device of a child follows them, also offline, and the child always sees what their parents can see.

These pages are also published on the obacht website. They are licensed under CC BY 4.0: reuse them freely, with credit to the obacht project.

Pages

• What works where: every feature on every kind of device, how far each one is, and what is planned.
• Running obacht at home: the server with NixOS or Kubernetes, Android phones, the DNS filter for consoles and TVs, UniFi.
• Ways to sign in: obacht on its own, with a login provider, with a policy engine, or with an account portal.
• Permissions per parent: optionally let Keycloak (or another AuthZEN decision point) decide which parent may see or change what, per child.
• Home Assistant: screen time in Home Assistant, pauses and extra time from automations.
• The media agreement: the family's rules written down together, shown to the child and quoted when an app is blocked.
• A login for your child: children see their own rules and propose changes, parents accept or decline.
• Where your child is: optionally see where your child's phone is, when you ask, its last known position, or with a history of a few days.
• Which websites your child visits: optionally see the sites (not pages or searches) your child's devices visit.
• AI apps and chatbots: how obacht limits AI assistants without reading them.
• Platform limitations: what Google, Apple and others don't let obacht do, and the workarounds.

The API is documented by the server itself, as OpenAPI at /api/v1/openapi.json.

This page is part of obacht's documentation, licensed under CC BY 4.0. Source on GitHub · CC BY 4.0 · Version: main (2ab2740)