Skip to main content
Quick answers to the most common questions about nowrun — from account setup and card verification to supported engines and the agent-driven workflow.
The $0 card verification is not a charge — it’s a lightweight check to prevent spam and abuse. Your card is not billed, and you remain on the free plan until you choose to upgrade.
No. Your agent runs nowrun login, a browser tab opens, and you approve the device. There is nothing to copy or paste. If the machine has no browser, open the URL the command prints on your phone and approve it there.
Python 3.8 or later is required to install and run the nowrun CLI.
Your agent needs to be able to run shell commands and install Python packages. Standard AI coding agents — including Claude Code, Codex, Cursor, and similar tools — already have these capabilities and work with nowrun out of the box.
For Android, any engine that produces an .apk file is supported: native Android, Unity, Godot, Unreal Engine, and others. The .aab (Android App Bundle) format is not supported, configure your build pipeline to output a plain .apk file.nowrun also supports HTML5 web games, deployed as a .zip web bundle. Create the app with nowrun app create --type h5, then deploy the bundle with nowrun deploy -f <bundle>.zip.
Yes. Ask your agent to run nowrun deploy -f <build> again after a new build. nowrun creates a new version of your app; your existing URL remains live throughout the process.
No. The live URL nowrun generates opens in any standard browser. Only the person deploying the app needs a nowrun account and the CLI. Your users just click the link.
Yes, the CLI works independently. Run nowrun login to authenticate, nowrun app create once to register the app, then nowrun deploy -f <build> to push it. That said, nowrun is designed and optimized for agent-driven workflows, so using an AI agent gives you the smoothest experience.
Log in to the dashboard at nowrun.io and navigate to Plan & Billing to view available plans and upgrade options.