Who it is forA systems administrator who runs services on a Linux host and does not want a container runtime.
The problemTeams that avoid Docker still need the same gateway, dashboard, and migrations on their own hosts.
The outcomeGateway and dashboard run natively, supervised by systemd units or the foreground supervisor.
What you need first
- Docker with Docker Compose, curl, and jq, or Go and Make for the native build
- At least one provider API key such as OPENAI_API_KEY or ANTHROPIC_API_KEY in .env
- A host with ports 8080 and 3000 free, or a changed GATEWAY_PORT
Steps
- Clone the repo and run
make buildfrom the repo root. - Run
synapass native installto create templates, build, and apply migrations. - Run
synapass native upfor a foreground supervisor, or install the units fromdeploy/systemd/for production. - Check readiness with
curl -sf http://127.0.0.1:8080/ready.
Prompt for your agent
In the ShadowSafin/Synapass repo, build with make build, install with synapass native install, and start with synapass native up on <host>. Report the output of curl -sf http://127.0.0.1:8080/ready. Verify that the readiness check succeeds before reporting the service as running.
Caveat. The README gives native steps for Linux but names PostgreSQL, Redis, ClickHouse, and NATS as required services, so you must provision those before the native install can work.
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