Manage Your Backend From Your Android Phone
Check, deploy, roll back and monitor 33 hosting, database, backend, monitoring, code, payments and messaging services from your Android phone. PocketCode's Backend Manager runs it all from the IDE.
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." PocketCode'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. PocketCode doesn't host, bill or proxy any of these services: each call goes from your phone to the provider's official API, with your own account.
33 services in 8 families
The Backend Manager groups everything that orbits your project but lives outside the code into eight families. It opens on three tabs: Status ("is anything broken right now?"), Projects (every project from every connected account in one list) and Services (what's connected, plus the catalog to connect the rest).
| Family | Services |
|---|---|
| Hosting (8) | Vercel, Netlify, Render, Railway, Fly.io, Cloudflare, DigitalOcean, Expo EAS |
| Databases (7) | Firebase, Supabase, Neon, PlanetScale, MongoDB Atlas, Turso, Upstash |
| Backend (4) | Appwrite, Convex, PocketBase, Clerk |
| Monitoring (5) | Sentry, PostHog, Axiom, Healthchecks.io, UptimeRobot |
| Code (3) | GitHub, GitLab, Bitbucket |
| Payments (2) | Stripe, RevenueCat |
| Messaging (3) | Resend, OneSignal, Twilio |
| Media (1) | Cloudinary |
Hosting: honest capabilities per provider
Every hosting provider exposes a different slice of API surface, and the Backend Manager doesn't pretend otherwise. The matrix below shows what each one offers (a full tick means available, a half tick means partial because the provider's API only gives part of it, and a dash means the provider has no API for it).
| Capability | Vercel | Netlify | Render | Railway | Fly.io | Cloudflare | DigitalOcean |
|---|---|---|---|---|---|---|---|
| Deployments and activity | Yes | Yes | Yes | Yes | Partial | Yes | Yes |
| Build logs | Yes | — | Yes | Yes | — | Yes | Partial |
| Runtime logs | Yes | — | Yes | Yes | — | Yes | Partial |
| Live logs (Pro) | Yes | — | Yes | Yes | — | Partial | Yes |
| Rollback (Pro) | Yes | Yes | Yes | Yes | — | Yes | Yes |
| Environment variables | Yes | Yes | Yes | Yes | Partial | Partial | Yes |
| Domains and DNS | Yes | Yes | — | Yes | Yes | Yes | Yes |
| Metrics | Partial | — | Yes | Yes | Partial | Partial | Yes |
| Usage and cost | Partial | Partial | — | Partial | — | — | Yes |
A few of the partial cells, spelled out. Fly.io has no deployment history (it shows the release in progress and its machines), no logs and no rollback; its environment variables are secrets (names and a digest). Cloudflare variables are Pages only, and its live stream only carries Pages Functions. DigitalOcean's "App logs" is the deploy log of the latest version only, and its runtime logs come only through Live Logs. Netlify publishes no log API that PocketCode can read. Railway's usage is an estimate with no amount.
Expo EAS shows a read-only list of your builds and their status, through an internal Expo API on a best-effort basis. Reading is free almost everywhere: live logs and the PostHog feature-flag list are Pro. Changes are not free. Writing environment variables, changing DNS, adding a custom domain, suspending a project and scaling are Pro actions, and each one tells you what it will change and asks you to confirm, with your fingerprint or screen lock too when the phone has one. Rolling back a deployment is also Pro, with one confirmation.
A redeploy is a lighter action: one confirmation, and on the free plan one deploy in flight at a time per project.
Going deeper: Cloudflare and DigitalOcean
Two providers have far more surface than a basic deploy flow, so the Backend Manager shows more of it.
- Cloudflare — beyond Pages, browse Workers scripts, KV namespaces, D1 databases, R2 buckets, DNS zones and certificates.
- DigitalOcean — droplets, managed databases, volumes and uptime checks. DigitalOcean's managed PostgreSQL, MySQL and Redis also open straight in the Database module, with no manual form.
Databases and backend services
- Supabase, Neon, PlanetScale, Turso, Upstash, MongoDB Atlas — a project's usage and health in the Backend Manager (MongoDB Atlas even shows real billing). Tables, SQL console and security tools live in the Database module; the Backend Manager links straight in with an Open in Database row. DigitalOcean's managed PostgreSQL, MySQL and Redis open the same way, from Managed databases.
- Firebase — Firestore collections and documents, using your own Firebase project. They open in the Database module too.
- Appwrite — users, functions, executions and rows.
- Convex — queries, usage and limits.
- PocketBase — collections and records.
- Clerk — users and sessions.
Monitoring: is it actually working?
- Sentry — issues, crash-free rate, logs and crons.
- PostHog — insights, events, feature flags (Pro, even to read), recordings, experiments and error tracking.
- Axiom — queries.
- Healthchecks.io and UptimeRobot — checks, with response times on UptimeRobot.
The Code, Payments and Messaging families round it out: GitHub Actions runs and jobs (with pending deployments you can approve), Stripe balance and today's charges, RevenueCat MRR, Resend deliveries and bounces, OneSignal notifications, Twilio balance and alerts, and Cloudinary credits.
Kubernetes and One-Click Deploy: not working in this version
The + button of the Projects tab lists One-Click Deploy and
Kubernetes (a local YAML generator for a Deployment and a Service), but
the screen each one opens shows nothing in this version. Until that is fixed, the
way to deploy from the phone is Deploy from the editor, or a Redeploy of a
project that already exists.
Your tokens stay locked to the device
Open the Services tab, tap a service in the Connect block, and paste a key. GitHub and GitLab show you a short code to type on their page; Railway and Firebase can sign in through the browser when your build includes it; the rest use a token, a key or a short form. The app checks it against the provider straight away and tells you what's wrong if it fails. Where the provider allows it, the screen asks for a read-only key and, for ten of the services, lists the minimum permissions to tick; where it can't be limited (Netlify, Render, Supabase, Resend, Clerk, RevenueCat, Cloudinary, PocketBase and OneSignal keys give access to the whole account), it warns you before you paste.
Every token is encrypted with the Android Keystore and only travels to the provider's own API (or, for PocketBase and self-hosted Appwrite, to the server you type in). The tokens you connect here never go to PocketCode's servers. Signing in to PocketCode itself with GitHub is a separate thing: that GitHub token is stored encrypted on PocketCode's backend, which uses it to list your repositories.
What's free, and what's Pro
Almost everything you need to read and understand your infrastructure is free: connecting all 33 services (one account each), status, projects, build and runtime logs, metrics and usage, viewing domains and DNS, and one deploy in flight at a time per project. The exceptions are live logs and the PostHog feature-flag list, which are Pro.
Pro is for changing things, for the phone watching them for you, and for the extras: environment variable writes, DNS changes, adding custom domains, suspending and scaling, rollback, live logs, PostHog feature flags (reading them and changing their rollout), background checks with notifications and the two Android home-screen Backend widgets, several accounts per provider, and AI summaries such as why a build failed. Background checks run on Android's schedule, so a notification can arrive up to 15 minutes late: there is no server pushing it.
Managing a backend used to mean a desk, a laptop, and a fistful of browser tabs. It doesn't anymore. PocketCode puts hosting, databases, backend services, monitoring, code, payments and messaging — 33 services, real API calls, encrypted tokens — in the same app where you write and ship the code, with the gaps listed above.
PocketCode is heading to Google Play. Join the pre-registration to be among the first to run your backend from your phone.
Backend Manager
Quick answers on this
Keep reading
- FeatureWhat's new in API Tester: Socket.IO, MQTT and real test scriptsThe API Tester grows from four protocols to six with Socket.IO and MQTT, and swaps its old test evaluator for a real sandboxed JavaScript engine. Plus: collections as project files.5 min
- FeatureCortex: Stop Being the Index of Your Own AI ChatsA new PocketCode mode where you talk to a coordinator instead of an assistant: it splits your work across specialized chat sessions that stay alive for weeks, and hands back grouped decisions instead of scattered interruptions.14 min
- FeatureAn AI Dev Team in Your Pocket: Multi-Agent Coding with AI OfficeBeyond autocomplete: PocketCode's AI Office turns a brief into a team of specialized AI agents that plan, split, build and review your project — with real tools — from your Android phone.8 min

