Skip to main content
What you need to run SPF depends on how you deliver it. The API and Hosted have no local requirements worth speaking of; On-Premise has real ones.

​
Browsers

The SPF employee interface (used by Hosted and on-premise clients) supports the following on both desktop and mobile.
  • Google Chrome 110 or newer
  • Mozilla Firefox ESR or newer
  • Safari 16.4 or newer

​
Mobile operating systems

  • iOS 12.4.9 or newer
  • Android 4.4 or newer
Symmetry strongly advises using current, supported browsers with all Symmetry products.
API clients aren’t bound by this list. You’re building the interface, so your own browser support policy applies.

​
On-Premise server requirements

SPF On-Premise is a Java web application (spf.war) deployed into a servlet container you operate.

​
Minimum

  • Java 8 or newer
  • A Servlet 3.1+ container: Tomcat 8.5+, Jetty 9.4+, or WildFly 10+
  • Bootstrap 5
  • 4 GB of memory
  • 1 GB of disk space, covering SPF, the container, Java, and room for logs

​
Suggested for production

  • Java 8
  • Tomcat 8.5.x or newer, or an equivalent servlet container
  • 16 GB of memory
  • 5 GB of disk space

​
Fonts

PDF generation requires Courier, Courier-Bold, and ZapfDingbats, or acceptable substitutes, installed on the server. Updating Symmetry Payroll Forms lists the accepted substitutes for each.

​
A note on Tomcat 10

Tomcat 8.5.x, 9.x, and 10.x all work, but Tomcat 10 needs one extra step. It moved to the Jakarta servlet implementation, which SPF isn’t built against. Deploy spf.war into a webapps-javaee folder in the Tomcat root instead of webapps, and Tomcat converts the application automatically. See Using Tomcat.

​
Next steps

On-premise quickstart

Download, deploy, and verify an installation.

Updating SPF

Full specifications and upgrade best practices.

Implementation types

Compare API, Hosted, and On-Premise.

Licensing

Credentials for each implementation.