Run Node.js on Your Phone (iPhone + Android)

You can run Node.js from your phone today, but the honest answer is that where it runs matters. Real, unmodified Node.js needs a Linux or macOS machine, so the fastest path is to install Cosyra for iOS or Cosyra for Android, sign in, and type node --version in the terminal — it is already there, because the AI coding CLIs we pre-install are Node programs. On Android you can also run Node locally in Termux with some sharp edges; on iPhone you cannot run real Node at all. Here is each option, honestly.

This guide was written by the Cosyra team. We run Node-based tools from a phone every day, and we checked the moving parts against primary sources on 2026-06-08: the Node.js release schedule, the Termux package recipe, the iSH and a-Shell issue trackers, and Apple's App Store Review Guidelines. Versions and dates below carry that date so you can re-verify them.

Why is running Node.js on a phone hard?

Node.js is not just a language — it is the V8 JavaScript engine plus a large set of native bindings (the filesystem, networking, child processes, the npm ecosystem). Two phone-specific facts get in the way. On iOS, V8 relies on just-in-time compilation, and Apple's App Store Review Guidelines forbid third-party apps from generating and executing code that way, so the real V8 build cannot run. On Android, you can run Node in Termux, but the OS treats long-lived background processes as disposable and the userland is arm64, where some native addons have no prebuilt binary.

None of that applies to a normal Linux server. So every working approach below either runs Node on-device with those constraints (Termux) or puts Node on a real Linux box your phone talks to (a cloud container).

How can you run Node.js on a phone?

There are three realistic paths in 2026: a cloud Ubuntu container with Node pre-installed reached from a native app (Cosyra), Termux on Android, and — on iOS — a set of options that all fall short of real Node. We will be specific about what each one actually gives you.

1. Cosyra: a cloud Ubuntu container with real Node.js

This is what we build. A native iOS and Android terminal connected to a persistent Ubuntu 24.04 x86_64 container. Because Claude Code, Codex CLI, Gemini CLI, and OpenCode are all Node programs, a current Node LTS and npm are already on the PATH. You get unmodified V8, working native-module compilation, and 30 GB of persistent storage.

• Works when: you want a real Node runtime — npm install that compiles native addons, a dev server that stays up, an LTS you can pin with nvm.
• Breaks when: you have no internet (the container is in the cloud), or you specifically need Node running on the device hardware itself.
• Cost: 1 hour free on signup, no credit card; a 10-hour, 7-day trial when you want more; then $29.99/month or $300/year. See pricing.

2. Termux: Node on-device on Android

Termux is an open-source Android terminal with a real package manager. pkg install nodejs installs Node, and for short scripts it works well. Three things to know before you lean on it:

• The default is Current, not LTS. The nodejs package tracks the Current line — Node 26.x as of 2026-06-08 per the Termux package recipe. For the LTS line, install nodejs-lts instead; the two packages conflict, so pick one.
• arm64 native modules can fail. Termux is an arm64 userland. Any npm package with a native addon that lacks an arm64 prebuild has to compile from source, which often fails for want of build tooling — developers have hit exactly this installing Node-based AI CLIs on Termux.
• Android can kill your process. Android 12 and later ship a phantom-process killer that terminates long-running child processes with signal 9; in Termux it surfaces as [Process completed (signal 9)]. It is the reason dev servers and long npm installs die. There are ADB workarounds, but they are not something everyone wants to maintain.

For more on the Android side, see our guide on running a Linux container on Android.

3. iPhone and iPad: the hard truth about Node on iOS

There is no real Node.js on stock iOS, and it is worth understanding why so you do not waste an afternoon on it:

• iSH emulates x86 Alpine Linux. You can apk add nodejs, but running node crashes with an illegal-instruction error: iSH's emulator does not implement the SSE2 instructions V8's JIT depends on. It is a long-standing, unresolved limitation in the iSH issue tracker, and iSH is slow regardless because it is pure emulation. See Cosyra vs iSH.
• a-Shell ships a JavaScriptCore engine, not Node. JavaScriptCore is the language engine only — there is no node binary, no npm, and none of Node's API surface (process, fs, require). Node support has been an open feature request since 2021.
• play.js markets a "Node.js IDE" but is a port of Node onto JavaScriptCore (V8 swapped for Apple's allowed engine). It runs a lot of JavaScript, but it is Node-compatible, not full Node, and native npm modules are limited.

The clean fix on iPhone is the same as on a locked-down work laptop: run Node somewhere real and reach it. That is the cloud-container path, and on iOS it is effectively the only way to get unmodified Node.

How do you run Node.js on iPhone or Android with Cosyra?

You set it up in about three minutes: install the app, sign in, confirm node is on the PATH, optionally pin a version with nvm, clone a repo, and npm install. No JIT workaround, no phantom-process killer, no SSH tunnel to babysit.

Step 1: Install Cosyra and sign in

Download from the App Store or Google Play. Sign in with Apple, Google, or email. On first launch we provision a fresh Ubuntu 24.04 container.

Step 2: Confirm Node.js and npm are there

Node is already installed because the bundled AI CLIs need it. Verify it in one command. The image tracks the active LTS (Node 24 at the time of writing) and we re-bake it regularly.

Step 3: Pin a specific Node version with nvm (optional)

Need a specific line for a project? Install nvm and switch versions per project. This is real version management, not a shim.

Step 4: Clone a project and install dependencies

Step 5: Run a script or a dev server

The container keeps running when you lock the phone, so the server is still up when you glance back at it — the thing Android's process killer takes away from a local Termux server.

Which Node.js version should you use in 2026?

Use Node 24. As of 2026-06-08 the Node.js release lines sit like this:

The catch on phones: Termux's default nodejs package installs the Current line (Node 26), not an LTS, so a fresh Termux install can put you on a version most production projects do not target. In a container you control the version explicitly with nvm.

What can you actually do with Node.js from a phone?

Enough to be useful in a 15-minute gap. Clone a repo and run its test suite, bump a dependency and confirm the build still passes, run a one-off migration script, spin up a dev server to check an API response, or drive a Node-based AI CLI against the codebase. Because the container persists, you pick the same work back up on an iPad or a laptop without re-cloning anything.

That last one is the common case we see: Node is the runtime under the AI agents. If your real goal is to run Claude Code, Codex CLI, or the other agents from your phone, a working Node runtime is the foundation they sit on.

What are the real limits?

• No offline mode in the cloud path. The container lives in the cloud; no internet, no terminal. Termux runs offline, with the caveats above.
• Phone keyboards are slow for long input. A Bluetooth keyboard or voice dictation helps for anything past a quick command.
• Heavy builds are still heavy. A cloud container handles a normal web project comfortably, but a giant monorepo build is a laptop job.
• Native phone APIs are out of scope. This is Node on a server you reach from a phone, not Node embedded in a mobile app (that is a different tool, nodejs-mobile).

Cosyra vs Termux vs a-Shell for Node.js

Cosyra wins for a real, current Node runtime on either platform; Termux wins if you are on Android, want on-device Node, and can live with the version and process-killer caveats; a-Shell is an iOS terminal but does not run Node at all. The table lines them up, verified 2026-06-08.

If you are weighing the broader Android vs cloud question, see Cosyra vs Termux; for the iOS side, Cosyra vs a-Shell and our roundup of the best terminal apps for iPhone. The same "run a language on your phone" walkthrough for Python lives in code Python on your phone.

Frequently asked questions