FAQ

Blue is a platform for publishing apps made with AI. Just upload a ZIP file and your app is live on the web instantly.

Blue currently supports four runtimes:

• python — Python applications
• node — Node.js applications
• php — PHP applications
• static — Static HTML/CSS/JS sites

Yes. Upload a ZIP containing an index.html file and it will be published as a static app. You can also include CSS and JavaScript files.

No. Sign-up is open and no invite code is required — anyone can register with an email address or a Google / Microsoft account. Invite and referral codes are optional and grant bonus credits when entered. If we've reached our current capacity, we may ask you to join a waitlist so we can onboard people in order.

There are three ways to deploy:

• Console — Upload a ZIP file from the console
• AI Build — Enter a prompt inside Blue and publish directly
• API — Use a deploy key (API key) for automated deployment

Click "Redeploy" on your app card in the console and upload a new ZIP file. Your app URL stays the same.

Yes. You can change the visibility level of your app in the console:

• Casual — Protected with a simple password
• Safe — Stronger access restriction
• Private — Only you can access it

Make sure the entry file (index.html, main.py, etc.) is at the root level of the ZIP, not nested inside a folder.

Tip: Select the files themselves and compress, rather than compressing the parent folder. An extra folder layer can cause runtime detection to fail.

Your files are likely nested one level too deep inside the ZIP. Make sure the entry file (index.html, main.py, etc.) is at the root of the ZIP, not inside a subfolder.

If you compressed a folder instead of individual files, re-compress by selecting the files directly.

Common causes:

• Dependency installation failed
• The app is listening on the wrong port
• There is an error in the code

Check the logs in the console for error messages.

The deployment security scan blocks apps that contain dangerous patterns such as reverse shells or system file access.

Code inside dependency directories like node_modules is excluded from the scan. Review your own code and remove any flagged patterns.

Apps owned by registered users are not stopped solely because they have not received traffic. Common reasons an app may stop:

• Health check failure — The app stopped responding correctly
• Operational action — Resource pressure, a terms-of-service violation, or another operational reason
• Manual action — The owner or an authorized member stopped the app

Check your app card in the console to see the stop reason.

Open App performance in the Console and switch from Standard to Power. Creator can use Power for one app, and Pro for three apps.

A running app is never restarted automatically. Use Restart now to open Blue's confirmation modal, or restart it manually later. A stopped app applies the change on its next start. Switching back to Standard works the same way.

Each plan has limits on the number of apps and resources. If you have reached your limit:

• Stop or delete unused apps to free up capacity
• Upgrade your plan to increase the limits

Open your app card in the console and click "Logs" to see recent output. Click "Live Logs" to stream logs in real time.

If an error occurs, you will find error messages and stack traces in the log output.