What you see

A control-room view, not a status icon.

Operators open PhoneForge in the morning and know — without clicking through — which devices are healthy, which ones are drifting, and which need attention before the day starts.

The dashboard is built for handoffs. A field engineer arriving for their shift reads the same panel the on-call operator left at the end of theirs.

metric · 01

LIVE

Up-time and connectivity

One glance shows which devices are online, how long they have been quiet, and what network they last reported in.

metric · 02

7–100%

Battery and thermal state

Read battery level, charging state, and device temperature on every enrolled device, with quiet thresholds so you are not paged at 49%.

metric · 03

GB

Storage and app versions

Surface running app versions against the required baseline, and watch free space drift before a device runs out at 3 a.m.

metric · 04

OPS

A complete audit trail

Every diagnostic, reboot, cache-clear, and config change is logged with the operator, device, timestamp, and outcome.

Who it is for

Built for any team that runs Android as an operational tool.

Use case

Mobile-app testing labs

Keep a stable pool of testers online, push the right app build to the right handset, and clear caches between runs without leaving the dashboard.

The playbook library

Pre-approved ADB-native diagnostics, ready to run.

Operators do not type shell commands. They pick a playbook from a library, choose a device or a group, and watch a per-device outcome line roll in. Engineering writes the playbooks; ops runs them.

Every command is logged with operator identity, device identity, timestamp, and outcome — producing a complete audit trail without anyone having to remember to write one down.

phoneforge · playbooks

  • $ playbook.health-snapshot

    Collect a health snapshot

    Pull a single, timestamped report covering battery, storage, connectivity, app versions, and last-check-in.

    READ
  • $ playbook.restart-app

    Restart a business app

    Kill and relaunch the operator-named package on selected devices, with a per-device success or failure line.

    WRITE
  • $ playbook.clear-app-cache

    Clear an application cache

    Targeted cache wipe for one app on any subset of devices — useful before a regression test or a store reset.

    WRITE
  • $ playbook.assert-installed

    Verify a required app is installed

    Assert that a named app is present at the expected version, and flag any device that drifts off the baseline.

    READ
  • $ playbook.maintenance-reboot

    Schedule a maintenance reboot

    Queue a reboot during an approved window — store closing, end of shift, before the first route — and only fire if the device is idle.

    SCHEDULE

Alerting

Quiet until something is wrong.

Alerts fire on signal, not on noise. Default thresholds are tuned for operations teams that would rather miss a 51%-battery page than live through a hundred of them a day.

silence · battery · storage
no repeat storms
  • rule · 01

    A device has not checked in for 15 minutes.

    Page the on-call operator with the site and last-seen timestamp.

  • rule · 02

    Battery drops below the configured floor during business hours.

    Send a single, low-noise alert — no repeat storms.

  • rule · 03

    Storage falls under 5% free.

    Surface the device, the heaviest app, and the suggested cache-clear playbook.

  • rule · 04

    A business app version drifts off the required baseline.

    List affected devices, ready to be re-pushed in one action.

  • rule · 05

    A device stops reporting entirely.

    Mark it offline after a grace window and hold any pending playbook until it returns.

Pricing

Two plans and a custom tier — paid onboarding is the same everywhere.

Plans are priced by device count, not by seats. You are not paying extra for the dashboard you already see — you are paying for the playbooks, the alerting, and the audit trail behind it.

Paid onboarding · one-time

$3,500 — included on every plan.

Covers enrollment, alert configuration tuned to your environment, custom playbook authoring for the playbooks you actually run, and live team training at the end of week one.

Book onboarding
Early access channel

Request early access.

Not ready to start a fleet rollout? Leave your email and we will let you know when PhoneForge is ready for your team.

No spam or noise Ops-first updates

request · access

FAQ

Questions operations teams ask first.

Short answers. If your question is not here, write to us — we read every message at phoneforge-2@polsia.app.

Built for ops teams who answer their own pages

Run Android as an operational tool, not an unknown.

Tell us how many devices, where they live, and what you want to know about them at 8 a.m. We will come back with a plan that fits — onboarding is $3,500 but a conversation is free.

Write to ops

phoneforge-2@polsia.app

Replies in under one business day. Phone and scheduling available on request.