Encrypted command delivery for managed Android fleets — without Firebase, FCM, or Google push.
Lockia Push moves signed, end-to-end encrypted commands to GMS and AOSP devices through a customer-scoped MQTT path. The current service is a private pilot with one validated region.
- E2E encrypted payloads (AES-256-GCM, RSA-OAEP-SHA256 key wrap)
- Signed ACK proof of execution (in delivery)
- Regional policy model; additional deployments require contract validation
- Device Owner / kiosk / launcher integration
- Tenant
- Regional gateway
- LockiaMQ broker
- Device
Built for the operations Firebase Cloud Messaging can't handle.
Firebase Cloud Messaging is a no-cost notification transport. Lockia Push is a different product: end-to-end encrypted, signed-ACK command delivery for Android fleets you actually own.
Protocol v2 keeps command bodies ciphertext-only through the orchestrator, gateway, broker, and database. Legacy pilot tenants remain on a separate migration path.
JavaScript and Android SDKs sign requested lifecycle acknowledgements with durable retry and server-side replay enforcement. Production failover evidence remains a launch gate.
The Android SDK integrates with a host Device Owner or kiosk app but never executes device policy itself. It supports GMS and AOSP devices through MQTT.
Tenant, country, and region are first-class policy fields. One pilot region is live; additional regions and failover are not generally available.
Dedicated cloud, private APN, and on-prem deployments are design options requiring a separate implementation, security review, and executed contract.
Rotate device keys on your schedule and audit who used what and when. BYO KMS/HSM custody is designed behind a provider trait — on the roadmap, not yet shipped.
Connect nonces and ACK windows persist across replicas, and SDK state survives restarts. Cluster-failover evidence remains a launch gate.
Core mutations emit audit events. Tamper evidence, complete retention enforcement, and verified exports are not yet commercially certified.
One signed POST. One signed ACK. Evidence-oriented by design.
No SDK lock-in, no Google account, no FCM token brokerage. Push a ciphertext envelope; the device decrypts, verifies, and signs the ACK back through the broker.
# Illustrative private-pilot request; use @lockiapush/sdk to build the signed envelope.
curl https://admin.lockiapush.com/v1/messages \
-H "Authorization: Bearer $LOCKIA_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"tenant_id": "fleet-eu-1",
"device_id": "veh-90211",
"command_id": "lock.session.rotate",
"ciphertext": "<base64 AES-256-GCM>",
"signer_key_id": "key-2026-04",
"region": "eu-fra-1"
}'{
"message_id": "01HX9F7B...",
"tenant_id": "fleet-eu-1",
"device_id": "veh-90211",
"command_id": "lock.session.rotate",
"outcome": "applied",
"seq": 47821,
"signer_key_id":"dev-90211-2026-q2",
"signature": "ecdsa-p256-sha256:bx7v...c4",
"acked_at": "2026-04-29T10:31:14Z"
}What you get the moment you leave Firebase Cloud Messaging.
We don't compete with Firebase on price. We compete on control.
Firebase Cloud Messaging is a no-cost product. If a free notification ping is all you need, FCM is fine. Lockia Push is a private-pilot command-delivery system for encrypted, signed traffic to managed non-Google fleets.
- • you only need consumer-grade push notifications
- • devices are GMS phones with Google Play Services
- • you don't need delivery proof or signed ACKs
- • plaintext payload visibility to Google is acceptable
- • regional routing isn't a procurement requirement
- • Android command bodies must be encrypted end-to-end
- • you need signed ACK evidence for your own compliance review
- • fleets include AOSP / non-GMS / rugged / kiosk devices
- • you can contract and validate a residency, sovereign, or OEM deployment before launch
- • operations need real-time visibility per region and per device
Private-pilot access while commercial launch controls are completed.
Pricing pending business approval. The plans live in code so quotes, the public site, and Stripe stay in sync.
- • 1 tenant in the current pilot region
- • Up to 250 active devices
- • 100k messages / month
- • Mock + dev environments
- • Up to 25,000 devices self-serve
- • Additional regions and failover are not generally available
- • 5 API clients
- • Webhook event delivery is not yet available
- • Up to 250,000 devices (sales-assisted above)
- • Priority dispatch controls
- • Webhook test endpoints; event delivery is not yet available
- • 1-year retention target; purge evidence pending