- Home
- Parental control apps
- OpenParental
OpenParental
What it is
OpenParental is free, open-source parental-control software for Android, designed around visible, consent-based supervision between parents and teenagers. A parent pairs a child’s device with a short code, and the device receives a scoped token. From the parent app, they can set app blocklists, daily limits for individual apps, schedules, or remotely lock or ping the device. The child app reports location periodically, daily app usage, newly installed apps, and tamper events to a dashboard or alert feed. Alerts can also cover a device going dark and unblock requests. The project describes optional live screen viewing after a setup-time MediaProjection grant. It says the child can disable the app, with bypass actions such as force-stopping intended to trigger a parent alert within minutes. The project excludes covert audio, camera, ambient recording, covert screen capture, storage of minors’ photos on its server, Device Owner, and device wipe. Families must self-host the backend; the child app is a sideloaded Android app, while the Flutter parent app has a Play Store track.
For and against
For
- Free and open source under the MIT license
- Offers app blocklists, daily limits, and schedules
- Reports usage, location, new apps, and tamper events
- Provides remote device locking and pinging
- Visible child app explains what it reports
Against
- Requires a self-hosted backend
- Child app is sideloaded
- Content filtering is not included
- Child can disable the app
The verdict
OpenParental combines practical app and schedule controls with visible reporting and consent-based supervision. Its self-hosted setup and sideloaded child app are important considerations for families.
Who it suits
It suits parents and teenagers seeking visible, consent-based Android supervision with app limits, schedules, and activity alerts. It also fits technically equipped households prepared to self-host the backend and sideload the child app.
Plans and prices
OpenParental
Open-source parental controls for Android · MIT licensed
Read 8 Oct 2026 · github.com
On the record
- Activity reports
- Yesgithub.com · read 22 Sep 2026
- Alerts
- Alerts cover tampering, a device going dark, new apps, and unblock requests.github.com · read 8 Oct 2026
- App blocking
- Yesgithub.com · read 22 Sep 2026
- App controls
- Parents can set app blocklists, per-app daily limits, and schedules.github.com · read 8 Oct 2026
- Apps
- The child app is a sideloaded Kotlin Android app and the parent app is Flutter, described as having a Play Store track.github.com · read 8 Oct 2026
- Architecture
- The repository describes a NestJS backend with PostgreSQL, Redis, and FCM, a Kotlin Android child app, and a Flutter parent app.github.com · read 8 Oct 2026
- Bypass behavior
- The project says the child can turn the app off, but bypasses such as disabling accessibility or force-stopping should trigger a parent alert within minutes.github.com · read 8 Oct 2026
- Bypass limitation
- The project says the child app can be disabled, but bypass actions are intended to trigger parent alerts within minutes.github.com · read 8 Oct 2026
- Consent
- The child app has a visible interface that explains what it does and shows what it reports.github.com · read 8 Oct 2026
- Content filtering
- The documented DNS content filter uses Android VpnService and says it does not inspect traffic or use a man-in-the-middle.github.com · read 8 Oct 2026
- Controls
- The parent can remotely lock or ping a device and configure app blocklists, per-app daily limits, and schedules.github.com · read 8 Oct 2026
- Deployment
- The README describes a self-hosted backend using Node 20+, Docker, PostgreSQL 16, and Redis 7.github.com · read 8 Oct 2026
- Device platforms
- androidgithub.com · read 22 Sep 2026
- Distribution
- The child app is described as a sideloaded APK, while the parent app is described as being on a Play Store track.github.com · read 8 Oct 2026
- Integrations
- Firebase Cloud Messaging is an optional integration for push notifications; without Firebase, devices poll every 60 seconds.github.com · read 8 Oct 2026
- License
- The repository identifies the project as MIT licensed and credits Suhaib, © 2026.github.com · read 8 Oct 2026
- License and maker
- The repository lists an MIT license and credits Suhaib with copyright in 2026.github.com · read 8 Oct 2026
- Live screen
- The README describes live screen viewing using a setup-time MediaProjection grant and JPEG frames sent over Socket.IO.github.com · read 8 Oct 2026
The review
OpenParental is open-source parental-control software for Android, built around visible, consent-based supervision. It is best suited to families willing to run their own server and install a child app outside the usual store flow. Its useful scheduling and reporting tools come without a software charge, but setup and the child app’s ability to be disabled are meaningful trade-offs.
Overview
A parent pairs a device by creating a short code for the child app to claim; the device then receives a scoped token. The child app explains its role and what it reports, making OpenParental a more suitable choice for parents and teenagers who agree to supervision than for families seeking covert monitoring.
OpenParental is self-hosted rather than a managed service. Its architecture combines a NestJS backend with PostgreSQL and Redis, a Kotlin Android child app, and a Flutter parent app. The child app is distributed as a sideloaded APK, while the parent app is described as having a Play Store track. That arrangement offers control over deployment, but asks caregivers to handle server operation and APK installation.
Key features
Schedules and device controls
Parents can create app blocklists, set per-app daily limits, and apply schedules, then remotely lock or ping a device. These controls suit families setting specific app rules and routines; they do not amount to content filtering, which OpenParental does not provide.
Reports and alerts
The child app periodically reports location, per-app daily usage, newly installed apps, and tamper events to a dashboard or alert feed. Alerts cover tampering, a device going dark, new apps, and unblock requests. This gives parents visibility into usage and attempted interference, although it depends on the child app continuing to run.
Consent, privacy, and bypasses
The project excludes covert audio or camera use, ambient recording, covert screen capture, server-side storage of minors’ photos, Device Owner, and device wipe. It describes live screen viewing through a setup-time MediaProjection grant, with JPEG frames sent over Socket.IO. That capability is distinct from covert capture, but families should consider whether live viewing fits their consent expectations.
A child can disable the app; actions such as disabling accessibility or force-stopping it are intended to trigger parent alerts within minutes. This is a useful warning mechanism, not a guarantee that controls cannot be bypassed. Optional Firebase Cloud Messaging supports push notifications; without Firebase, devices poll every 60 seconds.
Pricing
OpenParental is free and open source under the MIT license. Its OpenParental plan costs nothing and is described as open-source parental controls for Android. There is no free trial because the software is already free. No paid tier is described, so the main cost is the time and technical work needed to deploy and maintain the self-hosted backend.
Platforms
The child app runs on Android. The parent app is built with Flutter and described as having a Play Store track; the backend is self-hosted. Setup calls for Node 20+ and Docker for the backend, JDK 17 and Android Studio for the child app, and Flutter 3.22+ for the parent app. This is a technical stack, not a turnkey installation, and families needing child-device controls on iOS or desktop should look elsewhere.
Who it's for
OpenParental fits technically capable families who want transparent supervision, Android app limits, schedules, and usage reporting without paying for a software subscription. Its consent-first approach also suits households where teenagers are included in the monitoring agreement. It is a poor fit for families that need content filtering, cross-platform child coverage, a managed cloud service, or controls that cannot be disabled by the child.
Pros and cons
- Pro: App blocklists, per-app limits, and schedules support specific household rules rather than only broad device restrictions.
- Pro: Location, usage, new-app, and tamper reporting give parents several kinds of visibility in one system.
- Pro: The visible child interface and stated privacy boundaries make consent a central part of supervision.
- Con: Self-hosting and the documented developer tools put setup and maintenance beyond the comfort level of many families.
- Con: The child app is Android-only and sideloaded, leaving iOS households without equivalent child-device coverage.
- Con: The app can be disabled, and alerts about bypasses do not prevent them.
- Con: There is no content filtering, so parents seeking web or material restrictions need another solution.
Alternatives
For a wider selection, browse Parental control apps. OpenParental is the more fitting option for families who prioritize open-source software and are prepared to self-host; choose another parental-control app if you need a different platform or managed deployment.
The other linked alternatives are voice-changing tools rather than parental-control products, so they do not address the same need: EaseUS VoiceWave, FineShare VoiceTrans, Voice.ai, Dubbing AI, Echo Live, iMyFone MagicMic, IceVox, and Voicemod AI Voice Cleaner. The linked Game Voice Changers and AI Voice Changer Software lists are also for voice-changing software, not parental controls.
Verdict
Choose OpenParental if your family wants consent-based Android supervision, practical app and schedule controls, and visible activity reporting without a software fee—and can manage a self-hosted deployment. Look elsewhere if you need content filtering, iOS support, a managed setup, or stronger resistance to a child disabling controls.