What LuisSystemd is actually for
A real multi-tenant hosting platform: your account gets a persistent workspace with a real always-on server, a real SQLite database, a real terminal, and a real public URL — no VPS, no Dockerfile, no systemd unit file.
Use it when...
You're building something that calls an LLM
Encrypted secrets with real precedence rules, presets for OpenAI/DeepSeek/Anthropic/Stripe. Deploy a real endpoint that calls a real model in under a minute.
You want a public URL for a demo, now
Pick a template from the + button, tap Deploy — you have a live, shareable URL straight from your phone. No console, no billing setup.
Your project needs a real database
Any .db file in your workspace is a real SQLite database — tap it in the Files tab to browse tables and rows right on screen.
Something needs to run on a schedule
Backups, scrapes, cleanup — add a scheduled job from the Deploy tab, no cron access required.
You're prototyping and don't know the shape yet
Flask, Express, a bare worker.js, or static HTML — swap approaches without provisioning anything new.
More than one person needs access
Real per-project collaborators via invite links, not shared credentials.
How it comparesPicking the right tool for the job
| If you need... | Reach for |
|---|---|
| Static hosting live in seconds, same account as everything else | LuisSystemd Share — no separate host, no git repo needed. |
| Serverless at real production scale | Actual serverless platforms — worker.js here runs on shared infra, not the real edge. |
| Quick backend + db + terminal, minimal setup | LuisSystemd. |
| Scheduled jobs, no cron/systemd config | LuisSystemd Jobs. |
| A public URL without babysitting your own tunnel | Managed bore — re-tunnels automatically, no manually re-copying a URL every time a quick tunnel dies. |
| Uptime SLAs, dedicated resources | Not this — see below. |
What it's not for
- Production workloads with uptime guarantees — shared infra, no SLA, no isolation beyond account scoping.
- High-traffic public services — great for demos and small real projects, not built to scale horizontally.
- Guaranteed compute performance — stats are honestly labeled as instance-wide/shared.
- Long-term production credential storage — secrets are genuinely encrypted, but treat this as a dev/prototyping platform first.
Why bore for tunneling?
Every deployed server and static share gets its public URL from bore, a small open-source TCP tunnel — no custom proxy layer. It's a single static binary needing no account of its own, handing back a plain host:port the moment a process starts listening.
It's the platform for the gap between "just run it on my machine" and "set up real cloud infra for something that doesn't need it yet."