systemg - systemg<br>Documentation Index<br>Fetch the complete documentation index at: /llms.txt<br>Use this file to discover all available pages before exploring further.
Skip to main content
Search...
Navigation<br>systemg
:first-child]:hidden! peer-[.is-custom]:[&>:first-child]:sm:hidden! peer-[.is-custom]:[&>:first-child]:md:hidden! peer-[.is-custom]:[&>:first-child]:lg:hidden! peer-[.is-custom]:[&>:first-child]:xl:hidden! peer-[.is-center]:[&>:first-child]:hidden! peer-[.is-center]:[&>:first-child]:sm:hidden! peer-[.is-center]:[&>:first-child]:md:hidden! peer-[.is-center]:[&>:first-child]:lg:hidden! peer-[.is-center]:[&>:first-child]:xl:hidden!">
systemg runs your service graph from a single YAML file.<br>Install
Verify
curl --proto '=https' --tlsv1.2 -fsSL https://sh.sysg.dev/ | sh
sysg --version
Quickstart<br>Launch your first service graph in minutes.
Examples<br>Start from working examples for real-world service layouts.
What systemg does
Suppose you’re building an API that needs PostgreSQL, Redis, and a background<br>worker. Instead of starting each service manually in different terminals, you<br>define them once in a YAML file. systemg starts everything in the right order,<br>restarts crashed services, and provides unified logging.
version: "2"<br>services:<br>postgres:<br>command: "postgres -D /var/lib/postgresql/data"<br>redis:<br>command: "redis-cli ping"<br>api:<br>command: "python app.py"<br>depends_on: ["postgres", "redis"]<br>worker:<br>command: "celery worker -A tasks"<br>depends_on: ["redis"]<br>backup:<br>command: "pg_dump mydb > /backups/db-$(date +%Y%m%d).sql"<br>cron:<br>expression: "0 0 2 * * *"<br>timezone: "America/New_York"<br>hooks:<br>onstart:<br>command: "curl -X POST https://hooks.slack.com/services/T00/B00/XXX -H 'Content-Type: application/json' -d '{\"text\":\"Backup completed successfully\"}'"<br>onerr:<br>command: "curl -X POST https://hooks.slack.com/services/T00/B00/XXX -H 'Content-Type: application/json' -d '{\"text\":\"Backup failed!\"}'"
Built for production
Start services in dependency order.
Restart failed processes with configurable backoff.
Keep service logs isolated and predictable.
Run everything from a single binary.
⌘I
Assistant
Responses are generated using AI and may contain mistakes.