Devices online0 / 0No phones paired
PRIVATE CONTROL PLANE
Good to see you.
Good to see you.
Your devices are within reach.
Waiting for your phones to pair with the private server.
Commands0Waiting for activity
Messages stored0MySQL is ready
YOUR HARDWARE
Personal devices
LIVE FEED
Recent activity
ONE TAP
Quick actions
REMOTE ACTIONS
Make the phone respond.
Every command is constrained on the server and can also be disabled on each phone.
No phone selected
INSTANT CONTROLS
Device actions
CUSTOM ALERT
Push a notification
⌾
On-device guardrailThe “Allow remote actions” switch must be enabled in the Android app.
RECENT
Action history
MESSAGING
Text without picking up the phone.
Messages go through the selected phone’s SIM and are recorded in your private database.
REAL-TIME QUEUE
Queued → accepted → doneSMS task status
AUDIT TRAIL
Everything, in one timeline.
Review queued, delivered, accepted, completed, or failed commands across both phones.
COMMAND LOG
Command history
SYSTEM EVENTS
Connection & message events
PRIVATE SETUP
Connect phones and automations.
The Android clients talk only to this server; the MySQL password never goes on either phone.
Pair each phone
Install the APK, then enter this WebSocket address and the device token from the ignored server .env.
Trigger a webhook
Send one allow-listed command with your webhook secret as a Bearer token.
Keep it private
- Put the public server behind HTTPS.
- Do not expose MySQL directly if a private network or tunnel is available.
- Use a different secret for console, phones, and webhooks.
- Keep Android action toggles off when not needed.
Allowed webhook actions
notifyringstop_ringvibratetorchsend_smsget_smsget_status
Unknown action names and oversized values are rejected before a command is stored.