Sign in to continue
Don't have an account? Sign up
Host a Python or Node server, a SQLite database, and a terminal — all under your own account, running on shared infrastructure instead of your own hardware.
Deploy runs main.py or main.js in your project root as a real, always-on server (reads the port from the PORT env var). Share static just serves the project's files as-is, no server needed. Host Minecraft spins up a real PaperMC server (vanilla-compatible, much faster startup) and gives you a bore.pub:PORT address to connect to within seconds — first launch also downloads the server and generates the world, typically done in under a minute. Collaborate gives someone else full edit/deploy access to this exact project via a link. Publish to Gallery lists this project (with its deploy/share link) on the public community gallery for anyone to browse and like.
No file open
TERMINAL
DATABASE (SQLite)
✦

AI Assistant

Describe what you want built. It writes the files straight into your current project — Python or Node for a real server, or plain HTML for a static page — and you can deploy it right after.

Writes into: no project selected — files created here appear in the Files tab.
No project selected
—
CPU load (1m)—
Memory—
Disk (shared)—
Your workspace—
Instance uptime: — Process uptime: — Process memory: — Deploys: — Last deployed: —
Environment variables
Changes take effect on the next deploy/restart — PORT is always injected automatically, no need to set it yourself.
🔒 Secrets
API keys and other sensitive values — encrypted at rest (AES/Fernet), never shown back in full, decrypted only when your server deploys. Injected as environment variables, same as above.
⚡ Worker (advanced)
Instead of main.py/main.js, add a worker.js file for a Cloudflare-Workers-style handler — no HTTP server boilerplate:
module.exports = { async fetch(request) { return new Response("hello", { status: 200 }); // or: return Response.json({ ok: true }); } };
Detected automatically if present (checked after main.py/main.js) — just click Deploy.
Deploy logs stopped
Deploy your server, then click "Watch live" to tail its output.
📦 Deploy history
A snapshot of your files is kept before every deploy (last 10). Roll back to restore an older version, then Deploy again to make it live.
No project selected.
⏰ Scheduled jobs
Runs a shell command in your project's workspace on a repeating interval — backups, scrapes, cleanup, anything that doesn't need to be an always-on server.
Every minutes
No project selected.
⚡ Luisflow automations
Fire an action automatically when something real happens to your account's projects — right now: a deploy succeeding or failing. Scope one to a single project, or leave it blank to cover every project you own.
Log in to manage automations.
This runs on shared infrastructure (one instance serving every project), so CPU/memory/disk numbers reflect the whole machine, not just yours — your workspace size and process stats are measured separately. "Restart" stops and restarts your server; it does not reboot the shared instance.