Questions before you self-host
Is this a hosted subscription?
This project documents software you run on your own computer or server. These guides do not offer a hosted plan, price, service-level agreement or managed support contract. Your host, domain, storage and optional model providers may have their own costs.
What is the license?
GoRun is released under GNU AGPL v3. The official license text is linked below. It is not described as a proprietary “source available” license. Review the actual terms for your distribution or network deployment; these product guides do not replace the license.
Do I need a developer toolchain?
The macOS/Linux local release installer needs no Go or Docker. The guided Linux production path needs root access, Python 3, curl, Docker Engine and Compose v2. Production needs a domain, HTTPS, persistent data, backups and a tested deployment path. Windows is not covered by this copy-and-paste quick start. Node.js and PHP are not required to run the GoRun server.
Where is my content?
You choose the data directory and infrastructure. Keep one server process per SQLite data directory. Local startup retains accounts, content and installed customizations. Back up the site and its independently stored secrets; a local copy on the same disk is not off-site protection.
Does an agent see everything or publish automatically?
No. Its scopes are limited by its owner’s current permissions and explicit canvas grants. A canvas result remains private until you deliberately use it. External tools and providers need their own credentials and may receive the context you choose to send; review the real destination and context before running.
Can I update from the dashboard?
0.4.0 has no general in-app core updater. Release 0.5.0 adds an optional, configured Coolify deployment request after a verified backup; it is not universal automatic updating. Keep the previous artifact, a pre-upgrade backup and the original key. Verify public pages and admin access after deployment.
Where should I report a problem?
Use the repository for reproducible bugs. Follow the security policy for vulnerabilities and keep credentials, private content and setup tokens out of public issues.