Does this install or start a service on my server?

No. It generates a unit file and commands locally in the browser. Inputs are not uploaded or saved. You must review the output and run any installation commands yourself.

Can I paste a shell command into the arguments field?

No. Enter an absolute executable path separately and one literal argument per line. The builder escapes dollar signs and percent signs rather than expanding variables, and does not run pipes or redirects. Blank lines are ignored; empty arguments and standalone semicolons are not supported.

Which service types are supported?

Only system-level Type=simple units for foreground processes under an existing non-root account. Forking daemons, notify services, oneshot jobs, timers, template units, and user services need different configuration.

Is an EnvironmentFile the same as sourcing a .env file?

No. systemd parses the file using its own assignment and quoting rules. It does not execute a shell or expand shell expressions. Use plain KEY=value assignments and check systemd.exec for details; do not assume an application's dotenv file is compatible.

systemd Service Builder

Runs locally. Inputs are not uploaded or saved. Generates a system-level service for a foreground application under an existing non-root account; nothing is installed or executed here.

Service name (without .service) Description Executable (absolute path) Working directory (absolute path) Existing service user Group (optional; otherwise user's primary group)

Arguments (one literal argument per line; blank lines ignored)

/opt/example-app/server.js

Do not paste a shell command. Spaces inside a line belong to that single argument. Dollar signs and percent signs are escaped as literals: no variable expansion, pipes, redirects, or shell evaluation.

Environment file path (optional; do not paste its contents)

Restart policy Restart delay (seconds) Stop timeout (seconds)

Ignore a missing environment file Wait for network-online.target NoNewPrivileges + PrivateTmp

Network ordering is not a guarantee of connectivity. Hardening is optional: it prevents gaining privileges and isolates /tmp and /var/tmp, which can change application behavior. Review paths, permissions, and environment-file syntax on your server.

Service unit

Generated .service file

Review and install on your server

These commands modify system configuration and start the application when you run them. Download the unit first. Create the service account and deploy the application separately; the builder cannot check either exists.

Installation and troubleshooting commands

Learn

systemd Service Builder Guide

About this tool

Generate a system-level Type=simple service for a foreground application running under an existing non-root user. Configure its working directory, literal arguments, optional environment file, restart policy, network ordering, and optional NoNewPrivileges and PrivateTmp settings.

Questions

Does this install or start a service on my server?: No. It generates a unit file and commands locally in the browser. Inputs are not uploaded or saved. You must review the output and run any installation commands yourself.
Can I paste a shell command into the arguments field?: No. Enter an absolute executable path separately and one literal argument per line. The builder escapes dollar signs and percent signs rather than expanding variables, and does not run pipes or redirects. Blank lines are ignored; empty arguments and standalone semicolons are not supported.
Which service types are supported?: Only system-level Type=simple units for foreground processes under an existing non-root account. Forking daemons, notify services, oneshot jobs, timers, template units, and user services need different configuration.
Is an EnvironmentFile the same as sourcing a .env file?: No. systemd parses the file using its own assignment and quoting rules. It does not execute a shell or expand shell expressions. Use plain KEY=value assignments and check systemd.exec for details; do not assume an application’s dotenv file is compatible.