Manage Your Backend From Your Android Phone

Production breaks and you're on the bus. A deploy needs a rollback, an environment variable is wrong, and the only thing in your pocket is a phone — not a laptop with the Vercel dashboard, the Cloudflare console and the Sentry tab all open. The usual answer is "wait until you're home." Pocket Code's Backend Manager removes that wait: it's a unified panel to manage your backend from your phone, wired to the real provider APIs, living right inside the IDE next to your editor and terminal.

It is not a link farm to web dashboards. It talks to the providers directly, holds your tokens in encrypted device storage, and adapts its UI to exactly what each provider's API actually supports.

Three hubs, thirteen providers

The Backend Manager splits everything that orbits your project but lives outside the code into three independent hubs. You pick one from the welcome screen and land straight in its provider grid.

Hub	Providers	The question it answers
Deploy	Vercel, Render, Netlify, Railway, Fly.io, Cloudflare, DigitalOcean	"Where does my app run?"
BaaS	Firebase, Appwrite, Convex, Supabase	"Where is my data and where are my users?"
Observability	Sentry, PostHog	"Is it working in production?"

Navigation is gesture-based — there are no visible tabs and no back button in the header. The back gesture walks you one level up, then back to the welcome screen, then closes the panel.

Deploy: honest capabilities per provider

Every hosting provider exposes a different slice of API surface, and the Backend Manager doesn't pretend otherwise. Instead of showing greyed-out buttons, it hides actions a provider can't do — so you never tap something that returns "not supported." Here's the shipped matrix, verified against the real dispatch code:

Capability	Vercel	Render	Netlify	Railway	Fly.io	Cloudflare	DigitalOcean
List projects / services	Yes	Yes	Yes	Yes	Yes	Pages	Apps
Trigger deploy	—	Yes	Yes	—	—	—	Yes
Rollback	Yes	Yes	Yes	Yes	—	Yes	Yes
Env vars (read + write/delete)	Yes	Yes	Yes	Yes	—	—	—
Custom domains	Yes	—	—	—	—	Zones	—
Build config write	Yes	Yes	—	—	—	—	—
Cancel deployment	Yes	—	—	—	—	—	—
Suspend / Resume	—	Yes	—	—	—	—	—
Servers / VMs	—	—	—	—	Apps	—	Droplets

So you can deploy a backend on Android by triggering a build on Render, Netlify or DigitalOcean; promote or roll back on Vercel, Render, Netlify, Railway, Cloudflare or DigitalOcean; edit and delete environment variables on Vercel, Render, Netlify or Railway; and suspend or resume a Render service — all from the phone.

Two honest caveats. Spinning up a brand-new project through the One-Click Deploy wizard currently resolves only for Vercel — the other providers appear in the wizard but aren't wired to a real endpoint yet. And preview deploys and branch/Git deploys have their screens built but don't trigger yet; that wiring is a follow-up, so the manager keeps those actions out of the way for now.

Under the hood these are the providers' own REST and GraphQL endpoints. A rollback on Render, for example, hits POST /v1/services/{id}/rollback; a Vercel promotion goes to POST /v10/projects/{id}/promote/{deploymentId}; env var writes on Railway run a GraphQL variableUpsert. Deleting an env var always asks for confirmation first.

Going deeper: provider capability sub-hubs

Three providers have far more surface than a basic deploy flow, and the Backend Manager surfaces it through capability sub-hubs that load lazily and cache per session.

• Cloudflare — browse Workers scripts, KV namespaces, D1 databases, R2 buckets, and Zones. On the Zones list there's an inline Purge cache action (POST /zones/{id}/purge_cache). The account ID is resolved automatically and cached for the session.
• DigitalOcean — list Kubernetes clusters, managed databases, volumes and firewalls, with droplets reachable through the Servers route.
• Railway — inspect a project's environments and volumes (project-scoped, so the state resets when you switch projects).

All of these run under a single reusable list screen, which is why the module can offer 21 different capability views without bespoke UI for each one.

Backend as a service: data and users

The BaaS hub is where you keep an eye on your backend as a service stack.

• Appwrite — list your projects, then drill into a project's users (GET /v1/users, authenticated with X-Appwrite-Key).
• Convex — list your teams, enter a deployment URL, and load its tables via the system tables query. You can also run any Convex query against the live deployment and get the result summarized back to you.
• Supabase — list projects, then drill into a project's tables. The Backend Manager fetches the project's anon key on demand, hits the PostgREST schema endpoint, and parses the public table names out of the OpenAPI definition. That anon key is never persisted — it lives in memory only for the length of the call.

One honest note: Firebase is a read-only placeholder today. Listing Firebase projects needs an OAuth scope the module hasn't wired yet, so selecting it shows an informational message pointing you to the Firebase Console rather than pretending to list projects.

Observability: is it actually working?

• Sentry — list every project your token can reach, then open its unresolved issues, color-coded by level (fatal, error, warning, info, debug). From there you can lazily load releases, alert rules, replays and user feedback.
• PostHog — list projects and their insights, then drill into events, cohorts, experiments, session recordings, dashboards and annotations. PostHog's host is configurable, so the same client works for PostHog Cloud and for a self-hosted instance — useful if you self-host from mobile and point the manager at your own deployment.

A Kubernetes manifest generator in your pocket

The Deploy hub also ships a local Kubernetes YAML generator. You fill in an app name, image, replica count, ports, namespace, and CPU/memory requests and limits, and it emits a single YAML document containing a Deployment and a matching Service, ready to paste into kubectl apply -f -. It's purely a generator — it doesn't connect to a cluster, apply anything, or validate against a live API. It just saves you from hand-writing boilerplate on a touchscreen.

Your tokens stay locked to the device

Every provider token is stored with SecureTokenStorage — EncryptedShared­ Preferences backed by the Android Keystore, using AES256-GCM for keys and AES256-SIV for values. Nothing is sent to our servers.

Before any provider call, the Backend Manager checks whether a token exists. If it doesn't, it makes zero API calls and instead shows a "Connect provider" empty state with a button to open integrations. That deep link is protected by a biometric gate — BIOMETRIC_STRONG | DEVICE_CREDENTIAL — so someone with your unlocked phone can't jump from the Backend Manager into your saved API keys without authenticating first.

What's free, and what's Pro

The doc is specific about gating, so we'll be specific too. A few capabilities sit behind a plan feature:

Action	Plan feature
Open the Custom Domains screen	CUSTOM_DOMAINS
Rollback a deployment	PREVIEW_DEPLOYS
PostHog Feature Flags	COLLABORATION

On the free plan, maxActiveDeploys is 1 — so triggering a second concurrent deploy (counting deployments that are ready, building or deploying) is what raises the PREVIEW_DEPLOYS gate. Listing projects, reading env vars, browsing Cloudflare and DigitalOcean sub-hubs, generating Kubernetes YAML, and viewing Sentry issues and PostHog insights are all part of the core experience.

Built into the IDE, not bolted on

Because the Backend Manager lives inside Pocket Code, the AI assistant can talk to it over the app's event bus. Ask it about a deploy and it can trigger one, report deploy status, summarize recent deployments as log lines, or list your projects across the Deploy and Observability hubs — all grounded in the state you're already looking at.

---

Managing a backend used to mean a desk, a laptop, and a fistful of browser tabs. It doesn't anymore. Pocket Code puts hosting, BaaS and observability — thirteen providers, real API calls, encrypted tokens — in the same app where you write and ship the code.

Pocket Code is heading to Google Play. Join the pre-registration to be among the first to run your backend from your phone.