Authorization notice. Rakazo is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.
Credentials. The sandbox provider API key and model keys stored in .env on a public server must be protected with server hardening.
Remote script. The installer is downloaded from the internet and run with bash, so review the script before running it on a server.
Who it is forA small team lead who wants bots and shared Team Computers to stay online without a laptop left running, and who can manage a server and a domain.
The problemBots on a personal laptop stop when the machine sleeps, so the team cannot count on them to answer or finish work.
The outcomeA Rakazo instance on a VPS behind HTTPS, reachable from the desktop app, mobile app, or a browser.
What you need first
- Docker Engine and the Compose plugin
- curl and OpenSSL
- A model provider account or key, such as an OpenRouter API key or a supported provider connected during onboarding
Steps
- Run
bash install-images.sh --prepare-onlyon the VPS. - Edit .env and set SANDBOX_PROVIDER (for example boat, e2b, or daytona) with its API key, and set RAKAZO_HOST to your domain.
- Run
bash install-images.sh. - Put HTTPS in front of port 5173 using the Caddy setup in docs/self-host.md.
- In the desktop app, choose Existing instance and enter the https:// address.
Prompt for your agent
In the Rakazo repo at https://github.com/elie222/rakazo, follow the Run on a server section and docs/self-host.md to prepare a VPS for <your-domain>. Report the sandbox provider chosen and the public https:// address. Verify that the health check for the instance succeeds over HTTPS before reporting completion.
Caveat. The README says public servers must use HTTPS, and the self-hosting guide covers the Caddy setup and host hardening you need to add.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page